GCP Professional Cloud Architect Practice Question

Your company operates a latency-sensitive public API in GKE clusters deployed in us-central1 and europe-west1. A Cloud Run service must handle only requests to the /metrics path. You need to expose a single anycast public IP that automatically directs traffic to the nearest healthy region with failover, terminates TLS at Google's edge while encrypting traffic to every backend, and preserves the original client IP inside the pods. Which Google Cloud load-balancing architecture should you implement?

  • Configure a global external HTTP(S) load balancer (backend-service/Envoy) with regional NEGs for the GKE clusters and a serverless NEG for Cloud Run, enabling TLS to backends.

  • Create a regional internal HTTP(S) load balancer and publish it through Cloud DNS with geo-location-based A records pointing to each region's VIP.

  • Provision classic external HTTP(S) load balancers in each region, assign separate forwarding rules, and rely on DNS weighted round-robin for distribution and failover.

  • Deploy a global TCP proxy load balancer in front of the GKE clusters and use Cloud Armor plus Cloud Run domain mapping for the /metrics path.

GCP Professional Cloud Architect
Designing and planning a cloud solution architecture
Your Score:
Settings & Objectives
Random Mixed
Questions are selected randomly from all chosen topics, with a preference for those you haven’t seen before. You may see several questions from the same objective or domain in a row.
Rotate by Objective
Questions cycle through each objective or domain in turn, helping you avoid long streaks of questions from the same area. You may see some repeat questions, but the distribution will be more balanced across topics.

Check or uncheck an objective to set which questions you will receive.

Bash, the Crucial Exams Chat Bot
AI Bot