Design Google-recommended network architecture for a highly available web application across us-east1 and us-west1 (no DB required).

The recommended architecture for a highly available web application across multiple regions uses a global HTTP(S) load balancer. This load balancer provides a single, global IP address, simplifying DNS configuration with an A record, and automatically directs traffic to the closest healthy backend. Cloud CDN improves performance by caching content closer to users, and Cloud Armor provides DDoS protection and WAF capabilities. A single VPC spanning regions simplifies network management. Incorrect options: Regional load balancers require external DNS (like Cloud DNS with failover policies) to manage traffic distribution and failover between regions, adding complexity. Separate VPCs with peering add management overhead and are not necessary for a single application spanning regions. While a CNAME can point to the load balancer, an A record directly to the static IP is generally preferred for apex domains and can offer slightly better performance by avoiding an extra DNS lookup. The standard tier for the HTTP(S) load balancer is less performant and offers fewer features than premium tier (which global HTTP(S) LBs use).