McAfee Secure

Exam Code: FCP_FCT_AD-7.4

Exam Name: Fortinet NSE 6 - FortiClient EMS 7.4 Administrator

Certification Provider: Fortinet

Corresponding Certification: NSE6

Fortinet FCP_FCT_AD-7.4 Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

33 Questions & Answers with Testing Engine

"Fortinet NSE 6 - FortiClient EMS 7.4 Administrator Exam", also known as FCP_FCT_AD-7.4 exam, is a Fortinet certification exam.

Pass your tests with the always up-to-date FCP_FCT_AD-7.4 Exam Engine. Your FCP_FCT_AD-7.4 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Fortinet FCP_FCT_AD-7.4 Practice Test 28

Question 270

At fictional Summit Agriculture, an endpoint security engineer responsible for rural offices is reviewing endpoint provisioning, security modules and profile delivery during a profile and group recertification (FCT-7.4-2.3-068). The observed endpoint management issue is: A department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. Which observation best verifies that the proposed correction worked?

  1. The event record identifies the filtering decision and a narrowly approved policy resolves the legitimate access.
  2. Newly enrolled devices use current supported registration settings and unauthorized downloads cease.
  3. A test endpoint maintains the intended active malware scanning state after a regular user attempts to disable it.
  4. The authorized application works while unrelated malicious test indicators remain detected in protected locations.

Explanation

Correct Answer

D:

This is the direct verification evidence: The authorized application works while unrelated malicious test indicators remain detected in protected locations. It supports the engineering change to investigate the application conflict and replace global exclusions with narrowly justified supported exceptions. The relevant principle is that overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage.

Incorrect Answers

A:

Evidence that “The event record identifies the filtering decision and a narrowly approved policy resolves the legitimate access” occurred would not by itself establish resolution of the reported problem: a department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. The specific reason is overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage. The applicable verification is “The authorized application works while unrelated malicious test indicators remain detected in protected locations”.

B:

Evidence that “Newly enrolled devices use current supported registration settings and unauthorized downloads cease” occurred would not by itself establish resolution of the reported problem: a department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. The specific reason is overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage. The applicable verification is “The authorized application works while unrelated malicious test indicators remain detected in protected locations”.

C:

Evidence that “A test endpoint maintains the intended active malware scanning state after a regular user attempts to disable it” occurred would not by itself establish resolution of the reported problem: a department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. The specific reason is overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage. The applicable verification is “The authorized application works while unrelated malicious test indicators remain detected in protected locations”.

Question 271

At fictional Summit Agriculture, an endpoint security engineer responsible for rural offices is reviewing endpoint provisioning, security modules and profile delivery during a profile and group recertification (FCT-7.4-2.3-068). The observed endpoint management issue is: A department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. Which corrective engineering action best addresses the specific problem?

  1. Verify FortiClient edition, endpoint operating system, sandbox integration and selected module availability.
  2. Investigate the application conflict and replace global exclusions with narrowly justified supported exceptions.
  3. Confirm enrollment invitation target, group assignment and associated endpoint policy before distribution.
  4. Configure and validate appropriate FortiClient malware protection independently from URL category policy.

Explanation

Correct Answer

B:

The targeted correction is to investigate the application conflict and replace global exclusions with narrowly justified supported exceptions. The diagnosed issue is: A department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. Evidence of success is: The authorized application works while unrelated malicious test indicators remain detected in protected locations. The underlying endpoint-security principle is that overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage.

Incorrect Answers

A:

“Verify FortiClient edition, endpoint operating system, sandbox integration and selected module availability” would address a different implementation objective; the stated problem is a department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. The actual control boundary is overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage. The directly responsive action is “Investigate the application conflict and replace global exclusions with narrowly justified supported exceptions”.

C:

“Confirm enrollment invitation target, group assignment and associated endpoint policy before distribution” would address a different implementation objective; the stated problem is a department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. The actual control boundary is overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage. The directly responsive action is “Investigate the application conflict and replace global exclusions with narrowly justified supported exceptions”.

D:

