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 is deploying dual-stack Google Kubernetes Engine (GKE) clusters using VPC subnets configured with the IPV4_IPV6 stack type and INTERNAL IPv6 access. Your VPC connects to an on-premises data center over two Dedicated Interconnect connections with dual-stack (IPV4_IPV6) VLAN attachments and active IPv4 BGP sessions on Cloud Router. You must meet these requirements:
How should you configure Cloud Router and your on-premises routers?
--enable-ipv6, retrieve each VLAN attachment's customerRouterIpv6Address, assign those addresses to the corresponding on-premises VLAN subinterfaces, and apply outbound route policies on the on-premises routers to set the IPv6 next hop to each attachment's customerRouterIpv6Address.Multiprotocol BGP (MP-BGP) extends standard BGP-4 so a single IPv4 BGP peering session can carry Network Layer Reachability Information (NLRI) for both IPv4 and IPv6 unicast address families. On a dual-stack (IPV4_IPV6) Dedicated Interconnect VLAN attachment, Google Cloud automatically allocates both IPv4 link-local addresses and a /125 IPv6 link subnet (cloudRouterIpv6Address and customerRouterIpv6Address) to support IPv6 forwarding.
gcloud compute routers update-bgp-peer with --enable-ipv6 activates the IPv6 address family on the existing IPv4 BGP peers, allowing Cloud Router to advertise the IPV4_IPV6 GKE subnet IPv6 ranges and learn on-premises IPv6 prefixes without adding separate IPv6 BGP sessions.customerRouterIpv6Address (via gcloud compute interconnects attachments describe), configuring it on the corresponding on-premises VLAN subinterface, and applying an outbound route-map or policy-statement (such as set ipv6 next-hop or include-mp-next-hop) ensures Cloud Router receives valid IPv6 next hops.--enable-ipv6 preserves existing IPv4 peering while extending reachability to dual-stack GKE subnets.cloudRouterIpv6Address and customerRouterIpv6Address pairs on each attachment.Compared to parallel dual-session BGP or overlay VPNs, enabling MP-BGP on existing IPv4 BGP peers with explicit outbound customerRouterIpv6Address next-hop policies is the most efficient, resilient, and native design for dual-stack Dedicated Interconnect hybrid connectivity.
--enable-ipv6, manually specify --ipv6-nexthop-address and --peer-ipv6-nexthop-address values from the 2600:2d00:0:2::/63 range on Cloud Router, and enable the IPv6 address family on the on-premises IPv4 BGP neighbors without an outbound next-hop policy.When configuring MP-BGP over an IPv4 BGP session, flags such as --ipv6-nexthop-address and --peer-ipv6-nexthop-address allow administrators to manually assign IPv6 Global Unicast Addresses (GUA) from Google's reserved 2600:2d00:0:2::/63 range for HA VPN tunnels.
This configuration fails on both the Google Cloud and on-premises sides for Dedicated Interconnect:
cloudRouterIpv6Address and customerRouterIpv6Address to each dual-stack VLAN attachment.customerRouterIpv6Address, preventing Cloud Router from installing valid IPv6 forwarding routes for the GKE subnets.2600:2d00:0:2::/63 manual next-hop pool is strictly for HA VPN MP-BGP over IPv4 sessions, whereas Dedicated Interconnect assigns addresses automatically per VLAN attachment.customerRouterIpv6Address /125 address to the tagged VLAN subinterface so Layer 3 IPv6 forwarding matches the BGP next-hop attribute.Established, missing or mismatched IPv6 next-hop attributes prevent on-premises and GKE dual-stack traffic from routing properly.You were configuring MP-BGP on an IPv4 BGP session for a dual-stack HA VPN tunnel (where 2600:2d00:0:2::/63 manual next-hop assignment is supported) rather than Dedicated Interconnect VLAN attachments, and still applied valid peer next-hop policies.
HA VPN over Cloud Interconnect layers IPsec-encrypted HA VPN gateways and tunnels across Dedicated Interconnect VLAN attachments. This architecture uses two Cloud Routers per region: an encrypted Cloud Router (--encrypted-interconnect-router) managing the underlay VLAN attachments and a standard VPN Cloud Router managing the encrypted overlay BGP sessions.
This design is both architecturally unsupported with the existing attachments and fails the scenario requirements:
IPV4_IPV6 dual-stack VLAN attachments for HA VPN over Cloud Interconnect deployments.Your security policy mandated IPsec encryption in transit over Dedicated Interconnect and you provisioned IPv4-only VLAN attachments as the underlay for HA VPN gateways rather than using dual-stack VLAN attachments.
--ip-version=IPV6) and new IPv6 BGP peers to Cloud Router for each VLAN attachment, and enable MP-BGP on both the IPv4 and IPv6 BGP peers so both address families are exchanged across parallel sessions.Running parallel IPv4 and IPv6 BGP sessions on a dual-stack Dedicated Interconnect VLAN attachment creates two separate Cloud Router interfaces and two independent BGP peering sessions over the same physical link: an IPv4 BGP session dedicated to IPv4 prefixes and an IPv6 BGP session dedicated to IPv6 prefixes.
This approach directly conflicts with Cloud Router's MP-BGP rules and violates the stated design constraints:
--enable-ipv6 on an IPv4 peer or --enable-ipv4 on an IPv6 peer while both sessions exist causes a configuration conflict; you must first remove the separate IPv6 peer and interface before enabling MP-BGP on the IPv4 session.You wanted to isolate IPv4 and IPv6 routing control planes into separate BGP sessions without using MP-BGP, and the architecture permitted adding dedicated IPv6 BGP interfaces and peers to Cloud Router for your dual-stack GKE subnets.
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