Question 470
Original fictional FortiClient EMS 7.4 practice case R181-CASE-118 — Consultancy validating shared certificates. Observed evidence: Another FortiGate is mistakenly trusted using credentials intended for a separate device. 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: Replace shared connector access with the supported per-peer authorized relationship. The initial signal was: Another FortiGate is mistakenly trusted using credentials intended for a separate device. A generic online indication alone would not prove this particular issue was resolved: Shared integration credentials undermine peer-specific audit and revocation.
Incorrect Answers
Incorrect for this incident. This result would support a different diagnosis: The policy is not bound to the specific security posture condition; its warning sign is: A firewall policy grants access based solely on the existence of any EMS tag without checking the correct compliance tag. The current case instead requires verification that: EMS identifies and can revoke only the targeted Fabric peer. That follows remediation of: Shared integration credentials undermine peer-specific audit and revocation.
Incorrect for this incident. This result would support a different diagnosis: Fabric pairing is per authorized peer and was not completed for the second device; its warning sign is: Tags work on headquarters firewall but not on the new regional firewall. The current case instead requires verification that: EMS identifies and can revoke only the targeted Fabric peer. That follows remediation of: Shared integration credentials undermine peer-specific audit and revocation.
Incorrect for this incident. This result would support a different diagnosis: EMS connector destination no longer resolves to the active service; its warning sign is: The Fabric connector still points to the old management FQDN after the migration. The current case instead requires verification that: EMS identifies and can revoke only the targeted Fabric peer. That follows remediation of: Shared integration credentials undermine peer-specific audit and revocation.