3.3 Configuring Cloud DNS. Considerations Include: PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   A company runs a global web application with two backend clusters: one in us-central1 and one in europe-west1. They want users in North America to reach the us-central1 cluster and users in Europe to reach the europe-west1 cluster. If a user's region has no matching cluster, traffic should fall back to the nearest available cluster. The team has already created a public zone and added A records for both clusters. What should they configure next?

   • ACreate a weighted routing policy with 50% weight for each cluster, so traffic is split evenly regardless of user location.
   • BCreate two separate record sets, one for each region, and rely on the resolver's EDNS Client Subnet to pick the closest one.
   • CCreate a failover routing policy with us-central1 as primary and europe-west1 as backup, then attach a health check to the primary.
   • DCreate a geolocation routing policy on the record set, with two geolocation policies (North America → us-central1, Europe → europe-west1) and a default policy that routes to the nearest cluster.
   Reveal Solution Discussion Select an answer first
2. 2expert · hard

   A team runs a GKE cluster and uses external-dns to manage records in a Cloud DNS public zone. They have a Service of type LoadBalancer that should be registered as 'app.example.com'. The external-dns pod is running, but the record is not being created. They have verified that the Service has the correct annotation. What is the most likely cause?

   • AThe external-dns deployment is in a different namespace than the Service.
   • BThe Cloud DNS zone is a private zone, not a public zone.
   • CThe ServiceAccount used by external-dns does not have the 'dns.admin' IAM role on the Cloud DNS zone.
   • DThe Service is not of type LoadBalancer; it is of type ClusterIP.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   An organization has an internal application that must resolve to a private IP address (10.0.0.5) when queried from inside the VPC, but to a public IP address (203.0.113.10) when queried from the internet. They currently have a public zone for the domain. What is the minimal set of Cloud DNS resources needed to achieve this?

   • AUse a routing policy with a geolocation rule that returns 10.0.0.5 for the VPC's region and 203.0.113.10 for all other regions.
   • BAdd a CNAME record in the public zone pointing to an internal hostname that resolves to 10.0.0.5.
   • CCreate a second public zone with the same name and set the DNS TTL to 0 so internal resolvers pick the private IP.
   • DCreate a private zone for the same domain, add an A record pointing to 10.0.0.5, and attach it to the VPC.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   A company has a private zone in Project A and wants resources in Project B's VPC to resolve names from that zone. What should be configured?

   • AA CNAME record in Project B
   • BDNS peering between the two VPC networks
   • CAn outbound forwarding rule
   • DA public zone in Project B
   Reveal Solution Discussion Select an answer first
6. 5foundation · easy

   A company wants Cloud DNS to forward queries for a specific domain to an on-premises DNS server. What should be configured?

   • AAn outbound DNS server policy with a forwarding rule
   • BAn inbound DNS server policy
   • CA DNS peering zone
   • DA private zone with a CNAME record
   Reveal Solution Discussion Select an answer first