Question

You are migrating a series of applications to Google Cloud Platform with a lift and shift methodology, using Compute Engine.
Applications must be scalable, so Load Balancer and instance groups are being configured.
Some applications manage session data in memory.
Which of the following configurations do you choose to allow apps to work properly?

A. HTTP(S) load balancer with Session affinity
B. HTTP(S) load balancer with WebSocket proxy support
C. QUIC protocol support for HTTPS Load Balancing
D. Network Load Balancing

Answer 1

Correct Answer: A
Session affinity provides a best-effort attempt to send requests from a particular client to the same backend for as long as the backend is healthy and has the capacity, according to the configured balancing mode.
It is the best way to assure that session data is maintained in memory.
It is a feature of the HTTP(S) load balancing.
Google Cloud SSL Proxy Load Balancing terminates user SSL (TLS) connections at the load balancing layer, then balances the connections across your instances using the SSL or TCP protocols. Cloud SSL proxy is intended for non-HTTP(S) traffic. For HTTP(S) traffic, HTTP(S) load balancing is recommended instead.
pass-through load balancer, so your backends receive the original client request