Question 330
Original fictional FortiClient EMS 7.4 practice case R181-CASE-083 — Regional insurer reviewing scheduled scans. Observed evidence: A security audit shows no evidence that the required periodic scanning policy runs on endpoints. 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: Configure the supported scan schedule and assignment on the correct EMS profile. The initial signal was: A security audit shows no evidence that the required periodic scanning policy runs on endpoints. A generic online indication alone would not prove this particular issue was resolved: The central endpoint profile does not define or deliver the scheduled scan setting.
Incorrect Answers
Incorrect for this incident. This result would support a different diagnosis: A suspected false positive is being handled with a global security bypass; its warning sign is: A legitimate signed application repeatedly triggers a detection and staff propose disabling all protection. The current case instead requires verification that: A pilot scan completes and is recorded in the endpoint status. That follows remediation of: The central endpoint profile does not define or deliver the scheduled scan setting.
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: A pilot scan completes and is recorded in the endpoint status. That follows remediation of: The central endpoint profile does not define or deliver the scheduled scan setting.
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: A pilot scan completes and is recorded in the endpoint status. That follows remediation of: The central endpoint profile does not define or deliver the scheduled scan setting.