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.
An e-commerce platform hosted on Google Cloud experiences periodic flash-sale traffic surges that can exhaust Compute Engine regional vCPU quotas and cause capacity constraints in the primary region (us-central1).
The Site Reliability Engineering (SRE) team needs to implement an automated multi-region capacity scaling and rapid failover strategy. The solution must:
us-east4) as soon as the primary region reaches backend capacity or quota limits.Which architectural strategy should the SRE team implement?
Network Service Tiers Premium Tier routes global traffic over Google's high-performance, low-latency private backbone network using a single global anycast IP address. When combined with an external Application Load Balancer and multi-region backend services, Google Cloud monitors backend utilization in real time.
us-central1 hit capacity limits or cannot autoscale further due to regional quota exhaustion, the global load balancer automatically spills over excess requests to the nearest healthy region (us-east4) with available capacity.This approach provides true active-active multi-region resilience. It seamlessly absorbs regional capacity constraints without administrative intervention or complex client-side failover logic.
us-central1 and updates Cloud DNS records.Manual capacity draining is an operational procedure used to gracefully remove traffic from a backend group during maintenance, while Cloud DNS updates programmatically alter DNS records via API calls.
Engineers were executing a planned regional maintenance event or disaster recovery exercise where immediate, automated traffic overflow was unnecessary.
Network Service Tiers Standard Tier routes traffic over the public internet rather than Google's premium global backbone, utilizing regional IP addresses for entry into the network.
The primary goal were to minimize egress network costs for latency-insensitive workloads that do not require automated, sub-second cross-region overflow.
us-central1 and configure Horizontal Pod Autoscaling (HPA).A regional Google Kubernetes Engine (GKE) cluster runs control plane replicas and worker nodes across multiple zones within a single Google Cloud region. Horizontal Pod Autoscaling (HPA) scales Pod replicas up or down based on observed resource utilization metrics.
us-central1 reaches its project-level regional Compute Engine vCPU or IP address quota limits, Cluster Autoscaler cannot provision new nodes, leaving HPA Pods in a perpetual Pending state.us-central1, it cannot route excess requests or failover traffic to us-east4 during localized infrastructure limitations.The business requirement only mandated high availability across zones within a single geographical location without protection against regional quota exhaustion.
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