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 provisioning a Layer 2 Partner Interconnect connection in us-central1 using a Cloud Router with ASN 16550. After your service provider finishes configuring the initial VLAN attachment, its state changes to PENDING_CUSTOMER with the following details:
vlanTag8021q): 10002050169.254.67.201/29 (Cloud Router) and 169.254.67.202/29 (Peer)Before passing traffic, your security team mandates switching BGP peering to custom IP addresses (192.0.2.0/29) and enabling BGP MD5 authentication.
Which sequence of actions should you take to complete the configuration?
In Google Cloud Partner Interconnect, VLAN IDs and BGP IP addresses (both the Cloud Router IP and the customer peer IP) are immutable once a VLAN attachment is created. Replacing automatically allocated link-local addresses (169.254.0.0/16) with custom IP ranges (192.0.2.0/29) requires deleting the existing attachment and creating a replacement attachment with the custom IP addresses defined at creation time.
DEFUNCT state, stops billing for the unused resource, and allows safe cleanup of its auto-generated Cloud Router interface and BGP peer.partnerMetadata confirms the expected provider before activating the attachment.2050), establishes an authenticated BGP session and functional data plane.--admin-enabled / --no-admin-enabled) can be updated in place, BGP IP addresses and VLAN IDs cannot.vlanTag8021q value (1000) applies strictly to Google Cloud's side of the interconnect, whereas the on-premises router tags frames using the VLAN ID (2050) assigned by the service provider.Unlike modifying auto-generated Cloud Router interfaces directly or attempting in-place attachment updates, recreating the attachment follows the supported Partner Interconnect lifecycle, avoids breaking Google-managed BGP interfaces, and ensures end-to-end Layer 2 and Layer 3 alignment.
This approach correctly identifies that the VLAN attachment must be deleted and recreated, but it relies on automatic IP allocation with pre-activation (--admin-enabled), asks the service provider to inject custom IP ranges during provisioning, and uses Google Cloud's vlanTag8021q value on the on-premises router.
partnerMetadata verification check that ensures the expected provider paired with the key.vlanTag8021q (1000) instead of the service provider's VLAN ID (2050) prevents Layer 2 connectivity between the on-premises router and the provider network.PENDING_PARTNER state before provider pairing).Leaving IP allocation to the service provider during provisioning and enabling pre-activation would be appropriate for a Layer 3 Partner Interconnect connection, though the on-premises router would still follow the service provider's Layer 3 handoff specifications rather than Google's vlanTag8021q.
This approach assumes that BGP IP addresses can be modified in place on an existing Partner Interconnect VLAN attachment using gcloud compute interconnects attachments partner update and delegates BGP MD5 authentication and peer ASN configuration to the service provider.
partner update command only supports modifying mutable attributes such as description, mtu, stack-type, and administrative enablement (--admin-enabled or --no-admin-enabled). It cannot alter the Cloud Router IP or Peer IP addresses after attachment creation.Established state.No answer could make partner update change existing BGP IP addresses; however, contacting the service provider for MD5 authentication and automatic peer ASN assignment would be appropriate if the connection were a Layer 3 Partner Interconnect and only mutable properties needed adjustment.
This option attempts to bypass recreating the VLAN attachment by manually editing the Google-defined interface and BGP peering session on the Cloud Router, while using the vlanTag8021q field (1000) from the attachment description to tag frames on the on-premises router.
MANAGED_BY_ATTACHMENT) on the Cloud Router. Manually modifying the IP addresses on these Google-defined configurations shuts down the BGP session.vlanTag8021q attribute (1000) returned by Google Cloud identifies the VLAN on the Google Cloud side of the connection. Using it on the on-premises router instead of the service provider's assigned VLAN (2050) causes Layer 2 frame drops.interconnectAttachment must stay synchronized with the attachment's cloudRouterIpAddress and customerRouterIpAddress.2050) and Google's side (1000), so the two VLAN IDs do not need to match.It would never be valid to manually overwrite IP addresses on a Google-managed Cloud Router interface for an existing attachment; configuring the on-premises router with vlanTag8021q directly only applies to Dedicated Interconnect, where there is no intermediary service provider.
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