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 enterprise DevOps team is optimizing compute costs for a latency-sensitive, stateless microservice governed by Cloud Service Mesh. To implement FinOps cost-reduction practices, the team provisions Spot Virtual Machine (VM) Managed Instance Groups (MIGs) across multiple zones to serve as the primary compute tier, backed by standard on-demand VM MIGs to handle spillover and maintain high availability.
During periodic Spot VM preemption events in a specific zone, multiple instances are reclaimed simultaneously. The surviving Spot VM instances in that zone risk experiencing immediate traffic saturation and cascading failures before autoscaling can replace them.
Which traffic management configuration should the DevOps engineer implement in Cloud Service Mesh to protect degraded instance groups and ensure resilient traffic distribution?
Waterfall by zone is a Cloud Service Mesh load balancing algorithm that routes client requests to the closest backend MIG or Network Endpoint Group (NEG) in the local zone up to its capacity limit before spilling excess traffic over to the next closest zone.
The primary goal was strictly to minimize cross-zone egress bandwidth and latency across stable, non-preemptible workloads where local capacity is guaranteed.
Preferred backends allow Cloud Service Mesh to prioritize routing traffic to specific compute resources—such as cost-effective Spot VM Managed Instance Groups (MIGs)—until their capacity is fully utilized before spilling over to non-preferred backends (such as standard on-demand VMs). Automatic capacity draining is an advanced traffic management feature that automatically scales a backend's effective capacity down to zero when less than 25% of its instances or endpoints pass health checks.
Combining preferred backends with automatic capacity draining establishes an automated, resilient FinOps architecture where cost-optimized Spot VMs are prioritized while eliminating the risk of traffic bottlenecks during sudden preemption surges.
Spray to world is a global load balancing algorithm in Cloud Service Mesh that distributes client requests uniformly across all configured backend instances and regions globally. Setting the capacityScaler to zero is an administrative action that removes a backend from receiving traffic.
gcloud) or slow out-of-band scripts cannot react quickly enough to prevent cascading overload on surviving instances.capacityScaler changes require external monitoring and API invocation overhead.The workload was globally distributed with uniform regional capacity and planned maintenance windows where administrators manually decommission backend groups.
Memorystore for Valkey is a fully managed in-memory data store service. In Cluster Mode Disabled configuration, the instance consists of a single primary node and multiple read replicas across zones, exposing a dedicated reader endpoint to load-balance read queries across replicas.
The scenario focused on state externalization and caching architecture to make compute instances stateless before migrating workloads to Spot VMs.
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