Question 860
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A company blocks a critical call-center workstation because a compliance rule mistakenly requires software not relevant to its job. Which ongoing control best prevents the same issue from recurring?
Explanation
Correct Answer
In this situation, a company blocks a critical call-center workstation because a compliance rule mistakenly requires software not relevant to its job. The relevant technical mechanism is: Uniform endpoint prerequisites can harm legitimate workflows when business roles differ. The most direct diagnostic or implementation action is: Review role-scoped device requirements and approve a narrow policy correction with compensating controls. A useful verification is: The workstation meets the relevant approved checks without weakening other departments' rules. An ongoing safeguard is: Use pilot groups to test compliance baselines per device class. 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: Loose device identification can turn a narrow exemption into a general bypass. Here the sustained control must address: Uniform endpoint prerequisites can harm legitimate workflows when business roles differ. Choose “Use pilot groups to test compliance baselines per device class”.
That safeguard is relevant to: Agentless proxy clients may not provide the same device telemetry as an installed agent. The current failure instead follows from: Uniform endpoint prerequisites can harm legitimate workflows when business roles differ. Its prevention measure is “Use pilot groups to test compliance baselines per device class”.
This routine guards against another mechanism: Geolocation rules can affect legitimate travel because location is not equivalent to authorization. The recurring exposure in the current case is: Uniform endpoint prerequisites can harm legitimate workflows when business roles differ. The matching preventive check is “Use pilot groups to test compliance baselines per device class”.