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 is deploying a mission-critical hybrid workload in a single VPC network (vpc-prod) with VM instances in us-central1 and us-east1. You must achieve a 99.99% availability SLA using Dedicated Interconnect and support active-active forwarding without packet loss or unexpected TCP connection resets during planned maintenance or single-domain failures.
You have provisioned four 10-Gbps Dedicated Interconnect connections across two metros to handle an 8-Gbps peak production workload:
int-lga-1 (lga-zone1-16) and int-lga-2 (lga-zone2-1422)int-iad-1 (iad-zone1-1) and int-iad-2 (iad-zone2-2)Which configuration meets all SLA, failover capacity, and active-active routing requirements?
vpc-prod to global dynamic routing mode, deploy two Cloud Routers in us-central1, and attach all four 10-Gbps VLAN attachments (one per interconnect connection) to us-central1. Configure identical MED values on the Cloud Router BGP sessions, apply a higher MED value on the IAD BGP sessions at the on-premises routers, and enable BGP graceful restart.This configuration enables global dynamic routing, terminates all four 10-Gbps VLAN attachments (spanning both LGA and IAD metros) into the us-central1 region using Cloud Routers in us-central1, and applies a higher MED value to the IAD sessions solely on the on-premises routers.
LGA and IAD), the four VLAN attachments must be split across two Google Cloud regions (two in us-central1 and two in us-east1), with one Cloud Router per region. Terminating all four attachments in us-central1 creates a regional single point of failure, meaning a us-central1 outage disconnects workloads in us-east1 as well.IAD at the on-premises side causes Cloud Router to load-balance egress traffic across LGA and IAD, while on-premises routers prefer LGA for return traffic—violating symmetric active-active forwarding.PRODUCTION_CRITICAL connection group and attached to that metro's corresponding low-latency region.IAD VLAN attachments were moved to a Cloud Router in us-east1 to provide regional diversity, and matching MED values were configured symmetrically for ECMP.Terminating connections from a distant metro like IAD solely in us-central1 also adds unnecessary cross-country latency for us-east1 workloads and forfeits the regional resilience required by the 99.99% SLA.
vpc-prod to global dynamic routing mode, deploy one Cloud Router in us-central1 and one in us-east1, and create four 5-Gbps VLAN attachments (one per interconnect connection). Configure identical MED values across regional BGP sessions, enable BGP graceful restart, and use ECMP with per-packet round-robin load balancing on the on-premises routers.This configuration establishes a multi-region topology using global dynamic routing and two regional Cloud Routers, but provisions 5-Gbps VLAN attachments on each 10-Gbps Dedicated Interconnect connection and relies on per-packet round-robin load balancing on the on-premises routers.
Even when the underlying physical Dedicated Interconnect links are 10 Gbps, the configured bandwidth on the VLAN attachment acts as a strict throughput ceiling that triggers drops if local-region traffic exceeds it during a single-domain failover.
vpc-prod in regional dynamic routing mode, deploy four Cloud Routers (two in us-central1 and two in us-east1) to eliminate router single points of failure, and create four 10-Gbps VLAN attachments (one per interconnect connection). Assign higher MED values to the zone2 BGP sessions on both Cloud Routers and on-premises routers, and use flow-based hashing.This configuration leaves vpc-prod in regional dynamic routing mode, deploys four Cloud Routers (two in each region), provisions four 10-Gbps VLAN attachments, and applies higher MED values to the zone2 BGP sessions on both sides of the peering.
LGA connections in us-central1 fail, VMs in us-central1 cannot reroute hybrid traffic through the us-east1 Cloud Router and IAD connections.zone2 BGP sessions demotes those links to passive backup paths, preventing active-active ECMP load balancing across both edge availability domains.vpc-prod were configured for global dynamic routing mode, identical MED values were configured across regional BGP sessions for active-active ECMP, and only one Cloud Router per region were used.If two on-premises routers are deployed for physical redundancy, they should also maintain Layer 3 connectivity with each other (using iBGP or an IGP) so routes remain reachable regardless of which link receives inbound traffic.
vpc-prod to global dynamic routing mode, deploy one Cloud Router in us-central1 and one in us-east1, and create four 10-Gbps VLAN attachments (one per interconnect connection). Configure identical MED values across regional BGP sessions, enable BGP graceful restart, and configure ECMP with flow-based hashing on the on-premises routers.This design implements Google Cloud's prescriptive multi-region 99.99% availability Dedicated Interconnect architecture paired with active-active ECMP forwarding, full per-link failover capacity, and BGP session resiliency.
LGA and IAD) and both edge availability domains (zone1 and zone2) per metro, four VLAN attachments distributed across us-central1 and us-east1, one Cloud Router per region, and global dynamic routing mode on vpc-prod.zone1 and zone2 within each metro.Compared to undersized 5-Gbps attachments, regional dynamic routing, or asymmetric MED designs, this topology satisfies every architectural, capacity, and routing prerequisite for a 99.99% SLA with deterministic active-active load balancing.
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