Answer-first summary for fast verification
Answer: Client IP
The requirement is for clients to be sticky to a specific instance across both HTTP and TFTP services. Client IP (B) session affinity uses only the client's IP address to maintain affinity. Since both services (HTTP and TFTP) originate from the same client IP, this ensures all traffic from that client is directed to the same instance, regardless of protocol or port. Options C and D include protocol/port, which would treat HTTP (TCP) and TFTP (UDP) as separate sessions, breaking cross-service stickiness. Option A provides no affinity.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have deployed a new internal application offering HTTP and TFTP services to on-premises hosts. You need to distribute traffic across multiple Compute Engine instances while ensuring client sessions remain sticky to a specific instance for both services.
Which session affinity setting should you configure?
A
None
B
Client IP
C
Client IP and protocol
D
Client IP, port and protocol
No comments yet.