Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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?
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.
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.
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.
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 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.
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.
A Global External Application Load Balancer leverages advanced traffic management features defined within its URL map (route rules) to perform weighted traffic splitting. This capability enables Site Reliability Engineers (SREs) and DevOps teams to route predetermined proportions of incoming traffic across multiple independent backend services behind a single global IP address and target HTTP(S) proxy.
Executing traffic shifting at the URL map layer of a Global External Application Load Balancer avoids the propagation delays and caching issues inherent in DNS-based shifting. It allows deterministic percentage-based canary routing, simplifies rollback in the event of elevated error budgets consumption, and guarantees automatic failover if canary instances degrade.
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.
Create separate global forwarding rules for each backend service and balance traffic between them using multiple anycast IP addresses on the same URL map.
StudyCerts
StudyCerts