Question 390
Original fictional FortiClient EMS 7.4 practice case R181-CASE-098 — Online retailer monitoring configuration drift. Observed evidence: Users locally edit endpoint security settings and some changes persist after check-in. 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: Reapply managed protections and restrict unauthorized local changes. The initial signal was: Users locally edit endpoint security settings and some changes persist after check-in. A generic online indication alone would not prove this particular issue was resolved: Policy-enforcement and local modification controls are insufficient for the intended baseline.
Incorrect Answers
Incorrect for this incident. This result would support a different diagnosis: Protection capability depends on valid licensing and update entitlement; its warning sign is: EMS inventory shows healthy endpoints but the security subscription has expired. The current case instead requires verification that: Effective settings match the centrally approved baseline after restart. That follows remediation of: Policy-enforcement and local modification controls are insufficient for the intended baseline.
Incorrect for this incident. This result would support a different diagnosis: File containment and endpoint network quarantine are different response scopes; its warning sign is: Staff confuse a malicious-file quarantine with isolating an entire endpoint from the network. The current case instead requires verification that: Effective settings match the centrally approved baseline after restart. That follows remediation of: Policy-enforcement and local modification controls are insufficient for the intended baseline.
Incorrect for this incident. This result would support a different diagnosis: The central endpoint profile does not define or deliver the scheduled scan setting; its warning sign is: A security audit shows no evidence that the required periodic scanning policy runs on endpoints. The current case instead requires verification that: Effective settings match the centrally approved baseline after restart. That follows remediation of: Policy-enforcement and local modification controls are insufficient for the intended baseline.