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 connects an on-premises Cisco router to a VPC network via a Dedicated Interconnect VLAN attachment (dataplaneVersion: 2) and Cloud Router (cr-hybrid-prod) with BFD enabled. After you enable MD5 authentication by generating a key in the Google Cloud console and pasting it into the on-premises router, the BGP session fails to re-establish.
You inspect the diagnostics and configurations:
get-status: state: Connect, status: DOWN, md5AuthEnabled: true (no statusReason field)gce_router): Only Successfully added configuration for peers: peer-dc1 (no CONFIG_DISABLED, LINK_DOWN, or NOTIFICATION_RECEIVED entries)ACTIVE; ARP cache includes 169.254.10.2| Setting | Cloud Router | On-Premises Router |
|---|---|---|
| Local / Peer ASN | 65010 / 65020 | 65020 / 65010 |
| Interface IP | 169.254.10.1/29 | 169.254.10.2/29 |
| Neighbor IP | 169.254.10.2 | 169.254.10.1 |
| eBGP Multihop | Managed | 2 |
What is the most likely root cause of the BGP session failure, and how should you resolve it?
MD5_AUTH_INTERNAL_PROBLEM); wait up to one hour for Cloud Router to recover automatically, or contact Google Cloud Support if the session remains down.MD5_AUTH_INTERNAL_PROBLEM isMD5_AUTH_INTERNAL_PROBLEM is a specific statusReason value reported on a Cloud Router BGP peer when an internal Google Cloud control-plane failure prevents Cloud Router from programming the MD5 authentication configuration for that session.
MD5_AUTH_INTERNAL_PROBLEM, the BGP peer transitions to the Idle state, whereas the diagnostic output here explicitly reports Connect.statusReason field: get-status shows md5AuthEnabled: true without any statusReason value, demonstrating that Cloud Router successfully provisioned MD5 authentication on its side.MD5_AUTH_INTERNAL_PROBLEM is an internal Cloud Router fault that does not require configuration changes to your peer router or shared key.Idle state.Idle session with MD5_AUTH_INTERNAL_PROBLEM fails to recover after more than one hour.The gcloud compute routers get-status output showed the BGP session in the Idle state with md5AuthEnabled: true and statusReason: MD5_AUTH_INTERNAL_PROBLEM.
BGP MD5 authentication secures a Border Gateway Protocol (BGP) peering session by signing every TCP segment on port 179 with a shared secret key. Both Cloud Router and the on-premises peer router must share the exact same key string; otherwise, TCP segments are silently dropped or rejected before the BGP session can transition out of the initial handshake phase.
Connect, DOWN): A Connect state with md5AuthEnabled: true and no statusReason field shows that Cloud Router successfully applied the MD5 configuration locally and is actively attempting to open the TCP connection, but cannot complete the handshake with the peer.ACTIVE LACP status, a valid ARP entry for 169.254.10.2, matching /29 link-local subnet masks, properly swapped ASNs (65010 and 65020), and the absence of LINK_DOWN or CONFIG_DISABLED logs confirm that physical, Layer 2, and Layer 3 prerequisites are intact.gcloud, or API using the exact manual key.Connect to Established (UP).Unlike internal Google Cloud errors (which place the session in Idle state) or BFD timer failures (which log CONFIG_DISABLED), a key mismatch caused by an overly long auto-generated secret requires explicit manual key alignment on both peers to restore TCP authentication.
ebgp-multihop 2 configuration, causing the BFD control detection timer to expire; configure fall-over bfd single-hop on the on-premises router.Bidirectional Forwarding Detection (BFD) provides sub-second or rapid link failure detection for Cloud Router BGP sessions over VLAN attachments running Dataplane version 2. Cloud Router supports only BFD single-hop mode (without BFD authentication); if an on-premises router inherits BFD multi-hop mode from an ebgp-multihop statement, BFD packets will not align and the control detection timer will expire.
CONFIG_DISABLED logs: When the BFD control detection timer expires on a BFD-enabled Cloud Router session, Cloud Router intentionally tears down the session and logs a CONFIG_DISABLED event in Cloud Logging. No CONFIG_DISABLED entries exist in the logs.Connect: The BGP peer has not completed TCP/BGP establishment since MD5 authentication was enabled, whereas BFD detection timer expiration stops the BGP session to immediately signal an error state to the peer.ebgp-multihop was first configured.1000ms and a minimum multiplier of 5.ebgp-multihop or configuring neighbor x.y.y.z fall-over bfd single-hop is a valid BFD best practice on Cisco devices, but it will not fix an MD5 TCP authentication mismatch.Cloud Logging contained a CONFIG_DISABLED entry (and BFD flap metrics recorded ControlDetectionTimeExpired) immediately after enabling BFD alongside ebgp-multihop without MD5 key discrepancies.
BGP route policies filter or modify route attributes (such as MED, AS path, or communities) for inbound learned routes and outbound advertised routes on an active BGP session. Separately, Cloud Router enforces a hard limit of 5,000 received prefixes per BGP peer session to protect control-plane stability.
NOTIFICATION log entry: When an on-premises router advertises more than 5,000 prefixes, Cloud Router explicitly logs BGP: Sent NOTIFICATION 6/1 (CEASE/MAX_PREFIXES_REACHED) before closing the session. No NOTIFICATION or max-prefix messages appear in Cloud Logging.Established state. A restrictive route policy can drop or filter prefixes, but it never keeps a BGP session stuck in Connect.CONFIG_DISABLED log is present, the session was not administratively shut down or stopped by a prefix-limit cease event.gcloud compute routers list-bgp-routes with --no-policy-applied or --policy-applied.Cloud Logging recorded BGP: Sent NOTIFICATION 6/1 (CEASE/MAX_PREFIXES_REACHED) and the session closed after the on-premises router advertised over 5,000 prefixes.
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