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 runs a stateless HTTP(S) application on autoscaled regional Managed Instance Groups (MIGs) in us-central1 and europe-west1. You must implement capacity-aware global backend load balancing with active-passive failover to regional external Application Load Balancers that share the same MIG backends.
During failover drills, you observe these issues:
us-central1 proxy-only subnet lacks capacity for failover Envoy proxies.Which configuration set should you implement?
This option substitutes regional external passthrough Network Load Balancers (Layer 4) for regional external Application Load Balancers (Layer 7), attempts to enable Cloud CDN at the regional layer, uses Standard Network Service Tier, and retains a RATE-based global backend service. While passthrough Network Load Balancers support regional backend failover policies (--failover-ratio and --connection-drain-on-failover), they operate very differently from Envoy-based Application Load Balancers.
RATE-based backend service without risking 2x traffic overload during failover.--failover-ratio) on passthrough Network Load Balancers only fail over between primary and failover backend pools within the same region, not across global-to-regional load balancer tiers.RATE balancing or Cloud CDN incompatibilities.This answer would be partially applicable only if the workload used non-HTTP(S) Layer 4 traffic (such as UDP or raw TCP requiring source IP preservation) within a single region needing zonal primary-to-failover pool redirection.
This option attempts to manage shared-backend failover using RATE balancing mode, load-balancer-utilization autoscaling, in-place subnet expansion, and a unified aggressive health check. While RATE balancing and load-balancer-based autoscaling are common in standalone single-load-balancer deployments, combining them across shared primary and backup load balancers violates critical operational constraints.
RATE balancing mode on both global and regional backend services attached to the same MIGs causes instances to receive traffic simultaneously from both load balancers up to each balancer's target rate, resulting in double traffic during failover and failback.expand-ip-range command the way you expand a standard subnet's primary IP range. Attempting this fails, leaving the us-central1 Envoy proxy pool exhausted.RATE mode targets requests per second per instance without reflecting actual CPU saturation across multiple independent load balancer frontends.This answer would be closer to correct only if each load balancer used completely non-overlapping backend MIGs (avoiding shared-backend restrictions), the subnet being expanded was a regular backend subnet rather than a proxy-only subnet, and a separate conservative health check was assigned to MIG autohealing.
This configuration establishes a resilient active-passive global-to-regional failover architecture for global external Application Load Balancers sharing regional Managed Instance Group (MIG) backends with backup regional external Application Load Balancers. It aligns Cloud DNS failover routing policies, backend balancing modes, MIG autoscaling, Envoy proxy-only subnet capacity, and health check separation so traffic shifts cleanly during outages and failback without capacity collapse or backend overload.
UTILIZATION balancing mode ensures both load balancers coordinate backend capacity awareness rather than sending independent request-rate streams (RATE) that would deliver 2x traffic to shared instances during transitions. Adding a connection draining timeout allows in-flight requests to finish gracefully during backend changes.Unlike active-active bypass or Layer 4 passthrough alternatives, this design satisfies every requirement of a shared-backend active-passive Layer 7 failover architecture while respecting Google Cloud platform constraints on autoscaling signals, balancing modes, proxy-only subnet updates, and health check isolation.
This option switches from an active-passive design to an active-active (global-to-regional bypass) topology using an INTERNET_FQDN_PORT network endpoint group (NEG), adjusts Cloud DNS health check parameters, and relocates the backup regional load balancers to a third region. Active-active bypass routes steady-state traffic sequentially through the global tier to regional external Application Load Balancers.
INTERNET_FQDN_PORT NEG to the nearest regional load balancer, which balances traffic only locally and cannot spill traffic across regions based on backend capacity. Workloads requiring capacity-aware global backend load balancing must use the active-passive strategy.us-central1 and europe-west1), because regional load balancers can only reach backends within their own region.INTERNET_FQDN_PORT NEGs point to regional DNS records rather than directly attaching MIGs to the global backend service.This answer would be correct if the application relied on regional isolation rather than capacity-based cross-region traffic spilling, the backup regional load balancers were placed in the same regions as their local backends, and the Cloud DNS health check used three source regions with at least a 30-second interval.
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