Question 410
Original fictional FortiClient EMS 7.4 practice case R181-CASE-103 — Retail branch rotating the EMS hostname. Observed evidence: The Fabric connector still points to the old management FQDN after the migration. After the scoped corrective action, which observation best confirms this specific incident was resolved?
Explanation
Correct Answer
This is the case-specific acceptance evidence after taking the targeted step: Correct the connector target and revalidate its trust relationship. The initial signal was: The Fabric connector still points to the old management FQDN after the migration. A generic online indication alone would not prove this particular issue was resolved: EMS connector destination no longer resolves to the active service.
Incorrect Answers
Incorrect for this incident. This result would support a different diagnosis: The access policy relies on fixed IP objects rather than dynamic EMS-synced identity; its warning sign is: A DHCP-renewed laptop keeps its old static firewall entry despite changing posture. The current case instead requires verification that: FortiGate reconnects to the expected EMS instance without disabling checks. That follows remediation of: EMS connector destination no longer resolves to the active service.
Incorrect for this incident. This result would support a different diagnosis: EMS tagging and FortiGate synchronization are not completing; its warning sign is: EMS displays the compliant tag but FortiGate shows no corresponding dynamic address object. The current case instead requires verification that: FortiGate reconnects to the expected EMS instance without disabling checks. That follows remediation of: EMS connector destination no longer resolves to the active service.
Incorrect for this incident. This result would support a different diagnosis: Fabric registration workflow lacks peer approval and change control; its warning sign is: Multiple administrators can independently authorize unknown FortiGates to EMS. The current case instead requires verification that: FortiGate reconnects to the expected EMS instance without disabling checks. That follows remediation of: EMS connector destination no longer resolves to the active service.