Question 450
Original fictional FortiClient EMS 7.4 practice case R181-CASE-113 — Government agency reviewing guest network access. Observed evidence: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. 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: Restrict tag-based policy application to the designated protected resources. The initial signal was: An endpoint security tag is added to a broad Internet allow rule unintentionally affecting guests. A generic online indication alone would not prove this particular issue was resolved: Fabric-derived tags were reused without limiting target-policy scope.
Incorrect Answers
Incorrect for this incident. This result would support a different diagnosis: Shared integration credentials undermine peer-specific audit and revocation; its warning sign is: Another FortiGate is mistakenly trusted using credentials intended for a separate device. The current case instead requires verification that: Only managed eligible devices gain access to the specified service. That follows remediation of: Fabric-derived tags were reused without limiting target-policy scope.
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: Only managed eligible devices gain access to the specified service. That follows remediation of: Fabric-derived tags were reused without limiting target-policy scope.
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: Only managed eligible devices gain access to the specified service. That follows remediation of: Fabric-derived tags were reused without limiting target-policy scope.