“Configure and validate appropriate FortiClient malware protection independently from URL category policy” would address a different implementation objective; the stated problem is a department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. The actual control boundary is overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage. The directly responsive action is “Investigate the application conflict and replace global exclusions with narrowly justified supported exceptions”.

Question 272

At fictional Summit Agriculture, an endpoint security engineer responsible for rural offices is reviewing endpoint provisioning, security modules and profile delivery during a profile and group recertification (FCT-7.4-2.3-068). The observed endpoint management issue is: A department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Audit exclusion paths, operational owners and expiry after each software release.
  2. Review malware scan exclusion breadth and usage during quarterly control checks.
  3. Test representative allowed and denied categories after policy publishing.
  4. Expire and rotate onboarding links or packages after significant EMS changes.

Explanation

Correct Answer

A:

The recurring safeguard is to audit exclusion paths, operational owners and expiry after each software release. It mitigates the actual failure: A department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. A suitable correction is to investigate the application conflict and replace global exclusions with narrowly justified supported exceptions; its proof is that the authorized application works while unrelated malicious test indicators remain detected in protected locations.

Incorrect Answers

B:

“Review malware scan exclusion breadth and usage during quarterly control checks” checks a different ongoing risk rather than the reported failure: a department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. The relevant mechanism is overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage. The directly matched preventive control is “Audit exclusion paths, operational owners and expiry after each software release”.

C:

“Test representative allowed and denied categories after policy publishing” checks a different ongoing risk rather than the reported failure: a department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. The relevant mechanism is overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage. The directly matched preventive control is “Audit exclusion paths, operational owners and expiry after each software release”.

D:

“Expire and rotate onboarding links or packages after significant EMS changes” checks a different ongoing risk rather than the reported failure: a department uses broad malware scanning exclusions for a slow application and leaves entire system directories unprotected. The relevant mechanism is overbroad endpoint exclusion patterns can create dangerous gaps in malware coverage. The directly matched preventive control is “Audit exclusion paths, operational owners and expiry after each software release”.

Question 273

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing FortiGate integration, posture tags, ZTNA and containment during a remote access rollout (FCT-7.4-3.1-069). The observed endpoint management issue is: An administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Verify the actual containment scope during incident response tabletop and live tests.
  2. Monitor posture tag age and evaluate disconnected-client failure behavior.
  3. Compare group membership, tag rule and FortiGate match conditions during access review.
  4. Test policy matches with one compliant and one noncompliant endpoint.

Explanation

Correct Answer

D:

The recurring safeguard is to test policy matches with one compliant and one noncompliant endpoint. It mitigates the actual failure: An administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. A suitable correction is to create or select a supported dynamic tag-address object and reference it in the intended firewall rule; its proof is that the resulting policy matches only endpoints currently associated with the approved EMS posture tag.

Incorrect Answers

A:

“Verify the actual containment scope during incident response tabletop and live tests” checks a different ongoing risk rather than the reported failure: an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The relevant mechanism is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The directly matched preventive control is “Test policy matches with one compliant and one noncompliant endpoint”.

B:

“Monitor posture tag age and evaluate disconnected-client failure behavior” checks a different ongoing risk rather than the reported failure: an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The relevant mechanism is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The directly matched preventive control is “Test policy matches with one compliant and one noncompliant endpoint”.

C:

“Compare group membership, tag rule and FortiGate match conditions during access review” checks a different ongoing risk rather than the reported failure: an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The relevant mechanism is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The directly matched preventive control is “Test policy matches with one compliant and one noncompliant endpoint”.

Question 274

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing FortiGate integration, posture tags, ZTNA and containment during a remote access rollout (FCT-7.4-3.1-069). The observed endpoint management issue is: An administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. Which observation best verifies that the proposed correction worked?

  1. Supported endpoint types enforce quarantine and unsupported types receive an alternative containment plan.
  2. The resulting policy matches only endpoints currently associated with the approved EMS posture tag.
  3. FortiGate reflects the changed device posture and its effective access result follows the current tag.
  4. The managed client reaches the permitted application without gaining arbitrary protected subnet reachability.

