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.
A global enterprise is deploying a 99.99% availability Partner Interconnect topology across two metropolitan areas to connect its on-premises data centers to a Google Cloud VPC. The network engineering team has established the following design requirements:
Which Partner Interconnect connectivity model and configuration workflow should the team implement?
A Layer 2 Partner Interconnect connection provides a bridged virtual circuit between your on-premises router and Google Cloud, giving you full control over BGP peering. However, this option incorrectly blends Layer 3 automation features—specifically pre-activation, automatic peer ASN assignment, and provider-configured custom IP ranges—into a Layer 2 workflow.
partnerMetadata field to confirm the expected service provider paired with your pairing key before enabling traffic.No such hybrid workflow exists in Google Cloud; instead, Layer 2 requires manual customer configuration of custom IPs at creation and manual peer ASN entry, whereas Layer 3 provides automated provider BGP setup and pre-activation benefits.
Layer 2 Partner Interconnect operates as a bridged Ethernet virtual circuit across the service provider's network, extending Layer 2 connectivity directly between your on-premises routers and your Google Cloud Cloud Routers. Because the service provider does not insert its own Layer 3 routing hop or Autonomous System (AS) into the BGP control plane, your organization maintains direct end-to-end eBGP peering.
Unlike Layer 3 Partner Interconnect—which abstracts BGP management to the service provider at the cost of stripping MED attributes and deferring IP configuration—Layer 2 gives network engineers complete control over routing policy, IP addressing, and session security.
Layer 3 Partner Interconnect is a routed connectivity model in which the service provider terminates the BGP session from Google Cloud on its own edge router and routes traffic between your on-premises network and your VPC. While this model reduces on-premises BGP configuration overhead, it introduces routing and IP provisioning constraints that conflict with the stated requirements.
You wanted to minimize on-premises BGP administration using automated provider peering and pre-activation, did not need MED-based active/passive traffic engineering, and were willing to let the service provider configure custom peering IP ranges.
In a Layer 3 Partner Interconnect architecture, the service provider establishes eBGP sessions directly between its edge routers and your Cloud Routers, while maintaining separate routing (such as BGP or a static default route) toward your on-premises network. This option correctly identifies that the service provider configures custom IP ranges after pairing, but it relies on a misconception about BGP MED behavior.
Your organization preferred delegating BGP peering and custom IP allocation to a Layer 3 service provider and did not require MED propagation, direct Cloud Router peer ASN management, or self-service MD5 authentication.
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