Question 140
Original fictional FortiClient EMS 7.4 practice case R181-CASE-035 — Manufacturing group migrating Windows EMS. Observed evidence: The migration runbook skips the import and validation of prior EMS configuration. Which follow-up operational gate best detects a recurrence of the same failure after recovery?
Explanation
Correct Answer
The preventive gate explicitly checks: A pilot cohort retains the correct group assignments and profiles, and escalates recurrence of: The migration runbook skips the import and validation of prior EMS configuration. That pair addresses the identified issue: Existing endpoints risk losing profile mapping after moving to Linux-based EMS. 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: A restored EMS presents an old expired certificate and endpoints reject management. The current failure to watch for is: The migration runbook skips the import and validation of prior EMS configuration. Use a monitored gate confirming: A pilot cohort retains the correct group assignments and profiles.
Incorrect for this incident. That acceptance gate guards against a different situation: TLS authentication errors recur because the EMS host time is substantially inaccurate. The current failure to watch for is: The migration runbook skips the import and validation of prior EMS configuration. Use a monitored gate confirming: A pilot cohort retains the correct group assignments and profiles.
Incorrect for this incident. That acceptance gate guards against a different situation: Endpoints fail to register because the firewall blocks TCP 8013 while HTTPS administration works. The current failure to watch for is: The migration runbook skips the import and validation of prior EMS configuration. Use a monitored gate confirming: A pilot cohort retains the correct group assignments and profiles.