Explanation

Correct Answer

B:

This is the direct verification evidence: The resulting policy matches only endpoints currently associated with the approved EMS posture tag. It supports the engineering change to create or select a supported dynamic tag-address object and reference it in the intended firewall rule. The relevant principle is that network policy can apply dynamically to endpoint groups only when the tag object is correctly bound.

Incorrect Answers

A:

Evidence that “Supported endpoint types enforce quarantine and unsupported types receive an alternative containment plan” occurred would not by itself establish resolution of the reported problem: an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The specific reason is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The applicable verification is “The resulting policy matches only endpoints currently associated with the approved EMS posture tag”.

C:

Evidence that “FortiGate reflects the changed device posture and its effective access result follows the current tag” occurred would not by itself establish resolution of the reported problem: an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The specific reason is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The applicable verification is “The resulting policy matches only endpoints currently associated with the approved EMS posture tag”.

D:

Evidence that “The managed client reaches the permitted application without gaining arbitrary protected subnet reachability” occurred would not by itself establish resolution of the reported problem: an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The specific reason is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The applicable verification is “The resulting policy matches only endpoints currently associated with the approved EMS posture tag”.

Question 275

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing FortiGate integration, posture tags, ZTNA and containment during a remote access rollout (FCT-7.4-3.1-069). The observed endpoint management issue is: An administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. Which corrective engineering action best addresses the specific problem?

  1. Create or select a supported dynamic tag-address object and reference it in the intended firewall rule.
  2. Identify each Security Fabric component's supported role in endpoint management, logging and event analysis.
  3. Validate the documented Security Fabric topology and authorized EMS integration for participating devices.
  4. Complete the supported mutual authorization steps for the EMS–FortiGate Fabric connector.

Explanation

Correct Answer

A:

The targeted correction is to create or select a supported dynamic tag-address object and reference it in the intended firewall rule. The diagnosed issue is: An administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. Evidence of success is: The resulting policy matches only endpoints currently associated with the approved EMS posture tag. The underlying endpoint-security principle is that network policy can apply dynamically to endpoint groups only when the tag object is correctly bound.

Incorrect Answers

B:

“Identify each Security Fabric component's supported role in endpoint management, logging and event analysis” would address a different implementation objective; the stated problem is an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The actual control boundary is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The directly responsive action is “Create or select a supported dynamic tag-address object and reference it in the intended firewall rule”.

C:

“Validate the documented Security Fabric topology and authorized EMS integration for participating devices” would address a different implementation objective; the stated problem is an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The actual control boundary is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The directly responsive action is “Create or select a supported dynamic tag-address object and reference it in the intended firewall rule”.

D:

“Complete the supported mutual authorization steps for the EMS–FortiGate Fabric connector” would address a different implementation objective; the stated problem is an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The actual control boundary is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The directly responsive action is “Create or select a supported dynamic tag-address object and reference it in the intended firewall rule”.

Question 276

At fictional Maple Housing, an endpoint security engineer responsible for facilities support is reviewing FortiGate integration, posture tags, ZTNA and containment during a remote access rollout (FCT-7.4-3.1-069). The observed endpoint management issue is: An administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. Which endpoint-management or security principle best explains the proper response?

  1. EMS integration is gated by both transport connectivity and device authorization.
  2. Quarantine release should be an accountable incident decision rather than an uncontrolled user workaround.
  3. Network policy can apply dynamically to endpoint groups only when the tag object is correctly bound.
  4. EMS posture evaluation and FortiGate enforcement require correctly synchronized attribute data.

Explanation

Correct Answer

C:

The governing principle is: Network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. Here the appropriate correction is to create or select a supported dynamic tag-address object and reference it in the intended firewall rule. Confirmation would be that the resulting policy matches only endpoints currently associated with the approved EMS posture tag.

Incorrect Answers

A:

“EMS integration is gated by both transport connectivity and device authorization” is not the controlling explanation for an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The cited causal relationship is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The matching answer is “Network policy can apply dynamically to endpoint groups only when the tag object is correctly bound”.

