Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are designing the deployment architecture for a financial web application serving customers exclusively within a single European country. Your solution must satisfy the following requirements:
Which deployment architecture and resource configuration should you choose?
A regional deployment architecture distributes application components redundantly across two or more zones within a single Google Cloud region. Because zones are isolated failure domains backed by independent physical data centers, deploying across multiple zones protects workloads from single-zone hardware, power, or network interruptions while keeping all resources inside one geographic boundary.
Compared to a zonal setup, a regional architecture eliminates single points of failure at the zone level. Compared to multi-regional or global designs, it avoids unnecessary cross-region replication costs and ensures strict single-region data locality, making it the ideal balance of resilience, compliance, and cost.
A zonal deployment architecture provisions compute and primary storage resources inside a single Google Cloud zone. While it may pair with regional networking components such as a regional external Application Load Balancer, the underlying application stack shares one zonal failure domain.
This option would be appropriate for development and test environments, non-critical internal tools that can tolerate downtime, or tightly coupled batch computing jobs that prioritize minimal intra-zone network latency over high availability.
Students often assume that placing a regional load balancer in front of VMs makes the whole application regionally resilient. In practice, a workload is only as resilient as its narrowest resource scope; without backends distributed across multiple zones, the load balancer has no healthy targets during a zone outage.
A global deployment architecture spreads application stacks across Google Cloud regions worldwide behind a global external Application Load Balancer. Using a single anycast IP address, the load balancer directs each user request to the nearest healthy region while a globally replicated database maintains consistent state.
This option would be ideal for a global SaaS platform, retail site, or social media service with users distributed around the world that requires low latency everywhere and has no single-country data localization restrictions.
Developers sometimes choose global resources assuming they are always superior to regional resources. However, when customers and regulations are confined to a single country, a global architecture introduces unnecessary data transfer costs, latency from distant replication, and regulatory compliance violations.
A multi-regional deployment architecture runs independent, redundant application stacks across multiple zones in two or more Google Cloud regions. It typically pairs multi-region databases such as Spanner with Cloud DNS routing policies to survive complete regional outages.
This option would be the right choice for mission-critical applications serving geographically dispersed users across a continent where surviving an entire region outage is mandatory and strict single-country data residency is not a constraint.
While Cloud DNS geofenced routing policies can keep regional traffic within specified geographic areas like Europe, they do not restrict a multi-region database or secondary regional stack from residing outside a single country when only one Google Cloud region exists there. Choosing the right service scope means matching the failure domain to actual business and regulatory boundaries.
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