1.1: Designing an overall network architecture
1.A fintech serves an internal API through an internal passthrough Network Load Balancer in us-central1, with an identical stack in us-east1. Internal clients resolve api.corp.internal from a Cloud DNS private zone. If all us-central1 backends become unhealthy, clients must move to us-east1 automatically without manual changes. What should the network engineer configure?
- A.Add a Cloud DNS response policy rule for api.corp.internal returning the us-east1 address, and enable it from a Cloud Monitoring alert on us-central1 backends.
- B.Create an A record set for api.corp.internal with a failover routing policy, referencing both forwarding rules and using their health checks to cut over.
- C.Add the us-east1 instance groups as backends of the us-central1 load balancer's backend service, so one forwarding rule address serves both regions.
- D.Publish both forwarding rule addresses in one A record set with a 30-second TTL, so clients fall back to the other address when a connection fails.
Show answer & explanation
Correct answer: B — Create an A record set for api.corp.internal with a failover routing policy, referencing both forwarding rules and using their health checks to cut over.
- A. Response policy rules are static overrides and Cloud DNS does not evaluate backend health for them. A Monitoring alert only notifies, so enabling the rule still needs manual or custom-built action.
- B. A Cloud DNS failover routing policy can reference the forwarding rules of internal passthrough Network Load Balancers. It uses their health to return the us-east1 address when us-central1 is down.
- C. Backends of an internal passthrough Network Load Balancer must be in the same region as its forwarding rule. us-east1 instance groups cannot be added to the us-central1 backend service.
- D. A plain multi-value record set has no health awareness, so DNS keeps returning the dead us-central1 address. Fallback depends on each client's retry behavior, so cutover is not dependable.