Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise organization runs a critical e-commerce service behind an external Application Load Balancer on Google Cloud. The development team needs to deploy a major update using a canary deployment strategy.
The deployment strategy must satisfy the following operational requirements:
service-v2) to evaluate performance and error rates under real traffic.service-v1).service-v2 or instantly revert to 100% on service-v1 without deploying new infrastructure.Which traffic management configuration should you recommend?
Balancing capacity settings (such as max-utilization or max-rate-per-instance) instruct the load balancer on how many requests or how much CPU utilization an instance group can absorb before spilling traffic over to other backends.
You wanted to prevent backend instances in a specific region or zone from becoming overloaded by diverting excess load to secondary instance groups.
minAvailable: 95% to prevent the canary version from receiving more than 5% of total requests.A Pod Disruption Budget (PDB) is a Kubernetes policy that limits the number of replicated Pods that can be simultaneously unavailable during voluntary disruptions (such as node pool upgrades or cluster maintenance).
You needed to guarantee that at least 95% of stateful or quorum-critical pods remain online during automated GKE node pool maintenance.
service-v1 and service-v2.Cloud DNS weighted routing distributes DNS query responses across different IP endpoints according to configured percentage weights.
You needed to distribute traffic between entirely separate, isolated data centers or multi-cloud hosting environments across different public IP entry points.
routeAction.weightedBackendServices to assign weight 95 to service-v1 and weight 5 to service-v2.URL maps in Google Cloud Application Load Balancers provide advanced traffic routing and management capabilities. Using weightedBackendServices under a path matcher's routeAction, you can split incoming HTTP(S) traffic among multiple backend services based on assigned integer weights.
weight: 95 on service-v1 and weight: 5 on service-v2 distributes incoming production requests proportionately between the two independent backend services.service-v1 and service-v2) maintains its own health checks, ensuring unhealthy instances in the canary group do not take down the stable group.Using weightedBackendServices within the load balancer's URL map is the native, recommended pattern for managing canary and blue-green releases on Google Cloud Compute Engine and GKE backend workloads.

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