An enterprise runs a core business application primarily in its on-premises data center and maintains a warm standby disaster recovery environment in Google Cloud. The company has established the following technical and business continuity requirements: Primary traffic must be routed entirely to on-premises compute resources during normal operations to minimize cloud compute consumption. If on-premises capacity is exceeded or instances experience an outage, excess traffic must automatically spill over and fail over to autoscaled Managed Instance Groups (MIGs) in Google Cloud. If a backend group degrades and less than 25% of its endpoints pass health checks, traffic must automatically be drained away from it without manual intervention. Which configuration should the Cloud Architect recommend?

Configure Cloud Service Mesh load balancing with preferred backends pointing to hybrid connectivity NEGs, assign Google Cloud MIGs as non-preferred backends, and enable automatic capacity draining.: ### What Preferred Backends and Automatic Capacity Draining Are **Cloud Service Mesh** provides advanced traffic management and load balancing capabilities for hybrid and multi-region deployments. By configuring **preferred backends**, traffic is prioritized to a specific group of endpoints (such as on-premises compute represented by **hybrid connectivity Network Endpoint Groups (NEGs)**) up to their maximum capacity before spilling over to non-preferred backends. **Automatic capacity draining** is a resilience mechanism that automatically scales down a backend group's capacity to zero when its healthy endpoint ratio drops below a threshold. ### How It Meets the Requirements - **Minimize Cloud Consumption during Normal Operations**: Designating on-premises hybrid connectivity NEGs as **preferred backends** ensures that 100% of steady-state traffic is directed on-premises first. - **Automated Failover and Overflow**: Any traffic exceeding the configured threshold or capacity of the preferred backends is automatically routed to non-preferred backends (the autoscaled Google Cloud MIGs), providing seamless failover and overflow capabilities. - **Rapid Isolation of Degraded Backends**: Enabling **automatic capacity draining** automatically scales a backend group's capacity to zero when fewer than 25% of its endpoints pass health checks, preventing requests from being routed to failing infrastructure. ### Key Advantages and Capabilities - **Zero-Touch Failover**: Automatically transitions traffic to warm standby cloud instances during on-premises degradation or localized disasters. - **Cost Efficiency**: Keeps active cloud resource consumption low until failover or capacity overflow is needed. - **Endpoint Protection**: Protects remaining healthy instances in a degraded pool from cascading overload. - **Automatic Recovery**: Automatically undrains and restores traffic to preferred backends when at least 35% of endpoints remain healthy for 60 seconds. ### Why This Is Optimal This architecture delivers an automated warm standby disaster recovery pattern without manual capacity scaling or DNS modifications, meeting both cost and business continuity objectives.

StudyCerts

Hybrid Disaster Recovery Preferred Backends Automatic Capacity | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Hybrid Disaster Recovery Preferred Backends Automatic Capacity

Section: Business continuity

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 runs a core business application primarily in its on-premises data center and maintains a warm standby disaster recovery environment in Google Cloud.

The company has established the following technical and business continuity requirements:

Primary traffic must be routed entirely to on-premises compute resources during normal operations to minimize cloud compute consumption.
If on-premises capacity is exceeded or instances experience an outage, excess traffic must automatically spill over and fail over to autoscaled Managed Instance Groups (MIGs) in Google Cloud.
If a backend group degrades and less than 25% of its endpoints pass health checks, traffic must automatically be drained away from it without manual intervention.

Which configuration should the Cloud Architect recommend?

Configure Cloud Service Mesh using the spray to world load balancing algorithm across hybrid connectivity NEGs and Google Cloud MIGs.

Configure Cloud Service Mesh using the waterfall by zone algorithm and configure custom Cloud Monitoring alert policies to manually reset capacity scalers.

Deploy an external Application Load Balancer with Cloud DNS weighted routing policies configured to route 100% of requests to on-premises IP addresses.

Configure Cloud Service Mesh load balancing with preferred backends pointing to hybrid connectivity NEGs, assign Google Cloud MIGs as non-preferred backends, and enable automatic capacity draining.

Professional Cloud Architect

Hybrid Disaster Recovery Preferred Backends Automatic Capacity

Related questions