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 application in the us-east4 region of a Google Cloud VPC (prod-vpc). Stateful firewalls in your on-premises data centers require symmetric traffic flows across hybrid links. Your connectivity design must satisfy these requirements:
us-east4) and two Partner Interconnect connections in Dallas (us-central1).Which architecture and BGP configuration should you implement?
Layer 3 Partner Interconnect delegates Border Gateway Protocol (BGP) peering management to a third-party network service provider. In this model, the service provider's autonomous system (AS) sits between your on-premises routers and Google Cloud's Cloud Router, establishing separate BGP sessions with each side rather than a direct end-to-end BGP session between your routers and Google Cloud.
us-central1 instead of Layer 3, allowing direct eBGP peering between your on-premises routers and Cloud Router so MED values are preserved.While AS-Path prepending can pass across autonomous systems, Cloud Router requires direct Layer 2 peering when deterministic MED policies must be synchronized across both Dedicated and Partner Interconnect links.
This configuration attempts to combine Dedicated Interconnect, Layer 2 Partner Interconnect, and HA VPN while keeping prod-vpc in Regional dynamic routing mode, placing all redundant circuits within a single edge availability domain (zone1) per metropolitan area, and terminating only a single VPN tunnel on interface 0.
zone1 and zone2). Placing both circuits in zone1 creates a single maintenance and fault domain per metro.us-central1 only advertises and learns routes for us-central1. If both Ashburn connections fail, on-premises traffic cannot reach us-east4 workloads via Dallas.interface 0 leaves interface 1 unused, disqualifying the HA VPN gateway from its availability SLA.zone1 and zone2 within a metro so only one domain is impacted at a time; deploying only in zone1 exposes both circuits to simultaneous downtime.prod-vpc to Global dynamic routing mode, distributed each metro's connections across both zone1 and zone2, and configured tunnels on both interface 0 and interface 1 of the HA VPN gateway.Even when all compute workloads reside in a single region like us-east4, multi-region 99.99% SLA topologies mandate Global dynamic routing so the secondary region's Cloud Router can carry failover traffic to us-east4 subnets.
This option correctly enables Global dynamic routing, uses Layer 2 Partner Interconnect, and distributes Interconnect circuits across zone1 and zone2 in both metros. However, it applies higher MED values only on the Cloud Router side for the secondary path and configures an active-passive tunnel pair across two separate HA VPN gateways.
For deterministic active-passive failover across redundant Cloud Interconnect topologies, Google Cloud best practices explicitly require matching higher MED priorities on both the Cloud Router and peer router sides.
This design establishes a 99.99% availability SLA hybrid network combining Dedicated Interconnect in us-east4 and Layer 2 Partner Interconnect in us-central1, backed by a redundant HA VPN gateway. By using Global dynamic routing and synchronized bidirectional BGP metrics, traffic flows symmetrically across deterministic primary, secondary, and tertiary tiers.
zone1 and zone2 in Ashburn alongside two Partner Interconnect connections across zone1 and zone2 in Dallas meets Google Cloud's multi-region, dual-metro, dual-edge availability domain requirements. Global dynamic routing ensures us-east4 subnets remain reachable through us-central1 during an Ashburn outage.us-east4 enables Equal-Cost Multi-Path (ECMP) active-active load balancing across the Dedicated Interconnect links. Higher MED values on the Layer 2 Partner Interconnect BGP sessions keep Dallas as a standby path until both Ashburn circuits fail.interface 0 and interface 1 of the HA VPN gateway preserves VPN redundancy, while the highest MED values and AS-Path prepending ensure traffic only traverses the internet-based tunnels if all four Interconnect attachments fail.zone1 and zone2 in each metro ensures planned Google Cloud maintenance never takes down both links in a metro simultaneously.Unlike Layer 3 Partner Interconnect, Layer 2 preserves end-to-end MED visibility, and unlike Regional routing or single-side MED tuning, Global dynamic routing with bidirectional MED alignment guarantees full reachability and firewall flow symmetry.
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