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 hosts an internal application in a Google Cloud VPC using regional internal passthrough Network Load Balancers in us-central1 and europe-west1. Clients access the application from Compute Engine VMs across multiple regions and from on-premises networks over Cloud VPN tunnels terminating in us-east1 using a Cloud DNS inbound server policy.
You need to configure an A resource record set for app.internal.example.com. in a Cloud DNS private managed zone to meet these requirements:
Which configuration should you implement?
A Cloud DNS FAILOVER routing policy implements an active-passive high-availability configuration by defining a primary target set (--routing-policy-primary-data) and a geo-based backup target set (--routing-policy-backup-data). Under normal operation, Cloud DNS returns the active primary targets and switches entirely to the backup targets only after all primary forwarding rules fail health checks.
FAILOVER policy does not perform active-active proximity routing across all regions during steady state. Instead, 90% of all queries—including queries from Compute Engine VMs located in europe-west1—are routed to us-central1 as long as us-central1 remains healthy.--backup-data-trickle-ratio=0.1 sends 10% of global queries to europe-west1 regardless of client location to verify backup readiness, which still forces 90% of European traffic to us-central1 and sends 10% of North American traffic across to Europe.FAILOVER policies require --routing-policy-backup-data-type=GEO for the backup set, meaning geographic selection applies only after all primary endpoints fail.--routing-policy-type in place after creation; changing from FAILOVER to GEO requires deleting and recreating the record set.The organization wanted an active-passive disaster recovery design where us-central1 handles virtually all production traffic during normal operation and europe-west1 serves strictly as a standby region with 10% validation trickle traffic.
Choosing between GEO and FAILOVER depends on whether the steady-state architecture is active-active (closest healthy region) or active-passive (single primary with standby backup).
A Cloud DNS geolocation (GEO) routing policy in a private managed zone dynamically steers DNS queries to the nearest healthy regional endpoint based on where the query enters Google Cloud. Combining --enable-health-checking, --no-enable-geo-fencing, forwarding rule names, and global access on regional internal passthrough Network Load Balancers creates an active-active, health-aware cross-region DNS architecture.
us-east1) for queries arriving via an inbound server policy. Queries from us-east1 and North America resolve to us-central1, while European queries resolve to europe-west1.--no-enable-geo-fencing), automatically returns the next closest healthy region's VIP.us-east1 (over Cloud VPN) and other regions to reach the load balancer VIPs in us-central1 and europe-west1 during both normal operation and failover.Unlike a FAILOVER policy that forces steady-state traffic to a single primary region, or a geofenced GEO policy that blocks cross-region failover, a non-geofenced GEO policy with global access and forwarding-rule health checks delivers both lowest-latency active-active steering and automated regional resilience.
Creating a global Compute Engine health check with --source-regions and attaching it via --health-check is the workflow designed for public Cloud DNS zones monitoring external endpoints. Meanwhile, leaving global access disabled restricts an internal passthrough Network Load Balancer so that only clients in the same VPC and same region as the load balancer can connect to its VIP.
us-east1 nor Compute Engine VMs in non-local regions (including traffic failing over between us-central1 and europe-west1) can reach the load balancer VIPs.--enable-health-checking is used for internal load balancers in a private managed zone, Cloud DNS requires forwarding rule names in --routing-policy-data rather than raw VIP addresses, and does not probe internal VIPs using external --source-regions probers.--source-regions require three Google Cloud regions to probe external endpoints over the public internet (http, https, ssl, or tcp with a 30–300 second check interval) and apply to public zones.The application were exposed on external IP endpoints in a public Cloud DNS zone, where global health-check probers across three source regions monitor public VIPs and VPC global access does not apply.
A Cloud DNS geolocation routing policy (GEO) maps incoming DNS queries to regional endpoints based on the geographic origin of the request. Adding the --enable-geo-fencing flag applies a geofence to each configured region, strictly confining clients to the endpoint assigned to their nearest region regardless of backend health.
us-east1 to us-central1 continue receiving unreachable or degraded load balancer VIPs until local backends recover.false in Cloud DNS GEO policies unless explicitly enabled with --enable-geo-fencing.Regulatory, data residency, or compliance mandates required that traffic from a specific geography never leave its designated region, even during a complete regional backend outage.
A common misconception is that --enable-geo-fencing activates geographic routing or enforces regional boundaries only when healthy; in practice, it disables automatic cross-region failover.
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