B:

“Quarantine release should be an accountable incident decision rather than an uncontrolled user workaround” is not the controlling explanation for an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The cited causal relationship is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The matching answer is “Network policy can apply dynamically to endpoint groups only when the tag object is correctly bound”.

D:

“EMS posture evaluation and FortiGate enforcement require correctly synchronized attribute data” is not the controlling explanation for an administrator tries to apply a posture-based firewall rule before selecting the EMS-derived tag category in FortiOS. The cited causal relationship is network policy can apply dynamically to endpoint groups only when the tag object is correctly bound. The matching answer is “Network policy can apply dynamically to endpoint groups only when the tag object is correctly bound”.

Question 277

At fictional Ironbridge Utilities, an endpoint security engineer responsible for remote engineers is reviewing endpoint provisioning, security modules and profile delivery during a Security Fabric integration test (FCT-7.4-2.1-070). The observed endpoint management issue is: An engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. Which endpoint-management or security principle best explains the proper response?

  1. Profile-based policy exceptions should be scoped to the smallest affected user or resource population.
  2. Module availability is constrained by product version, operating system and licensing.
  3. Missing scan observations do not demonstrate the absence of vulnerabilities.
  4. Endpoint software packaging and installation requirements differ across operating system platforms.

Explanation

Correct Answer

B:

The governing principle is: Module availability is constrained by product version, operating system and licensing. Here the appropriate correction is to review supported platform modules, target licensing and deployment-package options before publishing. Confirmation would be that test devices show only valid selected modules without installation errors or missing entitlement.

Incorrect Answers

A:

“Profile-based policy exceptions should be scoped to the smallest affected user or resource population” is not the controlling explanation for an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The cited causal relationship is module availability is constrained by product version, operating system and licensing. The matching answer is “Module availability is constrained by product version, operating system and licensing”.

C:

“Missing scan observations do not demonstrate the absence of vulnerabilities” is not the controlling explanation for an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The cited causal relationship is module availability is constrained by product version, operating system and licensing. The matching answer is “Module availability is constrained by product version, operating system and licensing”.

D:

“Endpoint software packaging and installation requirements differ across operating system platforms” is not the controlling explanation for an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The cited causal relationship is module availability is constrained by product version, operating system and licensing. The matching answer is “Module availability is constrained by product version, operating system and licensing”.

Question 278

At fictional Ironbridge Utilities, an endpoint security engineer responsible for remote engineers is reviewing endpoint provisioning, security modules and profile delivery during a Security Fabric integration test (FCT-7.4-2.1-070). The observed endpoint management issue is: An engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. Which observation best verifies that the proposed correction worked?

  1. The needed workflow works on authorized devices without exposing other asset groups to the exclusion.
  2. Authorized devices register under the intended group while unapproved devices do not gain managed access.
  3. Test devices show only valid selected modules without installation errors or missing entitlement.
  4. Agent versions shown in EMS match the supported management release and operate under assigned policy.

Explanation

Correct Answer

C:

This is the direct verification evidence: Test devices show only valid selected modules without installation errors or missing entitlement. It supports the engineering change to review supported platform modules, target licensing and deployment-package options before publishing. The relevant principle is that module availability is constrained by product version, operating system and licensing.

Incorrect Answers

A:

Evidence that “The needed workflow works on authorized devices without exposing other asset groups to the exclusion” occurred would not by itself establish resolution of the reported problem: an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The specific reason is module availability is constrained by product version, operating system and licensing. The applicable verification is “Test devices show only valid selected modules without installation errors or missing entitlement”.

B:

Evidence that “Authorized devices register under the intended group while unapproved devices do not gain managed access” occurred would not by itself establish resolution of the reported problem: an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The specific reason is module availability is constrained by product version, operating system and licensing. The applicable verification is “Test devices show only valid selected modules without installation errors or missing entitlement”.

D:

