Fortinet FCP_FCT_AD-7.4 Practice Test 61
Question 600
An endpoint security operations team needs a controlled Fortinet response and proof of its result. A contractor with an invalid device certificate asks for unrestricted VPN access because a ZTNA app returns access denied. Which THREE complementary steps provide the best response, direct diagnostic evidence and a measurable success condition? Select THREE answers.
- Collect the gateway authentication event, endpoint certificate state, EMS tag, matched access-proxy rule and backend reachability.
- The exact failing control is corrected without opening unrelated internal applications or weakening all users' posture requirements.
- Investigate denied ZTNA traffic by separately checking user authentication, device identity, posture result and backend service route.
- Use current EMS security posture tags in an appropriately scoped FortiOS dynamic address group and firewall policy.
- Compare delivered Remote Access profile, server certificate, gateway address, authentication outcome and a controlled VPN connection.
- Review tenant or site assignments, administrator scope and a test endpoint's effective policy without moving unrelated users.
Explanation
Correct Answers
A:The discriminating evidence is: Collect the gateway authentication event, endpoint certificate state, EMS tag, matched access-proxy rule and backend reachability.
B:Confirm it through: Collect the gateway authentication event, endpoint certificate state, EMS tag, matched access-proxy rule and backend reachability.
C:The targeted next step is: Investigate denied ZTNA traffic by separately checking user authentication, device identity, posture result and backend service route.
Incorrect Answers
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 ZTNA access-denial evidence and least-privilege diagnosis described here (A contractor with an invalid device certificate asks for unrestricted VPN access because a ZTNA app returns access denied.). The targeted action for this case is: Investigate denied ZTNA traffic by separately checking user authentication, device identity, posture result and backend service route.
E:This evidence belongs to the distinct FortiClient EMS topic Remote Access profile parameters and user authentication, not the case-specific issue of ZTNA access-denial evidence and least-privilege diagnosis described here (A contractor with an invalid device certificate asks for unrestricted VPN access because a ZTNA app returns access denied.).
F:This evidence belongs to the distinct FortiClient EMS topic EMS tenant and site isolation in shared deployments, not the case-specific issue of ZTNA access-denial evidence and least-privilege diagnosis described here (A contractor with an invalid device certificate asks for unrestricted VPN access because a ZTNA app returns access denied.).
Question 601
A FortiClient EMS 7.4 administrator investigates this endpoint management case: A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving. 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.
- Size the FortiClient EMS service and supporting storage for enrolled endpoint volume, log growth and planned management operations.
- Check the FortiClient operating system and documented quarantine capability before promising endpoint self-isolation.
- Use a supported endpoint response control only after identifying a verified threat and the intended scope of isolation.
Explanation
Correct Answer
A:The targeted next step is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged. The supporting FortiClient EMS principle is: Endpoint connection logs can distinguish network failure, authentication refusal, deliberate deregistration and temporary service interruption.
Incorrect Answers
B:This action belongs to the distinct FortiClient EMS topic EMS server performance planning for endpoint count, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
C:This action belongs to the distinct FortiClient EMS topic Unsupported-platform quarantine caveat, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
D:This action belongs to the distinct FortiClient EMS topic Malware quarantine versus general network isolation scope, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Question 602
An endpoint security reviewer examines this scenario. A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving. The proposed action is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged. Which technical principle BEST supports that decision? Select ONE best answer.
- A response action such as EMS quarantine changes endpoint connectivity and can disrupt legitimate applications, so authorization and recovery are essential.
- Endpoint connection logs can distinguish network failure, authentication refusal, deliberate deregistration and temporary service interruption.
- An EMS-managed endpoint can receive locked configuration while some user actions may remain available according to profile and feature support.
- A response API must correlate the FortiGate observation to the endpoint registered with EMS so that the correct host is isolated.
Explanation
Correct Answer
B:Endpoint connection logs can distinguish network failure, authentication refusal, deliberate deregistration and temporary service interruption. Applied to this case (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.), it supports the controlled action: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Incorrect Answers
A:This principle belongs to the distinct FortiClient EMS topic Malware quarantine versus general network isolation scope, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
C:This principle belongs to the distinct FortiClient EMS topic System Settings profile and controlled endpoint self-service, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
D:This principle belongs to the distinct FortiClient EMS topic Quarantine endpoint identity and device lookup, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Question 603
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Inventory reachable endpoints, management routing, hosted service access and ownership of the management infrastructure.
- Inspect endpoint UID, current IP, registration state, posture status, connector synchronization and the FortiGate matched policy.
- Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes.
- Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access.
Explanation
Correct Answer
C:The discriminating evidence is: Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes. For the reported situation (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.), it should establish: The investigation identifies the actual Telemetry failure stage rather than resetting a healthy client without cause.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic FortiClient EMS on-premises and cloud placement, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.).
B:This evidence belongs to the distinct FortiClient EMS topic Endpoint identity correlation across EMS and FortiGate, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.).
D:This evidence belongs to the distinct FortiClient EMS topic Security posture tagging from operating-system facts, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.).
Question 604
An endpoint administrator must verify that a configuration change achieved its goal. A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving. The proposed validation is: Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- The investigation identifies the actual Telemetry failure stage rather than resetting a healthy client without cause.
- Only intended endpoints enroll and unauthorized devices do not gain the team's managed security configuration.
- The upgraded EMS retains inventory, effective policies and valid endpoint communication with a documented rollback plan.
- Compliant managed devices receive the intended tag and ineligible devices remain outside the privileged group.
Explanation
Correct Answer
A:The intended acceptance criterion is: The investigation identifies the actual Telemetry failure stage rather than resetting a healthy client without cause. Confirm it through: Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes.
Incorrect Answers
B:This outcome belongs to the distinct FortiClient EMS topic FortiClient registration invitations and enrollment identity, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
C:This outcome belongs to the distinct FortiClient EMS topic FortiClient EMS upgrade path and version migration, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
D:That option concerns Security posture tagging from operating-system facts. The associated corrective action is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Question 605
A security operations reviewer evaluates an unsafe configuration shortcut in this case. A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving. Which assumption is MOST DIRECTLY relevant to reject? Select ONE best answer.
- Assume every disconnected client was manually deregistered without examining its latest endpoint event log.
- Verify DNS, gateway and required supported management service connectivity from a failing client before reinstalling FortiClient.
- Configure an access proxy that maps an explicitly allowed application destination to the correct ZTNA policy and authenticated context.
- Establish an auditable process to register replacement endpoints and retire decommissioned ones from EMS without confusing their identities.
Explanation
Correct Answer
A:It conflicts with the technical behavior: Endpoint connection logs can distinguish network failure, authentication refusal, deliberate deregistration and temporary service interruption.
Incorrect Answers
B:This action belongs to the distinct FortiClient EMS topic Remote EMS registration and DNS path failures, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
C:This action belongs to the distinct FortiClient EMS topic FortiGate ZTNA access proxy and application mapping, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
D:This action belongs to the distinct FortiClient EMS topic Controlled endpoint onboarding and deprovisioning lifecycle, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (A remote agent was online yesterday but now displays an EMS disconnect after its management hostname stopped resolving.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Question 606
A FortiClient EMS 7.4 administrator investigates this endpoint management case: Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers. 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.
- Use a controlled EMS invitation or endpoint enrollment method that associates a legitimate device with the correct management instance.
- Evaluate EMS endpoint policy matching and priority before changing settings when devices belong to overlapping groups.
- Investigate denied ZTNA traffic by separately checking user authentication, device identity, posture result and backend service route.
Explanation
Correct Answer
A:The targeted next step is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged. The supporting FortiClient EMS principle is: Endpoint connection logs can distinguish network failure, authentication refusal, deliberate deregistration and temporary service interruption. Verify this by: Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes.
Incorrect Answers
B:This action belongs to the distinct FortiClient EMS topic FortiClient registration invitations and enrollment identity, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
C:This action belongs to the distinct FortiClient EMS topic Endpoint policy precedence and assignment conflicts, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
D:This action belongs to the distinct FortiClient EMS topic ZTNA access-denial evidence and least-privilege diagnosis, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Question 607
An endpoint security reviewer examines this scenario. Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers. The proposed action is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged. Which technical principle BEST supports that decision? Select ONE best answer.
- Endpoint connection logs can distinguish network failure, authentication refusal, deliberate deregistration and temporary service interruption.
- FortiOS can retrieve EMS-derived endpoint groups and apply network enforcement when corresponding policies reference the posture tags.
- Endpoint grouping provides administrative and policy targeting; incorrect membership can apply an unrelated restriction or leave devices unprotected.
- Successful service installation alone is insufficient; a pilot must verify endpoint management and the real protected traffic path.
Explanation
Correct Answer
A:Endpoint connection logs can distinguish network failure, authentication refusal, deliberate deregistration and temporary service interruption. Applied to this case (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.), it supports the controlled action: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Incorrect Answers
B:This principle belongs to the distinct FortiClient EMS topic Dynamic firewall policies driven by EMS security posture tags, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
C:This principle belongs to the distinct FortiClient EMS topic Endpoint grouping by inventory attributes and organizational scope, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
D:This principle belongs to the distinct FortiClient EMS topic Controlled EMS initial pilot and rollback decision, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Question 608
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Inspect deployment job output, endpoint installer logs, installed module inventory and EMS registration state.
- Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes.
- Compare delivered Remote Access profile, server certificate, gateway address, authentication outcome and a controlled VPN connection.
- Run equivalent approved and noncompliant tests from on-premises and remote networks and inspect both policy outcomes.
Explanation
Correct Answer
B:The discriminating evidence is: Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes. For the reported situation (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.), it should establish: The investigation identifies the actual Telemetry failure stage rather than resetting a healthy client without cause.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic FortiClient endpoint installation through managed distribution, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.).
C:This evidence belongs to the distinct FortiClient EMS topic Remote Access profile parameters and user authentication, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.).
D:This evidence belongs to the distinct FortiClient EMS topic ZTNA on-net and off-net consistent policy treatment, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.).
Question 609
An endpoint administrator must verify that a configuration change achieved its goal. Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers. The proposed validation is: Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- The investigation identifies the actual Telemetry failure stage rather than resetting a healthy client without cause.
- A clean recovery exercise restores representative profiles and endpoint records within the approved recovery objective.
- Each FortiGate receives appropriate posture information for its site without mixing unrelated customer security states.
- The responsible failed stage is repaired and a controlled malicious test produces the intended isolation evidence.
Explanation
Correct Answer
A:The intended acceptance criterion is: The investigation identifies the actual Telemetry failure stage rather than resetting a healthy client without cause. Confirm it through: Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes. The associated corrective action is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Incorrect Answers
B:That option concerns EMS database backup and disaster recovery validation. The associated corrective action is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
C:That option concerns EMS Fabric connector scope and multi-site mapping. The associated corrective action is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
D:That option concerns Quarantine automation evidence and action outcome. The associated corrective action is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
Question 610
A FortiClient EMS administrator prepares a focused response to this scenario. Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers. Which TWO complementary steps combine the most appropriate action and direct verification? Select TWO answers.
- Separate a missing EMS VPN profile from a FortiGate login, certificate or network tunnel failure when remote access fails.
- Compare configured management interfaces, remote access controls, permitted source networks and successful authorized admin logins.
- Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
- Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes.
- Test the canonical EMS FQDN from office and remote networks, relevant HTTPS connectivity and certificate name matching.
Explanation
Correct Answers
C:The targeted next step is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
D:The discriminating evidence is: Align the endpoint's connection events, EMS inventory last-seen time, hostname resolution and any relevant management changes.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic VPN profile versus remote gateway authentication problems, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.). The targeted action for this case is: Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
B:This evidence belongs to the distinct FortiClient EMS topic EMS server configuration and secure administrator access, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.).
E:This evidence belongs to the distinct FortiClient EMS topic EMS initial network identity and DNS reachability, not the case-specific issue of FortiClient endpoint Telemetry event chronology described here (Several workstations disconnect at the same time a firewall ACL is changed and the team initially blames individual installers.).