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 organization operates a global, mission-critical application hosted on Google Cloud using Compute Engine Managed Instance Groups (MIGs) behind an external Application Load Balancer. To improve release velocity and prevent customer-facing incidents, the SRE team requires the deployment pipeline to automate canary deployments, metric validation, and traffic draining.
The automated CI/CD workflow must satisfy the following criteria:
Which strategy should you integrate into your CI/CD pipeline to orchestrate this automated traffic draining and canary workflow?
Cloud DNS weighted round-robin is a DNS-level traffic routing policy that resolves client queries to different IP addresses based on predetermined statistical ratios.
This pattern would be appropriate for multi-cloud or hybrid active-active routing between distinct data center facilities where global Layer 7 load balancers cannot span both environments.
Host-level iptables redirection uses Linux kernel packet filtering rules inside the operating system of each Compute Engine instance to redirect local TCP/UDP port traffic to alternative processes or containers.
You were running localized testing inside a single standalone Linux host without access to cloud load balancing infrastructure.
Proactive rolling updates in Compute Engine Managed Instance Groups automatically replace existing instances with new VMs derived from an updated instance template, respecting maxSurge and maxUnavailable constraints.
The requirement was to perform a simple, hands-off rolling deployment across a stateless VM fleet where deployment speed takes precedence over in-depth canary validation.
URL map traffic splitting (weighted backend services) is a native Google Cloud Application Load Balancer feature that allows incoming HTTP(S) traffic to be distributed across multiple backend services according to configurable percentage weights. Connection draining is a backend service setting that ensures in-flight TCP/HTTP requests are given a configured duration (e.g., 300 seconds) to complete cleanly when a backend service or instance group is removed or its weight is reduced to zero.
95% of traffic to the baseline backend service and 5% to the canary backend service.0%. The Application Load Balancer stops routing new requests to the canary while honoring active connections through Connection Draining.100%, sets legacy backend service weight to 0%, and waits for the connection draining timeout to elapse before tearing down the legacy Managed Instance Group.This approach decouples infrastructure provisioning from traffic shifting, providing precise Layer 7 traffic routing control and automated draining natively supported by Google Cloud's network data plane.
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