Question 740
Original fictional FortiClient EMS 7.4 practice case R181-CASE-185 — Municipal factory restoring telemetry. Observed evidence: EMS has a valid certificate but remote agents connect to an alias not listed on it. Which follow-up operational gate best detects a recurrence of the same failure after recovery?
Explanation
Correct Answer
The preventive gate explicitly checks: Endpoint clients authenticate without disabling certificate verification, and escalates recurrence of: EMS has a valid certificate but remote agents connect to an alias not listed on it. That pair addresses the identified issue: The configured telemetry hostname does not match the trusted certificate identity. 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: Remote FortiClient telemetry fails after an endpoint proxy change. The current failure to watch for is: EMS has a valid certificate but remote agents connect to an alias not listed on it. Use a monitored gate confirming: Endpoint clients authenticate without disabling certificate verification.
Incorrect for this incident. That acceptance gate guards against a different situation: The installer package is tied to a retired endpoint group rule. The current failure to watch for is: EMS has a valid certificate but remote agents connect to an alias not listed on it. Use a monitored gate confirming: Endpoint clients authenticate without disabling certificate verification.
Incorrect for this incident. That acceptance gate guards against a different situation: A compliant device is blocked because a broader deny rule matches ahead of the required ZTNA allow rule. The current failure to watch for is: EMS has a valid certificate but remote agents connect to an alias not listed on it. Use a monitored gate confirming: Endpoint clients authenticate without disabling certificate verification.