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…

The correct answer is B. Client IP. HTTP/S port 80/443 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…

Submitted by devops_kid· Apr 18, 2026Configuring network services

Question

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?

Options

ANone
BClient IP
CClient IP and protocol
DClient IP, port and protocol

How the community answered

(32 responses)

A
19% (6)
B
72% (23)
C
3% (1)
D
6% (2)

Explanation

HTTP/S port 80/443 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

Topics

#Load Balancing#Session Affinity#Multi-protocol Traffic#Compute Engine

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice