Question 910
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A company permits unmanaged contractor laptops into a sensitive SaaS tenant because browser-based proxy login alone is treated as full device assurance. Which observable result would best verify the correction?
Explanation
Correct Answer
In this situation, a company permits unmanaged contractor laptops into a sensitive SaaS tenant because browser-based proxy login alone is treated as full device assurance. The relevant technical mechanism is: Agentless identity verification does not inherently establish device compliance at managed-agent depth. The most direct diagnostic or implementation action is: Apply access policies appropriate to unmanaged risk and supported available device signals. A useful verification is: Contractor browsers receive restricted capabilities while managed compliant endpoints retain full access. An ongoing safeguard is: Document differentiated SaaS controls by endpoint trust level. This is the INTENDED choice for the strongest verification evidence. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
That test belongs to another control with this basis: Agentless proxy clients may not provide the same device telemetry as an installed agent. In the current case, the governing reason is: Agentless identity verification does not inherently establish device compliance at managed-agent depth. The direct verification is “Contractor browsers receive restricted capabilities while managed compliant endpoints retain full access”.
This observation would test a different technical dependency: An enforceable posture rule needs a workable remediation path to avoid permanent operational lockout. The current issue is governed by: Agentless identity verification does not inherently establish device compliance at managed-agent depth. Its decisive check is “Contractor browsers receive restricted capabilities while managed compliant endpoints retain full access”.
The alternative verifies a different condition: Cloud activity controls require action-specific verification beyond generic network reachability. The current case instead depends on: Agentless identity verification does not inherently establish device compliance at managed-agent depth. Confirm that “Contractor browsers receive restricted capabilities while managed compliant endpoints retain full access”.