Gcp Global Alb Weighted Traffic Shift

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

Your team is preparing to execute a canary deployment for a high-traffic e-commerce microservice exposed via a Global External Application Load Balancer. You need to design a controlled traffic shift that gradually redirects incoming HTTP(S) requests from the baseline backend service to a newly deployed canary backend service while preserving high availability and predictable failover.

Which configuration and runtime behavior correctly describes how the Global External Application Load Balancer executes this traffic redirection?

Set the balancing mode on the canary backend service to RATE with a max rate of zero, which automatically triggers a gentle 70% cross-zone traffic drain to the baseline backend.

Configure CLIENT_IP session affinity on both backend services to maintain sticky routing; session affinity takes precedence over URL map weighted traffic splitting rules to prevent canary users from hopping backends.

Create separate global forwarding rules for each backend service and balance traffic between them using multiple anycast IP addresses on the same URL map.

Configure weighted traffic splitting in the URL map across the two backend services; weighted traffic splitting takes precedence over session affinity, and health check failures automatically redirect traffic to healthy backends.

Professional Cloud DevOps Engineer

Gcp Global Alb Weighted Traffic Shift

Related questions