Fortinet FCP_FCT_AD-7.4 Practice Test 38
Question 370
A FortiClient EMS administrator prepares a focused response to this scenario. A false-positive detection triggers a request to isolate a critical medication kiosk without checking business-impact safeguards. Which TWO complementary steps combine the most appropriate action and direct verification? Select TWO answers.
- Use a supported endpoint response control only after identifying a verified threat and the intended scope of isolation.
- Review the denied session's FortiGate event, matched policy, EMS device tag and supported endpoint certificate or service checks.
- Compare endpoint platform, exact FortiClient release, supported remediation options and incident playbook expectations.
- Check old and target versions, upgrade-path support, pre-upgrade backups, migration logs and post-upgrade pilot Telemetry.
- Review alert evidence, affected device identity, operator approval and local/remote quarantine state before and after the action.
Explanation
Correct Answers
A:The targeted next step is: Use a supported endpoint response control only after identifying a verified threat and the intended scope of isolation.
E:The discriminating evidence is: Review alert evidence, affected device identity, operator approval and local/remote quarantine state before and after the action.
Incorrect Answers
B:This evidence belongs to the distinct FortiClient EMS topic ZTNA application access denial event correlation, not the case-specific issue of Malware quarantine versus general network isolation scope described here (A false-positive detection triggers a request to isolate a critical medication kiosk without checking business-impact safeguards.).
C:This evidence belongs to the distinct FortiClient EMS topic Unsupported-platform quarantine caveat, not the case-specific issue of Malware quarantine versus general network isolation scope described here (A false-positive detection triggers a request to isolate a critical medication kiosk without checking business-impact safeguards.).
D:This evidence belongs to the distinct FortiClient EMS topic FortiClient EMS upgrade path and version migration, not the case-specific issue of Malware quarantine versus general network isolation scope described here (A false-positive detection triggers a request to isolate a critical medication kiosk without checking business-impact safeguards.).
Question 371
A FortiClient EMS 7.4 administrator investigates this endpoint management case: A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
- Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
- Select a supported endpoint distribution workflow and verify installer execution and post-install EMS enrollment as separate stages.
- Investigate the exact matched endpoint web-filter category and create an approved narrow exception when warranted.
Explanation
Correct Answer
B:The targeted next step is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions. The supporting FortiClient EMS principle is: Sandbox detection can provide a malware verdict, but only supported integration, module configuration and response policy turn that verdict into endpoint action.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic FortiClient endpoint Telemetry event chronology, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
C:This action belongs to the distinct FortiClient EMS topic FortiClient endpoint installation through managed distribution, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
D:This action belongs to the distinct FortiClient EMS topic Web Filter exceptions for business-critical sites, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Question 372
An endpoint security reviewer examines this scenario. A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured. The proposed action is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions. Which technical principle BEST supports that decision? Select ONE best answer.
- EMS stores separate profiles for functions such as Remote Access, Web Filter and Malware Protection; endpoint policies select the applicable combination.
- Endpoint quarantine changes local traffic behavior and may block normal applications, so an operator must verify scope and platform support.
- Sandbox detection can provide a malware verdict, but only supported integration, module configuration and response policy turn that verdict into endpoint action.
- A response API must correlate the FortiGate observation to the endpoint registered with EMS so that the correct host is isolated.
Explanation
Correct Answer
C:Sandbox detection can provide a malware verdict, but only supported integration, module configuration and response policy turn that verdict into endpoint action. Applied to this case (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.), it supports the controlled action: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Incorrect Answers
A:This principle belongs to the distinct FortiClient EMS topic Endpoint profile combination through EMS endpoint policies, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
B:This principle belongs to the distinct FortiClient EMS topic Endpoint quarantine state and data-plane effects, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
D:This principle belongs to the distinct FortiClient EMS topic Quarantine endpoint identity and device lookup, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Question 373
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured. 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.
- Review the local filtering event, profile identifier, domain category and business authorization for an exception.
- Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act.
- Compare intended rule criteria, client OS/process state, received tag event, group membership and FortiOS tag status.
Explanation
Correct Answer
C:The discriminating evidence is: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act. For the reported situation (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.), it should establish: Suspicious content is analyzed under approved controls and resulting protection decisions have traceable evidence.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic FortiClient platform capability differences, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.).
B:This evidence belongs to the distinct FortiClient EMS topic Web Filter exceptions for business-critical sites, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.).
D:This evidence belongs to the distinct FortiClient EMS topic Dynamic group posture rule mismatch troubleshooting, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.).
Question 374
An endpoint administrator must verify that a configuration change achieved its goal. A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured. The proposed validation is: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- Registration succeeds with a valid trusted server identity without disabling transport verification.
- An endpoint can re-establish its approved management connection after a documented EMS node failure.
- Suspicious content is analyzed under approved controls and resulting protection decisions have traceable evidence.
- Administrators can operate EMS through approved channels while unnecessary external management exposure remains closed.
Explanation
Correct Answer
C:The intended acceptance criterion is: Suspicious content is analyzed under approved controls and resulting protection decisions have traceable evidence. Confirm it through: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act.
Incorrect Answers
A:That option concerns Certificate handshake and trust chain failures. The associated corrective action is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
B:That option concerns EMS resilience and high availability architecture. The associated corrective action is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
D:That option concerns EMS server configuration and secure administrator access. The associated corrective action is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Question 375
A security operations reviewer evaluates an unsafe configuration shortcut in this case. A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured. Which assumption is MOST DIRECTLY relevant to reject? Select ONE best answer.
- Assume an external sandbox verdict automatically deletes every matching file without an endpoint policy or supported integration.
- Investigate the exact matched endpoint web-filter category and create an approved narrow exception when warranted.
- Distinguish the EMS server's policy and inventory role from the local FortiClient agent's enforcement before changing endpoint configurations.
- Require documented remediation and explicit approval before releasing a managed endpoint from quarantine.
Explanation
Correct Answer
A:It conflicts with the technical behavior: Sandbox detection can provide a malware verdict, but only supported integration, module configuration and response policy turn that verdict into endpoint action.
Incorrect Answers
B:This action belongs to the distinct FortiClient EMS topic Web Filter exceptions for business-critical sites, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions. Verify it through: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act.
C:This action belongs to the distinct FortiClient EMS topic EMS management plane versus FortiClient endpoint agent, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
D:This action belongs to the distinct FortiClient EMS topic Quarantine release approval and incident preservation, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (A workstation uploads a suspicious document for analysis but receives no actionable verdict because its sandbox integration is misconfigured.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Question 376
A FortiClient EMS 7.4 administrator investigates this endpoint management case: An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Set FortiClient system options in EMS so endpoint users retain only the self-service capabilities approved by policy.
- Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
- Evaluate EMS endpoint policy matching and priority before changing settings when devices belong to overlapping groups.
- Use current EMS security posture tags in an appropriately scoped FortiOS dynamic address group and firewall policy.
Explanation
Correct Answer
B:The targeted next step is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions. The supporting FortiClient EMS principle is: Sandbox detection can provide a malware verdict, but only supported integration, module configuration and response policy turn that verdict into endpoint action. Verify this by: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic System Settings profile and controlled endpoint self-service, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
C:This action belongs to the distinct FortiClient EMS topic Endpoint policy precedence and assignment conflicts, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
D:This action belongs to the distinct FortiClient EMS topic Dynamic firewall policies driven by EMS security posture tags, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Question 377
An endpoint security reviewer examines this scenario. An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response. The proposed action is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions. 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.
- An endpoint's effective configuration follows the supported policy matching behavior; multiple group memberships cannot be resolved by guessing.
- An EMS enrolled endpoint may not expose a given feature because its entitlement or deployment package differs from the expected profile.
- Sandbox detection can provide a malware verdict, but only supported integration, module configuration and response policy turn that verdict into endpoint action.
Explanation
Correct Answer
D:Sandbox detection can provide a malware verdict, but only supported integration, module configuration and response policy turn that verdict into endpoint action. Applied to this case (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.), it supports the controlled action: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
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 Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
B:This principle belongs to the distinct FortiClient EMS topic Endpoint policy precedence and assignment conflicts, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
C:This principle belongs to the distinct FortiClient EMS topic Licensing and managed feature entitlement diagnosis, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Question 378
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Inspect the endpoint's EMS status, entitlement, installed modules and policy before attempting to repair the application.
- Review the supported EMS HA architecture, failover endpoint hostname, database role and a controlled failover test.
- Trace one endpoint's received EMS policy, posture tag and matching FortiGate decision for a test application flow.
- Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act.
Explanation
Correct Answer
D:The discriminating evidence is: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act. For the reported situation (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.), it should establish: Suspicious content is analyzed under approved controls and resulting protection decisions have traceable evidence.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic Endpoint license and EMS provisioned features, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.).
B:This evidence belongs to the distinct FortiClient EMS topic EMS resilience and high availability architecture, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.).
C:This evidence belongs to the distinct FortiClient EMS topic Endpoint management versus FortiGate enforcement boundary, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.).
Question 379
An endpoint administrator must verify that a configuration change achieved its goal. An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response. The proposed validation is: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- The intended policy wins for each test endpoint and conflicts are resolved explicitly rather than through broad changes.
- Suspicious content is analyzed under approved controls and resulting protection decisions have traceable evidence.
- The missing feature is accounted for by a verified entitlement or installation condition rather than guessed protocol failure.
- Pilot clients connect consistently to the same approved management identity from each supported network location.
Explanation
Correct Answer
B:The intended acceptance criterion is: Suspicious content is analyzed under approved controls and resulting protection decisions have traceable evidence. Confirm it through: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act. The associated corrective action is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Incorrect Answers
A:That option concerns Endpoint policy precedence and assignment conflicts. The associated corrective action is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
C:That option concerns Licensing and managed feature entitlement diagnosis. The associated corrective action is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
D:That option concerns EMS initial network identity and DNS reachability. The associated corrective action is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Question 380
A FortiClient EMS administrator prepares a focused response to this scenario. An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response. Which TWO complementary steps combine the most appropriate action and direct verification? Select TWO answers.
- Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act.
- Compare configured management interfaces, remote access controls, permitted source networks and successful authorized admin logins.
- Set FortiClient system options in EMS so endpoint users retain only the self-service capabilities approved by policy.
- Enable supported Malware Protection controls and validate real signature or engine update health before relying on scan status.
- Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Explanation
Correct Answers
A:The discriminating evidence is: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act.
E:The targeted next step is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
Incorrect Answers
B:This evidence belongs to the distinct FortiClient EMS topic EMS server configuration and secure administrator access, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.).
C:This action belongs to the distinct FortiClient EMS topic System Settings profile and controlled endpoint self-service, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions. Verify it through: Inspect the Sandbox profile and connector state, sample event, returned verdict and whether the assigned endpoint profile can act.
D:This action belongs to the distinct FortiClient EMS topic Malware Protection settings and signature update lifecycle, not the case-specific issue of FortiClient Sandbox integration and detection handoff described here (An endpoint reports malware after a sandbox result, yet administrators cannot identify which security module produced the response.). The targeted action for this case is: Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.