Evidence that “Agent versions shown in EMS match the supported management release and operate under assigned policy” occurred would not by itself establish resolution of the reported problem: an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The specific reason is module availability is constrained by product version, operating system and licensing. The applicable verification is “Test devices show only valid selected modules without installation errors or missing entitlement”.

Question 279

At fictional Ironbridge Utilities, an endpoint security engineer responsible for remote engineers is reviewing endpoint provisioning, security modules and profile delivery during a Security Fabric integration test (FCT-7.4-2.1-070). The observed endpoint management issue is: An engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. Which recurring preventive or detective safeguard would best reduce recurrence?

  1. Maintain feature-versus-platform validation tests for each installer package.
  2. Audit DNS names, destination ports and scope in every ZTNA endpoint profile.
  3. Maintain an operating-system compatibility inventory for all remote deployment packages.
  4. Revalidate embedded EMS registration values whenever management service names change.

Explanation

Correct Answer

A:

The recurring safeguard is to maintain feature-versus-platform validation tests for each installer package. It mitigates the actual failure: An engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. A suitable correction is to review supported platform modules, target licensing and deployment-package options before publishing; its proof is that test devices show only valid selected modules without installation errors or missing entitlement.

Incorrect Answers

B:

“Audit DNS names, destination ports and scope in every ZTNA endpoint profile” checks a different ongoing risk rather than the reported failure: an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The relevant mechanism is module availability is constrained by product version, operating system and licensing. The directly matched preventive control is “Maintain feature-versus-platform validation tests for each installer package”.

C:

“Maintain an operating-system compatibility inventory for all remote deployment packages” checks a different ongoing risk rather than the reported failure: an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The relevant mechanism is module availability is constrained by product version, operating system and licensing. The directly matched preventive control is “Maintain feature-versus-platform validation tests for each installer package”.

D:

“Revalidate embedded EMS registration values whenever management service names change” checks a different ongoing risk rather than the reported failure: an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The relevant mechanism is module availability is constrained by product version, operating system and licensing. The directly matched preventive control is “Maintain feature-versus-platform validation tests for each installer package”.

Question 280

At fictional Ironbridge Utilities, an endpoint security engineer responsible for remote engineers is reviewing endpoint provisioning, security modules and profile delivery during a Security Fabric integration test (FCT-7.4-2.1-070). The observed endpoint management issue is: An engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. Which corrective engineering action best addresses the specific problem?

  1. Correct the approved protected-application destination and synchronize the relevant profile to endpoint groups.
  2. Use the supported FortiClient upgrade package and test retained management configuration before mass deployment.
  3. Rebuild the authorized EMS deployment package with the licensed and supported security modules required for students.
  4. Review supported platform modules, target licensing and deployment-package options before publishing.

Explanation

Correct Answer

D:

The targeted correction is to review supported platform modules, target licensing and deployment-package options before publishing. The diagnosed issue is: An engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. Evidence of success is: Test devices show only valid selected modules without installation errors or missing entitlement. The underlying endpoint-security principle is that module availability is constrained by product version, operating system and licensing.

Incorrect Answers

A:

“Correct the approved protected-application destination and synchronize the relevant profile to endpoint groups” would address a different implementation objective; the stated problem is an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The actual control boundary is module availability is constrained by product version, operating system and licensing. The directly responsive action is “Review supported platform modules, target licensing and deployment-package options before publishing”.

B:

“Use the supported FortiClient upgrade package and test retained management configuration before mass deployment” would address a different implementation objective; the stated problem is an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The actual control boundary is module availability is constrained by product version, operating system and licensing. The directly responsive action is “Review supported platform modules, target licensing and deployment-package options before publishing”.

C:

“Rebuild the authorized EMS deployment package with the licensed and supported security modules required for students” would address a different implementation objective; the stated problem is an engineering team includes mutually incompatible or unsupported FortiClient features in a deployment package for a device class. The actual control boundary is module availability is constrained by product version, operating system and licensing. The directly responsive action is “Review supported platform modules, target licensing and deployment-package options before publishing”.

Fortinet NSE 6 - FortiClient EMS 7.4 Administrator (FCP_FCT_AD-7.4) Practice Tests