Question 370
Original fictional FortiClient EMS 7.4 practice case R181-CASE-093 — Retail payments team checking scan performance. Observed evidence: A heavy scheduled scan repeatedly interrupts payment terminal operations. 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: Adjust the scan schedule and resource policy within security requirements. The initial signal was: A heavy scheduled scan repeatedly interrupts payment terminal operations. A generic online indication alone would not prove this particular issue was resolved: Scan timing conflicts with a high-availability business workflow.
Incorrect Answers
Incorrect for this incident. This result would support a different diagnosis: Detection results are not reflected in access posture or response decisions; its warning sign is: An endpoint has multiple threat events but remains fully trusted for sensitive application access. The current case instead requires verification that: Protection remains enabled and terminal performance stays within agreed thresholds. That follows remediation of: Scan timing conflicts with a high-availability business workflow.
Incorrect for this incident. This result would support a different diagnosis: A temporary exception remained overbroad and unreviewed; its warning sign is: A broad folder exclusion was added for troubleshooting and now bypasses required scanning. The current case instead requires verification that: Protection remains enabled and terminal performance stays within agreed thresholds. That follows remediation of: Scan timing conflicts with a high-availability business workflow.
Incorrect for this incident. This result would support a different diagnosis: Policy-enforcement and local modification controls are insufficient for the intended baseline; its warning sign is: Users locally edit endpoint security settings and some changes persist after check-in. The current case instead requires verification that: Protection remains enabled and terminal performance stays within agreed thresholds. That follows remediation of: Scan timing conflicts with a high-availability business workflow.