Question 130
At fictional Alder Community, an endpoint security engineer responsible for employee enrollment is reviewing FortiGate integration, posture tags, ZTNA and containment during a remote access rollout (FCT-7.4-3.2-033). The observed endpoint management issue is: A FortiGate quarantines an endpoint but the EMS operator sees no confirmation because cross-system communication is failing. Which recurring preventive or detective safeguard would best reduce recurrence?
Explanation
Correct Answer
The recurring safeguard is to alert when quarantine requests remain pending or systems report conflicting states. It mitigates the actual failure: A FortiGate quarantines an endpoint but the EMS operator sees no confirmation because cross-system communication is failing. A suitable correction is to diagnose the Fabric request flow, EMS managed-device state and endpoint status notification path; its proof is that quarantine state agrees between FortiGate, EMS and the affected agent after connectivity recovers.
Incorrect Answers
“Require security-status review before low-level network resets on managed endpoints” checks a different ongoing risk rather than the reported failure: a FortiGate quarantines an endpoint but the EMS operator sees no confirmation because cross-system communication is failing. The relevant mechanism is distributed containment needs acknowledgement and state consistency across security components. The directly matched preventive control is “Alert when quarantine requests remain pending or systems report conflicting states”.
“Document version-specific tag terminology in all deployment and support runbooks” checks a different ongoing risk rather than the reported failure: a FortiGate quarantines an endpoint but the EMS operator sees no confirmation because cross-system communication is failing. The relevant mechanism is distributed containment needs acknowledgement and state consistency across security components. The directly matched preventive control is “Alert when quarantine requests remain pending or systems report conflicting states”.
“Compare endpoint registration and FortiGate connector ownership before enabling automation” checks a different ongoing risk rather than the reported failure: a FortiGate quarantines an endpoint but the EMS operator sees no confirmation because cross-system communication is failing. The relevant mechanism is distributed containment needs acknowledgement and state consistency across security components. The directly matched preventive control is “Alert when quarantine requests remain pending or systems report conflicting states”.