Question 920
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A branch updates device compliance rules but does not communicate the remediation steps, leaving users locked out unnecessarily. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a branch updates device compliance rules but does not communicate the remediation steps, leaving users locked out unnecessarily. The relevant technical mechanism is: An enforceable posture rule needs a workable remediation path to avoid permanent operational lockout. The most direct diagnostic or implementation action is: Publish safe approved remediation and check-in instructions for each common compliance failure. A useful verification is: Pilot users restore compliant access without administrators disabling required controls. An ongoing safeguard is: Test user-facing recovery instructions before expanding enforcement. This is the INTENDED choice for the most useful ongoing preventive control. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
The suggested review tracks a different technical risk: Documentation alone does not change automated endpoint compliance evaluation. Here the sustained control must address: An enforceable posture rule needs a workable remediation path to avoid permanent operational lockout. Choose “Test user-facing recovery instructions before expanding enforcement”.
That safeguard is relevant to: OS version alone does not prove that local security defenses are active. The current failure instead follows from: An enforceable posture rule needs a workable remediation path to avoid permanent operational lockout. Its prevention measure is “Test user-facing recovery instructions before expanding enforcement”.
This routine guards against another mechanism: An isolated false positive does not justify eliminating broad vulnerability protection. The recurring exposure in the current case is: An enforceable posture rule needs a workable remediation path to avoid permanent operational lockout. The matching preventive check is “Test user-facing recovery instructions before expanding enforcement”.