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 connecting two dual-stack Google Cloud VPC networks (vpc-a and vpc-b) in the same region using HA VPN gateways and Cloud Routers (router-a and router-b) with two VPN tunnels (tunnel-0 and tunnel-1). Your design must satisfy the following requirements:
tunnel-0 as the active path with tunnel-1 serving as a passive failover path instead of load balancing across both tunnels.How should you configure the HA VPN tunnels and BGP sessions on router-a and router-b?
IPV4_IPV6) HA VPN gateways, and configure one IPv4 BGP session per tunnel with IPv6 traffic (MP-BGP) enabled. Assign unique /30 subnets from 169.254.0.0/16 for the BGP IPv4 peering addresses across both tunnels and IPv6 next-hop addresses from 2600:2d00:0:2::/63. Configure distinct private ASNs (65001 and 65002) on the Cloud Routers, and set a lower Advertised route priority (MED) on tunnel-0 (100) than on tunnel-1 (200).This configuration implements Multiprotocol BGP (MP-BGP) over dual-stack HA VPN gateways to connect two Google Cloud VPC networks securely while enforcing deterministic active/passive failover through Advertised route priority (MED).
IPV4_IPV6) HA VPN gateways with IKEv2 tunnels is mandatory for IPv6 traffic. Creating a single IPv4 BGP session per tunnel with IPv6 route exchange enabled uses MP-BGP to advertise both IPv4 and IPv6 prefixes over one BGP session./30 subnet from 169.254.0.0/16 (using the first and second usable host IPs) that is unique across all Cloud Routers in all regions of each VPC. Because IPv6 prefixes are exchanged inside an IPv4 MP-BGP session, manual IPv6 next-hop addresses are allocated from the Google-owned Global Unicast Address (GUA) range 2600:2d00:0:2::/63.100 on tunnel-0 and MED 200 on tunnel-1 ensures all traffic uses tunnel-0 during normal operation and automatically fails over to tunnel-1 if tunnel-0 or its BGP session goes down.65001 and 65002 uses valid 16-bit private ASNs (64512–65534), establishing clean eBGP peering between router-a and router-b.tunnel-0 upon tunnel or BGP failure, shifting traffic seamlessly to tunnel-1.Using MP-BGP on a single IPv4 BGP session per tunnel with properly scoped 169.254.0.0/16 /30 peering blocks, 2600:2d00:0:2::/63 next hops, valid private ASNs, and asymmetric MED values is the exact supported architecture for dual-stack active/passive VPC-to-VPC HA VPN connectivity.
IPV4_IPV6) HA VPN gateways, and configure one IPv4 BGP session per tunnel with IPv6 traffic (MP-BGP) enabled. Assign the same /30 subnet from 169.254.0.0/16 across both tunnels using distinct host IPs, and configure IPv6 next-hop addresses from fdff:1::/64. Configure distinct private ASNs (65001 and 65002), and set a higher Advertised route priority (MED) on tunnel-0 (200) than on tunnel-1 (100).This option correctly selects dual-stack HA VPN gateways, IKEv2, MP-BGP over a single IPv4 BGP session, and valid private ASNs, but fails on BGP IPv4 subnet uniqueness, IPv6 next-hop addressing, and MED priority ordering.
/30 subnet contains only four IP addresses—one network address, two usable host addresses, and one broadcast address—so two separate point-to-point BGP sessions cannot share the same /30 subnet with distinct host IPs. Furthermore, every BGP session's IPv4 /30 range must be unique among all Cloud Routers in all regions of a VPC network.fdff:1::/64 ULA prefix is designated for IPv6 BGP peering addresses (when running an IPv6 BGP session), not for IPv6 next-hop addresses on an IPv4 MP-BGP session, which require addresses from 2600:2d00:0:2::/63.200 to tunnel-0 and MED 100 to tunnel-1 makes tunnel-1 the primary active path and tunnel-0 the passive backup, violating the failover requirement./30 block in 169.254.0.0/16 supports exactly one BGP peering pair (Cloud Router IP and BGP peer IP).0 to 65535) indicate higher route preference.Each tunnel received its own unique /30 subnet from 169.254.0.0/16, IPv6 next hops were selected from 2600:2d00:0:2::/63, and tunnel-0 was configured with the lower MED (100) instead of tunnel-1.
IPV4_IPV6) HA VPN gateways, and configure one IPv4 BGP session per tunnel with IPv6 traffic (MP-BGP) enabled. Assign unique /30 subnets from 169.254.0.0/16 for the BGP IPv4 peering addresses and IPv6 next-hop addresses from 2600:2d00:0:2::/63. Configure ASN 16550 on router-a and 65002 on router-b, and set the same Advertised route priority (MED) of 100 on both tunnel-0 and tunnel-1.This configuration correctly sets up single-session MP-BGP over IKEv2 tunnels with valid IPv4 peering subnets and IPv6 next-hop addresses, but it misconfigures both the Cloud Router ASN and the Multi-Exit Discriminator (MED) routing policy.
16550 to router-a violates HA VPN ASN rules. ASN 16550 is reserved for Cloud Routers managing Partner Interconnect VLAN attachments, whereas Cloud Routers managing HA VPN tunnels must use a private ASN (64512–65534 or 4200000000–4294967294).100) on both tunnel-0 and tunnel-1 instructs BGP and VPC dynamic routing to treat both paths as equal cost. Instead of active/passive failover, traffic is load-balanced across both tunnels using Equal-Cost Multipath (ECMP) routing.16550 is specifically tailored for Partner Interconnect constraints.router-a were managing a Partner Interconnect attachment (requiring ASN 16550) and the network architecture required active/active ECMP load balancing across redundant paths rather than deterministic active/passive failover.
Because Cloud Router ASNs cannot be modified after creation, verifying private ASN allocations before provisioning HA VPN BGP sessions prevents disruptive router rebuilds.
IPV4_IPV6) HA VPN gateways, and configure both an IPv4 BGP session and an IPv6 BGP session on each tunnel with MP-BGP enabled. Assign unique /30 subnets from 169.254.0.0/16 for IPv4 peering and /64 ULA addresses from fdff:1::/64 for IPv6 peering. Use distinct private ASNs (65001 and 65002), and configure a lower MED value on tunnel-0 (100) than on tunnel-1 (200).This configuration establishes dual-stack HA VPN gateways using IKEv2 and attempts to run parallel IPv4 and IPv6 BGP sessions inside each VPN tunnel while simultaneously enabling Multiprotocol BGP (MP-BGP) on those sessions.
fdff:1::/64 Unique Local Address (ULA) block is reserved for IPv6 BGP session peering interfaces, whereas MP-BGP over an IPv4 session requires IPv6 next-hop addresses from 2600:2d00:0:2::/63.The design explicitly required separate single-family BGP sessions (without MP-BGP) to isolate IPv4 and IPv6 control planes in each tunnel using link-local 169.254.0.0/16 addresses for IPv4 peering and fdff:1::/64 addresses for IPv6 peering.
When using MP-BGP on a single IPv4 BGP session, enabling IPv6 route exchange allows both address families to share one TCP port 179 session while avoiding duplicate BGP state machines.
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