Question 400
At fictional Alder Community, an endpoint security engineer responsible for employee enrollment is reviewing EMS, endpoint and secure-access troubleshooting during a Security Fabric integration test (FCT-7.4-4.1-100). The observed endpoint management issue is: A FortiClient endpoint shows profile sync pending and an administrator keeps editing policy instead of reviewing the disconnected telemetry path. Which observation best verifies that the proposed correction worked?
Explanation
Correct Answer
This is the direct verification evidence: The endpoint reconnects and receives the unchanged approved policy without speculative policy edits. It supports the engineering change to examine current management connectivity, policy assignment and last successful client synchronization. The relevant principle is that policy synchronization depends on agent reachability and can lag even when configuration itself is valid.
Incorrect Answers
Evidence that “Monitoring searches and client telemetry recover after approved server resource remediation” occurred would not by itself establish resolution of the reported problem: a FortiClient endpoint shows profile sync pending and an administrator keeps editing policy instead of reviewing the disconnected telemetry path. The specific reason is policy synchronization depends on agent reachability and can lag even when configuration itself is valid. The applicable verification is “The endpoint reconnects and receives the unchanged approved policy without speculative policy edits”.
Evidence that “The expected device identity and authorized ZTNA handshake are restored after connection prerequisites are met” occurred would not by itself establish resolution of the reported problem: a FortiClient endpoint shows profile sync pending and an administrator keeps editing policy instead of reviewing the disconnected telemetry path. The specific reason is policy synchronization depends on agent reachability and can lag even when configuration itself is valid. The applicable verification is “The endpoint reconnects and receives the unchanged approved policy without speculative policy edits”.
Evidence that “The server handles staged registrations with acceptable resource levels and no destructive reset” occurred would not by itself establish resolution of the reported problem: a FortiClient endpoint shows profile sync pending and an administrator keeps editing policy instead of reviewing the disconnected telemetry path. The specific reason is policy synchronization depends on agent reachability and can lag even when configuration itself is valid. The applicable verification is “The endpoint reconnects and receives the unchanged approved policy without speculative policy edits”.