Question 350
At fictional Beacon Health, an endpoint security engineer responsible for clinical laptops is reviewing FortiGate integration, posture tags, ZTNA and containment during a server maintenance validation (FCT-7.4-3.1-088). The observed endpoint management issue is: An endpoint group is renamed in EMS and an engineer assumes FortiGate static IP objects will automatically follow the new label. Which observation best verifies that the proposed correction worked?
Explanation
Correct Answer
This is the direct verification evidence: FortiGate's effective policy references the intended synchronized tag and correct current endpoints. It supports the engineering change to use the supported EMS-derived dynamic posture objects instead of relying on unrelated manually maintained static firewall objects. The relevant principle is that dynamic security posture integration is distinct from manually created address object maintenance.
Incorrect Answers
Evidence that “Incident records connect the device, malicious event, cleanup and approved restoration” occurred would not by itself establish resolution of the reported problem: an endpoint group is renamed in EMS and an engineer assumes FortiGate static IP objects will automatically follow the new label. The specific reason is dynamic security posture integration is distinct from manually created address object maintenance. The applicable verification is “FortiGate's effective policy references the intended synchronized tag and correct current endpoints”.
Evidence that “Endpoint state appears in EMS and available correlated events appear at the configured analytic component” occurred would not by itself establish resolution of the reported problem: an endpoint group is renamed in EMS and an engineer assumes FortiGate static IP objects will automatically follow the new label. The specific reason is dynamic security posture integration is distinct from manually created address object maintenance. The applicable verification is “FortiGate's effective policy references the intended synchronized tag and correct current endpoints”.
Evidence that “Only the intended compromised device is quarantined and healthy devices remain reachable” occurred would not by itself establish resolution of the reported problem: an endpoint group is renamed in EMS and an engineer assumes FortiGate static IP objects will automatically follow the new label. The specific reason is dynamic security posture integration is distinct from manually created address object maintenance. The applicable verification is “FortiGate's effective policy references the intended synchronized tag and correct current endpoints”.