Question 660
Original fictional FortiClient EMS 7.4 practice case R181-CASE-165 — University tracking disconnected clients. Observed evidence: No endpoint events arrive from an entire remote office after a DNS migration. Which follow-up operational gate best detects a recurrence of the same failure after recovery?
Explanation
Correct Answer
The preventive gate explicitly checks: Remote endpoints resolve the active EMS address and reconnect, and escalates recurrence of: No endpoint events arrive from an entire remote office after a DNS migration. That pair addresses the identified issue: Clients resolve the EMS hostname to an obsolete private address. The control is derived from the case recovery evidence, not separately certified by a Fortinet subject-matter expert.
Incorrect Answers
Incorrect for this incident. That acceptance gate guards against a different situation: An alert report references a hostname shared by several rebuilt laptops. The current failure to watch for is: No endpoint events arrive from an entire remote office after a DNS migration. Use a monitored gate confirming: Remote endpoints resolve the active EMS address and reconnect.
Incorrect for this incident. That acceptance gate guards against a different situation: A ZTNA app reports a failed login but the user's identity provider shows successful authentication. The current failure to watch for is: No endpoint events arrive from an entire remote office after a DNS migration. Use a monitored gate confirming: Remote endpoints resolve the active EMS address and reconnect.
Incorrect for this incident. That acceptance gate guards against a different situation: EMS records agent telemetry but not the expected antivirus detection events. The current failure to watch for is: No endpoint events arrive from an entire remote office after a DNS migration. Use a monitored gate confirming: Remote endpoints resolve the active EMS address and reconnect.