Which of the following is a requirement for the PVWA load balancer?

The requirement for the PVWA (Password Vault Web Access) load balancer to support sticky sessions is correct because sticky sessions are crucial in maintaining user session state across multiple servers. When a user makes a request, they may be sent to different servers for load balancing. However, for web applications like PVWA, it's essential that subsequent requests from the same user go to the same server where their session data is stored. This ensures that the user remains authenticated and has a seamless experience while interacting with the application. Without sticky sessions, users could face interruptions or lose their session data, negatively impacting usability and efficiency.

The other options don't align with the requirements typical for load balancers in this context. Altering page content is generally not desirable as it can disrupt application behavior. Supporting only HTTP requests excludes the use of secure HTTPS, which is crucial for protecting sensitive user data. Requiring all sessions to be secure is important for security, but it does not pertain specifically to load balancer functionality in the same way that sticky sessions do. Therefore, the focus on sticky sessions is critical and highlights an essential operational aspect for the PVWA load balancer.