Fortinet FCP_FCT_AD-7.4 Practice Test 10
Question 90
A FortiClient EMS administrator prepares a focused response to this scenario. A security team buys endpoint licenses but distributes an installer lacking the protection module it expects users to see. Which TWO complementary steps combine the most appropriate action and direct verification? Select TWO answers.
- Check licensing and the installed deployment modules before concluding that a missing FortiClient protection feature is a technical defect.
- Check certificate assignment, validity, issuing chain, revocation state and a controlled client-to-FortiGate connection.
- Inspect the endpoint's EMS status, entitlement, installed modules and policy before attempting to repair the application.
- Review the agent's running protection components, signature age, FortiGuard update reachability and safe test detection logs.
- Correlate the detected IoC, analyzer event, FortiGate trigger, EMS endpoint identifier and response status.
Explanation
Correct Answers
A:The targeted next step is: Check licensing and the installed deployment modules before concluding that a missing FortiClient protection feature is a technical defect.
C:The discriminating evidence is: Inspect the endpoint's EMS status, entitlement, installed modules and policy before attempting to repair the application.
Incorrect Answers
B:This evidence belongs to the distinct FortiClient EMS topic ZTNA device certificates and endpoint authentication chain, not the case-specific issue of Endpoint license and EMS provisioned features described here (A security team buys endpoint licenses but distributes an installer lacking the protection module it expects users to see.).
D:This evidence belongs to the distinct FortiClient EMS topic Malware Protection settings and signature update lifecycle, not the case-specific issue of Endpoint license and EMS provisioned features described here (A security team buys endpoint licenses but distributes an installer lacking the protection module it expects users to see.).
E:This evidence belongs to the distinct FortiClient EMS topic Quarantine triggers from validated security indicators, not the case-specific issue of Endpoint license and EMS provisioned features described here (A security team buys endpoint licenses but distributes an installer lacking the protection module it expects users to see.). The targeted action for this case is: Check licensing and the installed deployment modules before concluding that a missing FortiClient protection feature is a technical defect. Verify it through: Inspect the endpoint's EMS status, entitlement, installed modules and policy before attempting to repair the application.
Question 91
A FortiClient EMS 7.4 administrator investigates this endpoint management case: An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Evaluate EMS endpoint policy matching and priority before changing settings when devices belong to overlapping groups.
- Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
- Renew or reissue supported enrollment certificates through an authorized managed workflow rather than bypassing ZTNA device authentication.
- Review management interface exposure, administration access controls and required endpoint-control settings before enrolling a pilot fleet.
Explanation
Correct Answer
B:The targeted next step is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint. The supporting FortiClient EMS principle is: FortiClient feature support and policy enforcement can differ across Windows, macOS and Linux, so a universal profile assumption is unsafe.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic Endpoint policy precedence and assignment conflicts, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
C:This action belongs to the distinct FortiClient EMS topic Client certificate expiration and enrollment recovery, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
D:This action belongs to the distinct FortiClient EMS topic EMS server configuration and secure administrator access, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Question 92
An endpoint security reviewer examines this scenario. An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear. The proposed action is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint. Which technical principle BEST supports that decision? Select ONE best answer.
- Installed feature modules are defined during client deployment and must be considered alongside later EMS policy provisioning.
- Sandbox detection can provide a malware verdict, but only supported integration, module configuration and response policy turn that verdict into endpoint action.
- FortiClient feature support and policy enforcement can differ across Windows, macOS and Linux, so a universal profile assumption is unsafe.
- Endpoint grouping provides administrative and policy targeting; incorrect membership can apply an unrelated restriction or leave devices unprotected.
Explanation
Correct Answer
C:FortiClient feature support and policy enforcement can differ across Windows, macOS and Linux, so a universal profile assumption is unsafe. Applied to this case (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.), it supports the controlled action: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Incorrect Answers
A:This principle belongs to the distinct FortiClient EMS topic EMS-created FortiClient deployment packages and feature modules, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
B:This principle belongs to the distinct FortiClient EMS topic FortiClient Sandbox integration and detection handoff, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
D:This principle belongs to the distinct FortiClient EMS topic Endpoint grouping by inventory attributes and organizational scope, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Question 93
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Review installer return codes, endpoint event logs, current FortiClient version, pending reboot and package execution context.
- Check old and target versions, upgrade-path support, pre-upgrade backups, migration logs and post-upgrade pilot Telemetry.
- Compare the delivered System Settings profile, local UI controls, admin policy and a controlled user attempt to change a setting.
- Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform.
Explanation
Correct Answer
D:For the reported situation (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.), it should establish: The supported controls operate where expected, and unsupported features are clearly documented rather than silently treated as failures.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic FortiClient installation retries and endpoint reboot coordination, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.).
B:This evidence belongs to the distinct FortiClient EMS topic FortiClient EMS upgrade path and version migration, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.).
C:This evidence belongs to the distinct FortiClient EMS topic System Settings profile and controlled endpoint self-service, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.).
Question 94
An endpoint administrator must verify that a configuration change achieved its goal. An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear. The proposed validation is: Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- The supported controls operate where expected, and unsupported features are clearly documented rather than silently treated as failures.
- Users can access permitted functions without disabling enforced security modules or management enrollment.
- Known software issues are identified, assigned to owners and reduced in follow-up scans.
- Changes can be tied to authorized accounts and the management service remains healthy after each maintenance window.
Explanation
Correct Answer
A:The intended acceptance criterion is: The supported controls operate where expected, and unsupported features are clearly documented rather than silently treated as failures. Confirm it through: Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform.
Incorrect Answers
B:That option concerns System Settings profile and controlled endpoint self-service. The associated corrective action is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
C:That option concerns Vulnerability Scan profiles and remediation priorities. The associated corrective action is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
D:That option concerns EMS patching administration and operational audit. The associated corrective action is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Question 95
A security operations reviewer evaluates an unsafe configuration shortcut in this case. An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear. Which assumption is MOST DIRECTLY relevant to reject? Select ONE best answer.
- Validate the health of the EMS application service and its database separately when management state or inventory becomes inconsistent.
- Assume every FortiClient feature and remote response action works identically on Windows, macOS and Linux.
- Use a supported endpoint response control only after identifying a verified threat and the intended scope of isolation.
- Create EMS security posture tag rules using defensible checks such as operating system, domain membership and required running processes.
Explanation
Correct Answer
B:It conflicts with the technical behavior: FortiClient feature support and policy enforcement can differ across Windows, macOS and Linux, so a universal profile assumption is unsafe.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic FortiClient EMS server and database component boundaries, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
C:This action belongs to the distinct FortiClient EMS topic Malware quarantine versus general network isolation scope, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
D:This action belongs to the distinct FortiClient EMS topic ZTNA posture tag rules and evaluation inputs, not the case-specific issue of FortiClient platform capability differences described here (An administrator copies a Windows-only remediation design to a Linux group and is surprised that the control does not appear.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Question 96
A FortiClient EMS 7.4 administrator investigates this endpoint management case: A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Stage a representative pilot of FortiClient registration, profile enforcement, Fabric integration and change rollback before broad rollout.
- Examine posture tag criteria and fresh endpoint facts before granting a compliant group to a device that failed the rule.
- Compare FortiGate EMS connector health with server-side Fabric Devices authorization when dynamic endpoint tags are unavailable.
- Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Explanation
Correct Answer
D:The targeted next step is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint. The supporting FortiClient EMS principle is: FortiClient feature support and policy enforcement can differ across Windows, macOS and Linux, so a universal profile assumption is unsafe. Verify this by: Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic Controlled EMS initial pilot and rollback decision, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
B:This action belongs to the distinct FortiClient EMS topic Dynamic group posture rule mismatch troubleshooting, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
C:This action belongs to the distinct FortiClient EMS topic FortiGate Fabric connector diagnostic state, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Question 97
An endpoint security reviewer examines this scenario. A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS. The proposed action is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint. Which technical principle BEST supports that decision? Select ONE best answer.
- EMS inventory and entitlements depend on actual managed devices; stale records and reused hostnames can distort policy targeting.
- FortiClient feature support and policy enforcement can differ across Windows, macOS and Linux, so a universal profile assumption is unsafe.
- Dynamic tags, static groups and policy ordering can change the effective endpoint configuration independently of the profile's contents.
- FortiClient evaluates rules on endpoints and communicates results to EMS, which can use them for dynamic grouping and downstream access policy.
Explanation
Correct Answer
B:FortiClient feature support and policy enforcement can differ across Windows, macOS and Linux, so a universal profile assumption is unsafe. Applied to this case (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.), it supports the controlled action: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Incorrect Answers
A:This principle belongs to the distinct FortiClient EMS topic Controlled endpoint onboarding and deprovisioning lifecycle, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
C:This principle belongs to the distinct FortiClient EMS topic Profile assignment and unexpected group membership diagnosis, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
D:This principle belongs to the distinct FortiClient EMS topic Security posture tagging from operating-system facts, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.). The targeted action for this case is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Question 98
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform.
- Compare delivered Remote Access profile, server certificate, gateway address, authentication outcome and a controlled VPN connection.
- Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes.
- Review host OS/build, CPU and storage, administrator rights, required components and preflight installer logs.
Explanation
Correct Answer
A:The discriminating evidence is: Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform. For the reported situation (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.), it should establish: The supported controls operate where expected, and unsupported features are clearly documented rather than silently treated as failures.
Incorrect Answers
B:This evidence belongs to the distinct FortiClient EMS topic Remote Access profile parameters and user authentication, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.).
C:This evidence belongs to the distinct FortiClient EMS topic FortiClient endpoint Telemetry event chronology, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.).
D:This evidence belongs to the distinct FortiClient EMS topic Installation prerequisites and supported server operating systems, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.).
Question 99
An endpoint administrator must verify that a configuration change achieved its goal. A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS. The proposed validation is: Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- The supported controls operate where expected, and unsupported features are clearly documented rather than silently treated as failures.
- Only the true blocking layer is changed and unrelated protection remains enforced.
- The investigation identifies the actual Telemetry failure stage rather than resetting a healthy client without cause.
- Registration succeeds with a valid trusted server identity without disabling transport verification.
Explanation
Correct Answer
A:The intended acceptance criterion is: The supported controls operate where expected, and unsupported features are clearly documented rather than silently treated as failures. Confirm it through: Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform. The associated corrective action is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Incorrect Answers
B:That option concerns Network versus endpoint protection event distinctions. The associated corrective action is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
C:That option concerns FortiClient endpoint Telemetry event chronology. The associated corrective action is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
D:That option concerns Certificate handshake and trust chain failures. The associated corrective action is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Question 100
An endpoint security operations team needs a controlled Fortinet response and proof of its result. A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS. Which THREE complementary steps provide the best response, direct diagnostic evidence and a measurable success condition? Select THREE answers.
- Inspect certificate validity, EMS registration status, trust chain and a controlled ZTNA device verification attempt.
- Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform.
- The supported controls operate where expected, and unsupported features are clearly documented rather than silently treated as failures.
- Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
- Inspect EMS quarantine state, endpoint response, FortiGate status and representative permitted/denied network traffic.
- Inspect the local Firewall profile, rule match, application test flow and relevant endpoint event logs.
Explanation
Correct Answers
B:The discriminating evidence is: Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform.
C:Confirm it through: Inspect the OS, FortiClient build, official platform feature matrix and a representative enforced setting per platform.
D:The targeted next step is: Match EMS policy and deployment features to the operating system and FortiClient release actually installed on each endpoint.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic Client certificate expiration and enrollment recovery, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.).
E:This evidence belongs to the distinct FortiClient EMS topic Endpoint quarantine state and data-plane effects, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.).
F:This evidence belongs to the distinct FortiClient EMS topic FortiClient host firewall profile placement, not the case-specific issue of FortiClient platform capability differences described here (A mixed-device deployment assigns one package to all employees without checking whether a needed client security module exists on macOS.).