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 redundant Google Cloud Cross-Cloud Interconnect topology to connect a VPC network in us-west1 to Oracle Cloud Infrastructure (OCI). You have provisioned two active Cross-Cloud Interconnect connections (cci-link-1 and cci-link-2) in the same region.
Your network architecture requires the following configuration:
Which configuration meets all of these requirements?
us-west1 with ASN 16550 and retain the default VPC network MTU of 1460. Create two dedicated VLAN attachments across cci-link-1 and cci-link-2 with --mtu=1500. Add interfaces for each attachment on the Cloud Router, and configure BGP peers with --peer-asn=64512 and an identical alphanumeric MD5 authentication key matching the OCI configuration.This configuration creates redundant dedicated VLAN attachments with --mtu=1500 and alphanumeric MD5 authentication, while using Google's public ASN 16550 on the Cloud Router, retaining the default VPC MTU of 1460, and peering with ASN 64512.
1460 vs. 1500): Retaining the default VPC network MTU of 1460 prevents Compute Engine VMs in that VPC from sending 1500-byte packets over the VLAN attachments, violating the end-to-end 1500-byte requirement.16550 is Google's public ASN (typically mandatory for Partner Interconnect, not Dedicated Cross-Cloud Interconnect).64512): ASN 64512 is the default peer ASN for AWS Direct Connect, whereas OCI requires peer ASN 31898.1500- or 8896-byte attachment MTU, the associated VPC network and remote compute instances must all be configured with the exact same MTU value.16550 on the Cloud Router.Using peer ASN 64512 would be valid when establishing Cross-Cloud Interconnect BGP peering with AWS, provided the VPC MTU matched the attachment MTU and a private Cloud Router ASN was selected if required.
Always finalize both the VPC network MTU and the Cloud Router ASN before deploying production VLAN attachments, as changing a Cloud Router's ASN requires rebuilding the router and changing a VPC MTU can briefly affect active VM traffic.
us-west1 with ASN 65530 and set the VPC network MTU to 1500. Create two dedicated VLAN attachments—one on cci-link-1 and one on cci-link-2—each configured with --mtu=1500 and attached to the Cloud Router. Add a Cloud Router interface for each attachment, and configure BGP peers on both interfaces with --peer-asn=31898 and an identical alphanumeric MD5 authentication key matching the OCI configuration, while ensuring OCI instances also use a 1500-byte MTU.This configuration establishes a high-availability Cross-Cloud Interconnect architecture between a Google Cloud Virtual Private Cloud (VPC) network and Oracle Cloud Infrastructure (OCI) by provisioning redundant dedicated VLAN attachments, matching 1500-byte MTU settings end-to-end, and securing dynamic BGP peering on a single Cloud Router.
1440-byte MTU, explicitly setting --mtu=1500 on both attachments—alongside setting the VPC network MTU and OCI instance MTU to 1500—ensures 1500-byte packets traverse the entire multicloud path without fragmentation.cci-link-1 and a second on cci-link-2 within us-west1 distributes traffic across both physical Cross-Cloud Interconnect connections and satisfies SLA redundancy requirements.65530 to the Cloud Router satisfies the requirement for a non-default private ASN within OCI's permitted 64512–65533 range (avoiding the restricted 65534 ASN), while --peer-asn=31898 correctly targets OCI's public BGP ASN.Compared to configurations that rely on default attachment MTUs, restricted ASNs, unsupported BFD settings, or incompatible MD5 characters, this approach aligns every Layer 2 and Layer 3 parameter with both Google Cloud and OCI specifications.
us-west1 with ASN 65530 and set the VPC network MTU to 1500. Create two dedicated VLAN attachments across cci-link-1 and cci-link-2 using the default attachment MTU setting. Add interfaces for each attachment on the Cloud Router, and configure BGP peers with --peer-asn=12076, an alphanumeric MD5 authentication key, and Bidirectional Forwarding Detection (BFD) enabled.This configuration attempts to establish redundant Cross-Cloud Interconnect BGP sessions using Bidirectional Forwarding Detection (BFD) for rapid link-failure detection while relying on the default VLAN attachment MTU.
--mtu flag leaves both VLAN attachments at the default value of 1440 bytes. Even when the VPC network is set to 1500, traffic exceeding 1440 bytes cannot cross the VLAN attachments unfragmented.12076): ASN 12076 is the BGP Autonomous System Number used by Microsoft Azure ExpressRoute, not OCI (which uses 31898). BGP peering with OCI will fail to establish due to the ASN mismatch.1440, 1460, 1500, and 8896, but the effective path MTU is always constrained by the lowest MTU along the path (VPC, VLAN attachment, and remote VM).31898 for OCI, 12076 for Azure, and 45104 for Alibaba Cloud.This peer ASN (12076) would be appropriate if you were connecting to Microsoft Azure (provided you also adjusted the attachment subnet mask to /30, removed BFD if unsupported by the peer topology, and explicitly set --mtu=1500 on both attachments).
A common misconception is that changing the VPC network MTU automatically updates attached VLAN attachments; in reality, each VLAN attachment maintains its own independent MTU setting that must be explicitly configured.
us-west1 with ASN 65534 and set the VPC network MTU to 1500. Create two dedicated VLAN attachments across cci-link-1 and cci-link-2 with --mtu=1500. Add interfaces for each attachment on the Cloud Router, and configure BGP peers with --peer-asn=31898 and a complex MD5 authentication key containing alphanumeric and special characters matching the OCI configuration.This configuration attempts to provision redundant dedicated VLAN attachments and Border Gateway Protocol (BGP) sessions over Cross-Cloud Interconnect to Oracle Cloud Infrastructure (OCI) while applying a 1500-byte Maximum Transmission Unit (MTU) and MD5 authentication.
65534): When peering with OCI over Cross-Cloud Interconnect, Google Cloud requires the Cloud Router ASN to be either 16550 or a private ASN in the 64512 to 65533 range. ASN 65534 is explicitly excluded because OCI reserves it internally.--mtu=1500 on both the VPC network and the VLAN attachments correctly prepares the Google Cloud side, the BGP session will fail to establish due to the ASN and MD5 key violations.This option would be correct if the Cloud Router used a valid private ASN between 64512 and 65533 (such as 65530) and the MD5 authentication key contained strictly alphanumeric characters.
When connecting to different external providers, always verify provider-specific ASN exclusions. For example, OCI excludes 65534, whereas Microsoft Azure reserves 65515 through 65520.
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