Question 70
Original fictional FortiClient EMS 7.4 practice case R181-CASE-018 — Development firm integrating FortiGate. Observed evidence: The draft diagram says FortiGate automatically reads endpoint posture without an EMS Fabric connector. 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: Include the supported EMS Fabric connector and policy-consumption path in the design. The initial signal was: The draft diagram says FortiGate automatically reads endpoint posture without an EMS Fabric connector. A generic online indication alone would not prove this particular issue was resolved: The policy enforcement device has no authorized posture-information integration.
Incorrect Answers
Incorrect for this incident. This result would support a different diagnosis: Distinct management functions have different service and trust requirements; its warning sign is: Architecture review groups FortiCloud licensing and endpoint telemetry into a single generic outbound rule. The current case instead requires verification that: FortiGate receives the expected EMS-derived endpoint security tags. That follows remediation of: The policy enforcement device has no authorized posture-information integration.
Incorrect for this incident. This result would support a different diagnosis: The deployment plan carries forward the earlier Windows-host architecture despite the Linux transition; its warning sign is: Procurement includes only a new Windows Server VM for an EMS 7.4.0 installation. The current case instead requires verification that: FortiGate receives the expected EMS-derived endpoint security tags. That follows remediation of: The policy enforcement device has no authorized posture-information integration.
Incorrect for this incident. This result would support a different diagnosis: Operational ownership between the MSP and customer is ambiguous; its warning sign is: The contract delegates console access but does not define responsibility for profile approval or incident quarantine. The current case instead requires verification that: FortiGate receives the expected EMS-derived endpoint security tags. That follows remediation of: The policy enforcement device has no authorized posture-information integration.