Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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?
This option suggests using CLIENT_IP session affinity on the backend services to keep client connections persistent while expecting session affinity to override weighted traffic splitting in the URL map.
CLIENT_IP uses a 2-tuple hash (source IP and destination IP) rather than full L7 session identification.The application required session stickiness to specific backend endpoints within a single backend service without performing multi-backend service weighted canary traffic splits.
When designing blue/green or canary rollouts, session affinity should be managed via application-level cookies or distinct URL routes if strict persistence to a canary deployment is needed.
This option proposes creating multiple global forwarding rules with distinct public anycast VIPs, pointing them to a single URL map, and attempting to divide traffic at the IP address level.
The architecture required maintaining entirely isolated entry points for distinct external networks or compliance perimeters rather than executing a gradual microservice deployment shift.
Using multiple forwarding rules to manage traffic shifts introduces DNS caching dependencies and prevents instant traffic shifting and immediate rollbacks.
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.
This option describes setting the backend service balancing mode to RATE with zero capacity and references the fixed 70% threshold failover algorithm.
UTILIZATION, RATE, or CONNECTIONS), whereas progressive canary redirection requires URL map weighted traffic splitting.An SRE needed to drain an entire backend instance group for maintenance by zeroing out its capacity setting, rather than performing a progressive multi-service canary shift.
Balancing capacity limits protect backends from overload, but they do not provide deterministic percentage-based splitting across distinct application versions.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated