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 uses an HA VPN connection between its on-premises data center and a Google Cloud VPC network (prod-vpc) with Cloud Router cr-central in us-central1. An existing BGP session (bgp-peer-1) uses RFC 2385 MD5 authentication with a key named bgppeer-1-key, whose plaintext value was not recorded.
You need to add a redundant BGP session (bgp-peer-2) via the compute.routers.patch API and tune routing policies to meet these requirements:
bgp-peer-2 on a /30 subnet without causing VPC-wide IP conflicts.bgp-peer-1 authenticated and undisturbed.bgp-peer-1 with a Multi-Exit Discriminator (MED) of 50 are not overridden by backup advertisements on bgp-peer-2 that omit the MED attribute.Which configuration should you apply?
169.254.2.1 and 169.254.2.2 from a /30 subnet unused across all regions of prod-vpc. In compute.routers.patch, include both {"name": "bgppeer-1-key"} (omitting key) and {"name": "bgppeer-2-key", "key": "<16-char-secret>"} in md5AuthenticationKeys, and reference bgppeer-2-key on the new peer. Leave the MED attribute unset on bgp-peer-2 so Cloud Router defaults its priority to 100 and prefers bgp-peer-1.This option correctly configures link-local addressing and retains bgppeer-1-key via compute.routers.patch, but relies on omitting the MED attribute from bgp-peer-2 advertisements to make it act as a backup link.
0), rather than 100.bgp-peer-2 with an implicit MED of 0 will beat routes received on bgp-peer-1 with a MED of 50, overriding the primary path.100 is commonly used as a default advertised route priority for Cloud Router's own outbound advertisements or sample templates, Cloud Router does not assign 100 to inbound peer routes that lack a MED.The primary tunnel (bgp-peer-1) advertised a MED of 0 (or also omitted MED while using other tie-breakers) and you intended active/active ECMP forwarding rather than active/passive failover with a MED of 50.
169.254.2.1 and 169.254.2.2 from a /30 subnet unused across all regions of prod-vpc. In compute.routers.patch, include both {"name": "bgppeer-1-key"} (omitting key) and {"name": "bgppeer-2-key", "key": "<16-char-secret>"} in md5AuthenticationKeys, and reference bgppeer-2-key on the new peer. Explicitly configure the on-premises router to advertise a MED greater than 50 (such as 200) on bgp-peer-2.This configuration combines VPC-wide unique link-local IPv4 addressing, RFC 2385 MD5 peer authentication, and explicit Multi-Exit Discriminator (MED) policy control to secure and govern dual-tunnel BGP peering on Cloud Router.
169.254.2.1 and 169.254.2.2 from an unused 169.254.2.0/30 subnet uses the valid first and second host addresses (reserving .0 for network and .3 for broadcast). Ensuring the /30 range is unique across all Cloud Routers in all regions of prod-vpc prevents global VPC routing collisions.md5AuthenticationKeys via compute.routers.patch, listing {"name": "bgppeer-1-key"} without the key field instructs Google Cloud to retain the existing secret without exposing it, while adding {"name": "bgppeer-2-key", "key": "<16-char-secret>"} manually supplies a length-compatible key for the on-premises device.0), explicitly advertising a MED above 50 (such as 200) on bgp-peer-2 ensures bgp-peer-1 (MED 50) remains the primary path.It is the only option that respects Cloud Router's /30 link-local host rules, preserves an unrecorded MD5 key during a PATCH operation, and accounts for RFC 4271's default 0 MED interpretation.
169.254.2.1 and 169.254.2.2 from a /30 subnet unused across all regions of prod-vpc. In compute.routers.patch, include only {"name": "bgppeer-2-key", "key": "<16-char-secret>"} in md5AuthenticationKeys so existing keys remain untouched, and reference bgppeer-2-key on the new peer. Explicitly configure the on-premises router to advertise a MED greater than 50 (such as 200) on bgp-peer-2.This approach correctly selects valid link-local host addresses and an explicit backup MED, but attempts an incremental compute.routers.patch update to md5AuthenticationKeys by specifying only the newly added key.
bgp-peer-1 authenticated and undisturbed: In the Compute Engine routers.patch API, the md5AuthenticationKeys array defines the complete set of active keys on the Cloud Router. Omitting bgppeer-1-key from the md5AuthenticationKeys array does not leave it untouched—every retained key must still be declared by name in the array.bgppeer-1-key from md5AuthenticationKeys while bgp-peer-1 still references md5AuthenticationKeyName: "bgppeer-1-key" causes the patch to fail validation or drop the key reference, disrupting the active production session.md5AuthenticationKeys requires listing every key name that should remain configured on the router.key property for existing entries in md5AuthenticationKeys precisely so administrators can retain existing keys without knowing their plaintext values.The administrator intended to remove bgp-peer-1 and its associated MD5 key entirely from the Cloud Router, or used the gcloud compute routers add-bgp-peer CLI command instead of raw API PATCH payloads to add the second peer independently.
169.254.2.0 and 169.254.2.1 from a /30 subnet unused in us-central1. Run gcloud compute routers get-status to retrieve the plaintext bgppeer-1-key value, include both keys in md5AuthenticationKeys, and use the Console's Generate and copy option for bgp-peer-2. Explicitly configure the on-premises router to advertise a MED greater than 50 (such as 200) on bgp-peer-2.This option attempts to allocate link-local BGP addresses starting at .0, limit uniqueness checks to a single region, retrieve an existing MD5 secret via status commands, and use the Console's auto-generated key feature.
/30 host addressing: In 169.254.2.0/30, 169.254.2.0 is the reserved network address and 169.254.2.3 is the broadcast address. Cloud Router requires the first and second host addresses (.1 and .2)./30 range must be unique across all Cloud Routers in all regions of prod-vpc, not merely within us-central1.gcloud compute routers get-status only outputs md5AuthEnabled (a boolean) and statusReason (such as MD5_AUTH_INTERNAL_PROBLEM)./30 from 169.254.0.0/16, only the middle two IPs are usable for BGP peering, and overlapping ranges in another region of the same VPC will fail configuration.Valid .1/.2 host addresses were selected globally across the VPC, bgppeer-1-key was retained by omitting its key field, and a custom 16-character key was supplied manually via CLI, API, or Console text input.
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