An application team is performing a load-balancing test for a critical application during off- hours and has requested access to the load balancer to review. Which servers are up without having the ad

This option is vague and nonsensical as written, and does not address the core security concern of limiting access scope on a shared load balancer.

Disabling other critical applications to grant access introduces unnecessary downtime and business risk, violating the principle of availability and creating more harm than the original problem.

Granting read-only access follows the principle of least privilege, allowing the application team to view server status and load-balancing metrics without the ability to modify configurations affecting other critical applications. This satisfies the team's requirement to check which servers are up during testing while maintaining security boundaries. Read-only access is a standard role-based access control (RBAC) approach that limits the blast radius of any potential misuse or accidental change.

Sharing an account violates the principle of individual accountability and non-repudiation, as actions cannot be traced to a specific user, and it exposes credentials that could be misused or leaked.