Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization connects North American and European data centers to a VPC via Dedicated Interconnect VLAN attachments in us-east4 and europe-west1. You configure:
app.internal.example.com): Geolocation routing policy (geofencing disabled) with health checks for regional Internal Application Load Balancers (global access enabled) in us-east4 and europe-west1.us-east4, entering Google Cloud via the europe-west1 VLAN attachment.app.example.com): Geolocation routing policy with external endpoint health checks.During a simultaneous outage of both internal load balancers after TTL expiration, European clients still receive VIPs instead of DNS errors.
Which statement accurately explains both the fallback behavior and geolocation evaluation across these zones?
us-east4) unless EDNS client subnet is enabled on the on-premises resolver; when all policy buckets fail health checks, Cloud DNS normally returns SERVFAIL, so VIPs are only returned if TTL caching is active or health check logging is disabled.An inbound server policy creates internal entry point IP addresses within a VPC network so on-premises clients and resolvers can query Cloud DNS private zones over Cloud Interconnect or Cloud VPN. Health check logging provides observability into routing policy decisions, while SERVFAIL is an error response code returned when an authoritative or forwarding DNS path cannot complete resolution.
us-east4, Cloud DNS identifies the source region as europe-west1 because that is the region of the Dedicated Interconnect VLAN attachment receiving the packets.SERVFAIL Fallback Misconception: Cloud DNS routing policies do not synthesize SERVFAIL when all health-checked endpoints fail; instead, Cloud DNS falls back to treating all endpoints as healthy and returns VIPs even after TTLs expire. Enabling or disabling health check logging only records telemetry and never alters DNS resolution behavior.SERVFAIL.The scenario involved outbound DNS forwarding (using a forwarding zone or outbound server policy) where all target on-premises name servers were unreachable or failed to respond within 4 seconds—in that case, Cloud DNS synthesizes a SERVFAIL response.
Cloud DNS integrates with internal load balancers in private zones using two distinct health-evaluation models depending on the load balancer type: Internal Application Load Balancers (and internal proxy Network Load Balancers) versus Internal Passthrough Network Load Balancers.
europe-west1)—to select which target region to return. Evaluating the target load balancer's region as the query's origin would make source-based geographic steering impossible.The targets were Internal Passthrough Network Load Balancers (which use the 20% backend threshold and appear healthy if zero backend instances are attached to the backend service), though private geolocation would still depend on the VLAN attachment region.
NXDOMAIN by default unless geofencing is enabled, in which case it returns the closest regional VIP unaltered.EDNS Client Subnet (ECS) is a DNS extension that allows recursive resolvers to pass a client's IP prefix to authoritative public name servers for more accurate geographic routing. Geofencing is a Cloud DNS geolocation option that locks traffic to a designated region rather than failing over across regions when endpoints become unhealthy.
NXDOMAIN Misconception: Cloud DNS never returns NXDOMAIN simply because health checks fail. NXDOMAIN means the queried domain name does not exist in the authoritative zone. When all health-checked policy buckets fail, Cloud DNS treats all endpoints as healthy and returns VIPs.A client queried a non-existent record inside an authorized private managed zone (which triggers NXDOMAIN), and the public zone alone was being evaluated for ECS-based geolocation.
europe-west1) rather than the entry point IP's region (us-east4), whereas the public zone uses source IP or EDNS client subnet; when all policy buckets are unhealthy, Cloud DNS falls back to treating all endpoints as healthy and still returns VIPs.Cloud DNS geolocation routing policies steer client queries to regional endpoints based on traffic origin, while integrated health checks automate regional failover. However, the mechanism used to determine source geography differs fundamentally between public managed zones and private managed zones, and total health check failure triggers a specific fail-open fallback behavior.
europe-west1)—the region of the entry point IP address (us-east4) is irrelevant.This option correctly distinguishes how public zones leverage source IP/ECS while private zones rely on the Interconnect VLAN attachment region, and accurately identifies Cloud DNS's fail-open behavior when all health-checked policy buckets are unhealthy.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated