Question 120
At fictional Oakridge Energy, an endpoint security engineer responsible for operations consoles is reviewing EMS, endpoint and secure-access troubleshooting during a remote access rollout (FCT-7.4-4.2-030). The observed endpoint management issue is: An organization upgrades EMS but some FortiClient devices stop registering because their version is outside the documented compatible range. Which observation best verifies that the proposed correction worked?
Explanation
Correct Answer
This is the direct verification evidence: Agent registration stabilizes after compatibility correction while unaffected clients retain service. It supports the engineering change to review release compatibility and upgrade the affected agents using supported version and package paths. The relevant principle is that cross-version EMS and client compatibility is a prerequisite for reliable managed endpoint operation.
Incorrect Answers
Evidence that “Directory synchronization recovers and expected endpoint memberships reappear without unnecessary removal” occurred would not by itself establish resolution of the reported problem: an organization upgrades EMS but some FortiClient devices stop registering because their version is outside the documented compatible range. The specific reason is cross-version EMS and client compatibility is a prerequisite for reliable managed endpoint operation. The applicable verification is “Agent registration stabilizes after compatibility correction while unaffected clients retain service”.
Evidence that “The authorized application functions while global malware controls and unrelated detections remain active” occurred would not by itself establish resolution of the reported problem: an organization upgrades EMS but some FortiClient devices stop registering because their version is outside the documented compatible range. The specific reason is cross-version EMS and client compatibility is a prerequisite for reliable managed endpoint operation. The applicable verification is “Agent registration stabilizes after compatibility correction while unaffected clients retain service”.
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: an organization upgrades EMS but some FortiClient devices stop registering because their version is outside the documented compatible range. The specific reason is cross-version EMS and client compatibility is a prerequisite for reliable managed endpoint operation. The applicable verification is “Agent registration stabilizes after compatibility correction while unaffected clients retain service”.