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 has provisioned two Dedicated Interconnect connections (int-1 and int-2) in the us-east4 region to connect an on-premises data center (ASN 65010) to a VPC network (prod-vpc). You must implement the Cloud Router, VLAN attachments, and BGP sessions to meet these requirements:
1010 and 1020 with specific non-link-local IPv4 and IPv6 addresses on both peering ends.How should you configure these resources?
us-east4 with an unused private ASN (64513) and CUSTOM advertisement mode for the required VPC prefixes. Create two dual-stack (IPV4_IPV6) VLAN attachments specifying --vlan values 1010 and 1020 with link-local candidate subnets for both the IPv4 and IPv6 BGP ranges. Add one IPv4 interface per attachment on the Cloud Router, and configure one BGP peer per interface with --peer-asn=65010, --enable-ipv6, --advertised-route-priority values of 100 and 200, and matching --md5-authentication-key values.Using candidate subnets instructs Cloud Router to automatically select IPv4 link-local (169.254.0.0/16) peering addresses from a supplied CIDR range, while setting distinct --advertised-route-priority values configures Multi-Exit Discriminator (MED) route metrics to prefer one path over another.
169.254.x.x addresses rather than the required non-link-local custom IPv4 addresses.--advertised-route-priority to 100 on one BGP peer and 200 on the other assigns unequal MED values to the advertised VPC routes. On-premises routers will prefer the lower MED (100) path, resulting in active/passive forwarding instead of active/active ECMP load balancing.tag8021q) cannot be modified after a VLAN attachment is created; changing them requires recreating the attachment.This approach would be appropriate if the organization wanted automatic link-local IPv4 addressing, allowed Google Cloud to auto-allocate IPv6 addresses rather than supplying candidate subnets, and intended an active/passive failover topology instead of ECMP.
us-east4 with an unused private ASN (64513) and CUSTOM advertisement mode for the required VPC prefixes. Create two dual-stack (IPV4_IPV6) VLAN attachments specifying --vlan values 1010 and 1020 with custom IPv4 and IPv6 CIDR addresses for both ends. Add both an IPv4 interface and an IPv6 interface per attachment on the Cloud Router, and configure BGP peers on both interfaces with --peer-asn=65010, --enable-ipv6 on the IPv4 peer, identical --advertised-route-priority values, and matching --md5-authentication-key values.Adding both an IPv4 interface and an IPv6 interface on a Cloud Router for a single dual-stack (IPV4_IPV6) VLAN attachment configures two separate, parallel BGP sessions over that attachment—one dedicated to exchanging IPv4 prefixes and one dedicated to exchanging IPv6 prefixes.
--enable-ipv6 on an IPv4 peer while an IPv6 interface and BGP session already exist for that attachment results in a configuration conflict.IPV4_IPV6) VLAN attachment supports either two parallel single-protocol BGP sessions (one IPv4 and one IPv6) or one MP-BGP session (either IPv4 with --enable-ipv6 or IPv6 with --enable-ipv4).ipv6NexthopAddress and peerIpv6NexthopAddress values without needing a separate Cloud Router IPv6 interface.This configuration would be valid if the organization wanted to run separate IPv4 and IPv6 BGP sessions in parallel over each dual-stack VLAN attachment without enabling MP-BGP flags (--enable-ipv6 or --enable-ipv4), and if the requirement did not specify a single MP-BGP session per attachment.
us-east4 with an unused private ASN (64513) and CUSTOM advertisement mode for the required VPC prefixes. Create two dual-stack (IPV4_IPV6) VLAN attachments specifying --vlan values 1010 and 1020 with custom IPv4 and IPv6 CIDR addresses for both ends. Add one IPv4 interface per attachment on the Cloud Router, and configure one BGP peer per interface with --peer-asn=65010, --enable-ipv6, identical --advertised-route-priority values, and matching --md5-authentication-key values.This implementation establishes a dual-stack, active/active Dedicated Interconnect hybrid architecture using a regional Cloud Router, two custom-addressed VLAN attachments, and Multiprotocol BGP (MP-BGP) sessions secured with MD5 authentication.
IPV4_IPV6 stack type and adding only a single IPv4 interface on the Cloud Router allows each BGP peer to use --enable-ipv6 to exchange both IPv4 and IPv6 prefixes over one TCP/BGP session.--vlan to 1010 and 1020 aligns 802.1Q tagging with the on-premises switch trunk, while custom IP address ranges assign the required non-link-local IPv4 and IPv6 addresses to both the Cloud Router and customer router ends.--md5-authentication-key enables BGP TCP MD5 signature validation with the on-premises router (--peer-asn=65010), and using CUSTOM advertisement mode ensures Cloud Router advertises only the designated VPC subnets.--advertised-route-priority (base MED) values on both BGP peers ensures both paths appear equally preferred, enabling equal-cost multipath (ECMP) traffic distribution across int-1 and int-2.169.254.0.0/16 link-local space.CUSTOM advertisement mode prevents unintended VPC subnet exposure to the on-premises network.Unlike parallel single-protocol BGP sessions, which violate the single-session MP-BGP requirement, or mismatched MEDs and candidate subnets, which break ECMP and fail IPv6 custom addressing rules, this design satisfies every technical and security constraint cleanly within Cloud Router and Dedicated Interconnect limits.
us-east4 with ASN 65010 and DEFAULT advertisement mode, using custom learned routes on each BGP session to restrict VPC route advertisements. Create two dual-stack (IPV4_IPV6) VLAN attachments specifying --vlan values 1010 and 1020 with custom IPv4 and IPv6 CIDR addresses for both ends. Add one IPv4 interface per attachment on the Cloud Router, and configure one BGP peer per interface with --peer-asn=65010, --enable-ipv6, identical --advertised-route-priority values, and matching --md5-authentication-key values.Assigning the same ASN (65010) on both the Cloud Router and the on-premises router attempts to match autonomous system numbers across peering endpoints, while custom learned routes manually inject destination prefixes into Cloud Router as if they were received from the BGP peer.
64512–65534 or 4200000000–4294967294) that is not already in use in the on-premises network. Configuring Cloud Router with ASN 65010 while --peer-asn is also 65010 causes an ASN collision and prevents the eBGP session from establishing.DEFAULT advertisement mode advertises all subnets visible to the Cloud Router in the region (or VPC in global routing mode). Custom learned routes affect routes received into the VPC (traffic from Google Cloud to on-premises) and do not filter or restrict the VPC prefixes Cloud Router advertises outbound to the on-premises router.CUSTOM advertisement mode) at either the Cloud Router level or the individual BGP session level.This configuration would work only if the Cloud Router used a distinct private ASN (such as 64513) and used custom advertised routes (CUSTOM advertisement mode) rather than DEFAULT mode with custom learned routes.
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