A lead software engineer tells you that his new application design uses websockets and HTTP sessions that are not distributed across the web servers. You want to help him ensure his application will run properly on Google Cloud Platform. What should you do?

The correct answer is to meet with the cloud operations team and the engineer to discuss load balancer options. The key issue is that the application uses websockets and HTTP sessions that are not distributed across web servers. This implies session affinity (sticky sessions) is required for the load balancer to direct subsequent requests from the same client to the same backend server. Google Cloud Load Balancers support session affinity, which needs to be configured. Discussing this with the operations team and the engineer ensures the correct load balancer type and configuration are chosen to maintain session state. Converting to HTTP streaming (option A) is a significant architectural change that might not be necessary if session affinity can solve the problem. Reviewing encryption requirements (option B) is important for security but doesn't address the core issue of non-distributed sessions. Redesigning the application (option D) is a drastic step; while a distributed session service is a good practice, it might not be immediately feasible or required if load balancer configuration can provide a solution.