Question 170
While designing controls for this requirement—An organization grants consultants broad server-subnet access after SSO authentication even though they need one ticketing application—what limitation should the project not overlook?
Explanation
Correct Answer
The issue is not a general product inconvenience: A broad private RFC1918 route is not equivalent to application-scoped authorization. That matters for an organization grants consultants broad server-subnet access after SSO authentication even though they need one ticketing application. The design should document the corresponding investigation and practical acceptance evidence.
Incorrect Answers
This can be appropriate when field laptops connect through VPN but sensitive engineering apps should require healthy encryption and endpoint protection, but it does not isolate the distinguishing requirement here: An organization grants consultants broad server-subnet access after SSO authentication even though they need one ticketing application. The correct risk decision is a broad private RFC1918 route is not equivalent to application-scoped authorization.
The choice “Allowing every host that uses a shared login defeats device-based segmentation” addresses a different architecture condition: A merger introduces unmanaged IoT terminals whose shared service accounts make User-ID alone unable to distinguish authorized devices. The present situation is an organization grants consultants broad server-subnet access after SSO authentication even though they need one ticketing application. For this lens the relevant response is instead: A broad private RFC1918 route is not equivalent to application-scoped authorization.
That alternative belongs to the case: A hospital allows privileged clinicians to open medical apps from any unmanaged endpoint merely because they have valid passwords. It is not sufficient evidence or remediation for an organization grants consultants broad server-subnet access after SSO authentication even though they need one ticketing application. The case-specific choice is a broad private RFC1918 route is not equivalent to application-scoped authorization.