Cloud Digital Leader Scaling with Google Cloud operations Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Deploy in a single region with a Managed Instance Group using 3 availability zones.

  Why it's wrong here

  An unmanaged instance group with 3 availability zones provides regional resilience, not disaster recovery across regions. All zones in a single region share the same infrastructure boundaries, so a regional outage (e.g., a major power event, a regional network failure, or a geographic disaster) will take down every zone simultaneously. While zonal redundancy protects against a single zone failure and enables autohealing, it does nothing to redirect users if the entire region becomes unreachable. True regional failover requires a second deployment in another region behind a global load balancer.

• ✓

  Deploy the application in multiple regions with a Global Load Balancer for automated failover.

  Why this is correct

  Deploying the application in multiple regions and placing the backends behind a global load balancer (e.g., Global HTTP(S) LB) provides active-active geographic redundancy. The GLB uses a single anycast IP and routes each request to the closest healthy backend based on latency and health check status; when the health checks for an entire region fail, the load balancer automatically shifts traffic to the remaining healthy regions. This protects against regional outages and is a core pattern for mission-critical applications requiring high availability. For full recovery, the application must also replicate state (e.g., Cloud Spanner or Firestore) across regions.

• ✗

  Enable Cloud Armor on the load balancer to protect against regional failures.

  Why it's wrong here

  Cloud Armor is a security product that runs at the edge of Google's network, providing WAF rules and DDoS protection. It is applied to a load balancer to filter malicious traffic, but it does not participate in traffic routing or failover decisions. Enabling Cloud Armor has no effect on the load balancer's ability to detect unhealthy backends or to redirect traffic away from an unavailable region. Protecting against regional failure requires redundant compute deployments in multiple regions and health-check-based global load balancing, not any edge security policy.

• ✗

  Use Cloud Storage multi-region buckets for application data.

  Why it's wrong here

  Cloud Storage multi-region buckets are a data-durability solution that replicates objects across at least two regions, protecting against loss of the storage layer. However, application availability depends on compute resources fronted by a load balancer; if the instances running your application go down in all zones of a region, the multi-region bucket cannot serve requests or execute application logic. Storing static assets or backups in multi-region buckets is a complementary part of a DR plan, but it must be paired with multi-region compute and global load balancing to actually keep the service reachable.

Go deeper

Related to this question