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 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:
Which configuration should the Cloud Architect recommend?
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.
This architecture delivers an automated warm standby disaster recovery pattern without manual capacity scaling or DNS modifications, meeting both cost and business continuity objectives.
The spray to world algorithm in Cloud Service Mesh distributes client requests globally across all available MIGs and NEGs in all regions simultaneously, regardless of geographic proximity or locality preference.
The organization required an active-active global load balancing pattern where user requests were intentionally and evenly dispersed across all global cloud and on-premises instances at all times.
The waterfall by zone algorithm in Cloud Service Mesh directs incoming traffic to fill the nearest local MIG or NEG in a zone up to its capacity limit before spilling traffic to the next closest zone within a region.
The architecture operated exclusively inside a single Google Cloud region across multiple zones and prioritized reducing cross-zone egress bandwidth over hybrid failover automation.
Cloud DNS weighted round-robin routing distributes traffic across multiple IP endpoints or load balancers according to static administrator-assigned percentage weights via DNS responses.
The goal was to execute scheduled, manual cross-region migrations or simple DNS-based canary rollouts where sub-minute automated failover and dynamic capacity overflow are not required.
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