Explanation:
The question asks how to ensure the application runs properly on GCP without redesigning it, as it is in the design stage. Option C is optimal because GCP's HTTP(S) load balancer natively supports WebSockets, allowing the application to run as-is without code changes. Community consensus (71% support for C, with high upvotes) and official documentation confirm this. Option A involves unnecessary code conversion, B addresses encryption not mentioned in the question, and D suggests a redesign, which contradicts the goal of ensuring the current design runs properly. While D promotes scalability, it is not the best fit here as it requires significant changes rather than leveraging GCP's built-in capabilities.
Ultimate access to all questions.
How can you ensure a web application using non-distributed WebSockets and HTTP sessions runs properly on Google Cloud Platform?
A
Help the engineer to convert his websocket code to use HTTP streaming
B
Review the encryption requirements for websocket connections with the security team
C
Meet with the cloud operations team and the engineer to discuss load balancer options
D
Help the engineer redesign the application to use a distributed user session service that does not rely on websockets and HTTP sessions.
No comments yet.