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 a Network Connectivity Center (NCC) hub in Google Cloud to unify connectivity across VPC spokes, an on-premises data center, and workloads in AWS and Microsoft Azure. You have created an NCC Gateway spoke in us-east4 and need to integrate three connections:
us-east4.us-east4.us-east4.Which configuration should you implement to establish compliant BGP sessions and interconnect topologies across all three environments?
This architecture establishes compliant, redundant hybrid and multi-cloud connectivity by combining Partner Interconnect for on-premises integration with Network Connectivity Center (NCC) and dedicated Cross-Cloud Interconnect pairs for AWS and Microsoft Azure, using valid Cloud Router regions, ASNs, and BGP security settings.
us-east4 (matching the NCC Gateway's region) with Google ASN 16550 fulfills the mandatory ASN requirement for Partner Interconnect and ensures the VLAN attachments' BGP sessions are integrated into the NCC Gateway spoke.64512 (the default AWS ASN within 64512–65534 or 4200000000–4294967294) and MD5 authentication enabled aligns with Google Cloud and AWS peering requirements.65515–65520 ASN range on the Cloud Router, and setting the peer ASN to 12076 ensures conflict-free BGP peering with Azure ExpressRoute.Unlike options that share physical Cross-Cloud Interconnect ports across providers, place Cloud Routers in mismatched regions, or use conflicting ASNs (64513 on Partner Interconnect, 65518 on Azure, or 31898 as Azure's peer ASN), this design adheres strictly to every Google Cloud, AWS, and Azure protocol constraint.
This configuration attempts to consolidate multi-cloud connectivity by sharing a single redundant pair of Cross-Cloud Interconnect connections across both AWS and Microsoft Azure using multiple 802.1Q VLAN attachments, while applying valid ASNs and MD5 authentication.
16550 for Partner Interconnect, 12076 for Azure peer ASN, and 64512 with MD5 for AWS) are all valid, making the shared physical topology the sole flaw.This option would be correct if two separate redundant pairs of Cross-Cloud Interconnect connections were provisioned—one pair dedicated to AWS and a second pair dedicated to Azure.
Because Dedicated Interconnect and Cross-Cloud Interconnect both support multiple 802.1Q VLAN attachments per link, administrators often assume a single Cross-Cloud Interconnect pair can multiplex traffic to multiple public clouds. However, Cross-Cloud Interconnect ports are physically patched directly into the designated remote cloud provider's edge routers.
This configuration correctly provisions separate redundant Cross-Cloud Interconnect pairs and uses valid Partner Interconnect and AWS ASN settings, but it violates the regional affinity requirement for NCC Gateway and assigns the wrong peer ASN for Microsoft Azure.
us-central1 prevents it from being associated with an NCC Gateway located in us-east4, regardless of whether global dynamic routing is enabled on a VPC.31898 for Azure ExpressRoute peering fails because 31898 is Oracle Cloud Infrastructure's (OCI) FastConnect ASN, whereas Microsoft Azure strictly requires a peer ASN of 12076.us-east4).12076 for Azure, 31898 for OCI, 45104 for Alibaba Cloud, and private ASNs (64512–65534 or 32-bit private ASNs) for AWS.64514 on the Azure Cross-Cloud Interconnect Cloud Router does avoid Azure's reserved 65515–65520 block, but the mismatched peer ASN still prevents BGP establishment.This option would be correct if the Partner Interconnect Cloud Router were created in us-east4 (matching the NCC Gateway region) and the Azure Cross-Cloud Interconnect peer ASN were set to 12076 instead of 31898.
While global dynamic routing allows a VPC's Cloud Router in one region to advertise routes from subnets in other regions, NCC Gateway resources strictly enforce same-region association between the gateway and its Cloud Router.
This configuration correctly separates the physical Cross-Cloud Interconnect port pairs for AWS and Azure and uses valid AWS BGP peering settings, but it assigns invalid Border Gateway Protocol (BGP) Autonomous System Numbers (ASNs) to both the Partner Interconnect Cloud Router and the Azure Cross-Cloud Interconnect Cloud Router.
64513. Google Cloud strictly mandates using the Google-owned public ASN 16550 for Partner Interconnect VLAN attachments.65518 falls within the general 16-bit private ASN range (64512–65534), Microsoft Azure reserves the 65515–65520 ASN block for internal ExpressRoute infrastructure. Assigning 65518 to the Cloud Router creates an ASN conflict that prevents BGP peering establishment with Azure.16550 ASN.64512–65514 and 65521–65534 (or public ASN 16550).64512 with MD5 authentication enabled accurately satisfies AWS Direct Connect peering requirements.This option would be correct if the Partner Interconnect Cloud Router ASN were changed from 64513 to 16550 and the Azure Cross-Cloud Interconnect Cloud Router ASN were changed from 65518 to a non-reserved value such as 16550, 64514, or 65521.
A common misconception is that any RFC 6996 private ASN works across all Cloud Interconnect products. In practice, Partner Interconnect mandates 16550, while Cross-Cloud Interconnect requires respecting each remote cloud provider's reserved ASN blocks.
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