Topic 1 Question 9
You have deployed a new internal application that provides HTTP and TFTP services to on-premises hosts. You want to be able to distribute traffic across multiple Compute Engine instances, but need to ensure that clients are sticky to a particular instance across both services. Which session affinity should you choose?
None
Client IP
Client IP and protocol
Client IP, port and protocol
ユーザの投票
コメント(17)
The correct answer is B HTTP/S port 80/443 TFTP port 69 Session affinity, (sticky sessions), overrides the load-balancing algorithm by directing all requests in a session to a specific application server.
So, we need a Session affinity by Client IP.
Session affinity https://cloud.google.com/load-balancing/docs/backend-service#session_affinity Session affinity options https://cloud.google.com/load-balancing/docs/internal#session_affinity
The answer A&D produces the same (Client IP, protocol, and port) by the way.
👍 21HateMicrosoft2020/08/21How can it be D when it says sticky across both the services?
👍 2beebee2020/08/01Answer B 2-tuple hashing, which uses the source and destination IPs. All connections from a client will end up on the same instance regardless of protocol as long as the instance stays healthy.
https://cloud.google.com/load-balancing/docs/target-pools#sessionaffinity
👍 2runtheworld2020/08/21
シャッフルモード