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 operates an internal microservice accessed by Compute Engine VMs across us-central1, us-east1, and europe-west1 within a single VPC network. You deployed regional internal passthrough Network Load Balancers in us-central1 (primary) and in us-east1 and europe-west1 (standby).
You must configure Cloud DNS to meet these requirements:
us-central1, failing over to the closest healthy standby region during an outage.Which configuration should you implement?
FAILOVER routing policy record set with a 30-second TTL, --enable-health-checking, --routing-policy-backup-data-type=GEO, and --backup-data-trickle-ratio=0.1, specifying the forwarding rule names for both the primary and backup targets.FAILOVER routing policy isA Cloud DNS FAILOVER routing policy implements active-passive traffic steering by linking a primary target set with one or more backup target sets, continuously monitored by integrated health checks. For internal passthrough Network Load Balancers, Cloud DNS inspects the health state of the underlying backend instances directly and considers a load balancer endpoint healthy as long as at least 20% of its backend instances pass their health checks.
--routing-policy-backup-data-type=GEO ensures that steady-state traffic routes solely to us-central1, while an outage shifts traffic to the healthy standby load balancer (us-east1 or europe-west1) closest to the querying VM's region.--enable-health-checking and referencing forwarding rule names (rather than raw IP addresses) enables Cloud DNS internal health probing. Enabling global access on the regional forwarding rules permits VMs in us-east1 and europe-west1 to connect to the us-central1 VIP—and vice versa during failover.--backup-data-trickle-ratio=0.1 instructs Cloud DNS to route 10% of DNS responses to healthy standby VIPs during normal operations, keeping backend caches warm and validating standby paths continuously.us-central1 automatically once its backend health rises back above the 20% threshold.1.0 to shift 100% of traffic to backup VIPs for planned maintenance.Unlike load balancer-level failover policies (which are confined to a single region) or GEO-only policies (which route regions active-active), combining a private FAILOVER policy with GEO backups, forwarding rule references, global access, and a 0.1 trickle ratio satisfies every cross-region availability, validation, and convergence requirement.
GEO routing policy record set with a 30-second TTL, --enable-health-checking, geofencing enabled, and --backup-data-trickle-ratio=0.1, mapping us-central1 to the primary forwarding rule and the other regions to the backup forwarding rules.GEO routing policy with geofencing doesA Cloud DNS GEO (geolocation) routing policy maps source regions to specific DNS targets in an active-active proximity model, returning the endpoint mapped to the querying VM's region (or the nearest healthy region if an exact match is unavailable). Enabling geofencing overrides automatic failover by strictly pinning each source geography to its assigned regional targets.
GEO policy distributes steady-state traffic across all mapped regions simultaneously (us-east1 VMs hit us-east1, and europe-west1 VMs hit europe-west1) instead of directing all steady-state traffic to us-central1.--backup-data-trickle-ratio parameter applies specifically to FAILOVER routing policies that separate primary and backup target sets; a GEO policy has no separate standby target set to receive trickle traffic.GEO policies with geofencing disabled automatically route queries to the next closest healthy region during an outage.You needed an active-active multi-region deployment with strict regional data-residency boundaries—rather than active-passive failover with standby trickle validation—and intentionally wanted traffic to stay pinned even when regional endpoints fail.
us-central1 with --failover-ratio=0.1 and attach the us-east1 and europe-west1 instance groups as --failover backend groups. Create a standard A record in the private Cloud DNS zone with a 30-second TTL pointing to the us-central1 forwarding rule IP address.--failover-ratio doFor an internal passthrough Network Load Balancer, backend service failover lets you classify instance groups or network endpoint groups (NEGs) within the same region as either primary or --failover backend groups. The --failover-ratio parameter sets the minimum proportion of healthy primary backends required before the load balancer switches eligible backends to the failover group.
us-east1 or europe-west1 instance groups to a us-central1 regional load balancer's backend service.--failover-ratio=0.1: Setting --failover-ratio=0.1 on a load balancer backend service does not trickle 10% of steady-state traffic to standby targets. Instead, it means the primary backend pool remains active until fewer than 10% of its VMs are healthy, at which point 100% of new connections shift to local failover backends.A record (rrdatas) always returns the single us-central1 VIP regardless of regional health, providing zero protection if the us-central1 region or load balancer becomes unreachable.FAILOVER policies handle multi-region resilience across independent regional VIPs.--failover-ratio is discouraged because dynamic group resizing can unexpectedly alter the healthy-to-total ratio.All primary and backup instances resided inside us-central1, you wanted intra-region failover only when primary healthy capacity dropped below 10%, and you did not need cross-region routing or steady-state trickle testing.
--source-regions matching your client regions. In the private Cloud DNS zone, create a FAILOVER routing policy record set with a 30-second TTL, --health-check referencing the global health check, and --backup-data-trickle-ratio=0.1, specifying the forwarding rule IP addresses for the primary and backup targets.A global HTTP health check configured with three --source-regions sends probes from external internet Points of Presence (PoPs) to publicly reachable endpoints. In Cloud DNS, attaching --health-check to a record set with raw IP addresses is designed for external endpoints in public zones, not internal load balancers in private zones.
gcloud commands for private DNS routing policies, specifying forwarding rule IP addresses instead of forwarding rule names fails to associate Cloud DNS health checking with the internal load balancer resources.us-east1 and europe-west1 cannot reach the primary VIP in us-central1 (and us-central1 VMs cannot reach backup VIPs during failover).--global, exactly three --source-regions, and public internet reachability over HTTP, HTTPS, or TCP.--enable-health-checking paired with forwarding rule names.The architecture used regional external Application Load Balancers (or public on-premises endpoints) in a public Cloud DNS zone, where external HTTP/HTTPS/TCP probes from three Google Cloud source regions monitor public forwarding rule IP addresses.
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