Cloud Service Mesh Spot Vm Resilience Automatic Capacity

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

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?

Deploy a multi-zone Memorystore for Valkey cluster with Cluster Mode Disabled and connect backends to the reader endpoint.

Configure the Waterfall by zone load balancing algorithm across all MIGs with unmanaged instance groups.

Apply the Spray to world load balancing algorithm and manually set the backend capacityScaler to zero using gcloud when preemption occurs.

Designate the Spot VM MIGs as preferred backends and enable automatic capacity draining on the backend service.

Professional Cloud DevOps Engineer

Cloud Service Mesh Spot Vm Resilience Automatic Capacity

Related questions