Answer-first summary for fast verification
Answer: Consult with the cloud enablement team about potential load balancer solutions.
Google HTTP(S) Load Balancing inherently supports the WebSocket protocol when HTTP or HTTPS (excluding HTTP/2) is used as the backend protocol. Therefore, the optimal approach is to engage with the cloud enablement team to explore load balancer options. There's no necessity to overhaul the application or switch to HTTP streaming, given Google HTTP(S) Load Balancing's WebSocket compatibility. While evaluating encryption requirements is beneficial, it's unrelated to WebSocket functionality. Reference: [Google Cloud Load Balancing Documentation](https://cloud.google.com/load-balancing/docs/https#websocket_proxy_support)
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
When designing an application that utilizes WebSockets and HTTP sessions not distributed across web servers for Google Cloud Platform, what is the recommended action to ensure proper functionality?
A
Redesign the application to eliminate reliance on WebSockets and HTTP sessions by adopting a distributed user session service.
B
Consult with the cloud enablement team about potential load balancer solutions.
C
Assess the encryption needs for WebSocket connections alongside the security team.
D
Modify the WebSocket implementation to utilize HTTP streaming instead.
No comments yet.