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.
You are troubleshooting a newly provisioned Layer 2 Partner Interconnect VLAN attachment (l2-attach-1) connecting an on-premises router to a 1500-byte MTU VPC network. The VLAN attachment status shows as down, and the Cloud Router BGP session fails to establish.
Diagnostic checks reveal the following:
gcloud compute interconnects attachments describe l2-attach-1 omits the dataplaneVersion field.ping from the on-premises subinterface (169.254.10.2) to cloudRouterIpAddress (169.254.10.1) succeeds with 0% loss.ip mtu 1460, remote-as 16550, BFD enabled, and omits ebgp-multihop to enforce single-hop BFD.What should you do to resolve the BGP peering issue?
16550.Partner Interconnect supports two distinct connectivity models: Layer 2 and Layer 3. In a Layer 3 Partner Interconnect deployment, the service provider's edge router terminates the BGP session with Google's Cloud Router, requiring the Cloud Router BGP peer to be configured with the service provider's Autonomous System Number (ASN).
16550 for Cloud Router on Partner Interconnect connections. Changing the on-premises remote-as away from 16550 would cause an ASN mismatch and actively prevent BGP peering from ever establishing.16550), retaining end-to-end control over Multi-Exit Discriminator (MED) values and route priorities.cloudRouterIpAddress.The organization had provisioned a Layer 3 Partner Interconnect connection where the service provider managed the BGP session, and Cloud Router had been misconfigured with the customer's internal ASN instead of the service provider's ASN.
Optical power diagnostics and bidirectional demarc loops are Layer 1 troubleshooting procedures used by circuit and Partner Interconnect providers to isolate physical transport faults. When a port experiences a loss of optic power, hardware cannot detect a light signal from the opposite end due to a faulty transceiver, dirty or damaged fiber, or a broken transport system.
ping from 169.254.10.2 to 169.254.10.1 succeeded with 0% packet loss. Because IP packets are successfully traversing the fiber, transceivers, service provider switches, and VLAN 1010 trunk in both directions, the physical transport layer is healthy.cloudRouterIpAddress.ping before escalating physical transport faults to a carrier.The link-local ICMP ping to 169.254.10.1 failed completely, interface counters showed input errors or low receive optical power, and you needed to isolate whether a physical fiber or transceiver fault resided on the provider side or Google's side of the demarc.
1460 bytes to 1500 bytes to match the VPC network MTU.Maximum Transmission Unit (MTU) defines the largest IP packet size, in bytes, that an interface or network path can transmit without fragmentation. Partner Interconnect VLAN attachments and on-premises router subinterfaces support standardized MTU sizes of 1440, 1460, 1500, or 8896 bytes depending on the attachment and VPC network design.
179 with small handshake and keepalive segments well under 1460 bytes, so a 1460-byte interface MTU will not prevent a BGP session from establishing.1 will still fail before reaching Cloud Router.1460 and 1500 bytes are valid MTU values for Partner Interconnect configurations.1460-byte subinterface path.The BGP session were already established and small ICMP ping probes succeeded, but large data-plane packets (between 1461 and 1500 bytes) were silently dropped or fragmented across the link due to an end-to-end MTU mismatch with jumbo or 1500-byte VPC payloads.
4 on the on-premises router and disable BFD on the BGP session.In Cloud Interconnect, VLAN attachments operate on either Dataplane version 1 or Dataplane version 2. When gcloud compute interconnects attachments describe omits the dataplaneVersion field, the attachment runs on Dataplane version 1. Under this architecture, BGP control-plane packets traverse multiple internal hops between the customer edge and the Cloud Router software tasks, requiring EBGP multi-hop to prevent packets from being dropped when their Time to Live (TTL) reaches zero.
4 allows BGP Open and Keepalive packets to survive the multi-hop internal path on Dataplane version 1, bringing both the BGP session and the VLAN attachment status up.ebgp-multihop.dataplaneVersion value of 2 indicates Dataplane v2 support; the absence of this field confirms Dataplane version 1.4 as the standard recommended TTL.ebgp-multihop must never be combined when BFD inherits multi-hop behavior.ping between 169.254.10.2 and 169.254.10.1 confirms that Layer 1 optics, 802.1Q VLAN tagging, and link-local IP addressing are already healthy.Rather than unnecessarily modifying valid MTU settings or escalating healthy physical circuits to the carrier, enabling ebgp-multihop 4 and disabling BFD directly addresses the architectural requirement of Dataplane version 1 VLAN attachments.
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