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.
An organization uses a Network Connectivity Center (NCC) hub to connect VPC spokes, a services spoke with Private Service Connect (PSC) endpoints, and a routing VPC with Cloud Interconnect VLAN attachments (hybrid spokes). The routing VPC's Cloud Router uses router-level CUSTOM mode (ALL_SUBNETS plus Private NAT and PSC ranges).
An engineer runs gcloud compute routers update-bgp-peer on one BGP session with --advertisement-mode=CUSTOM and --set-advertisement-ranges=10.200.5.10/32 for a new PSC endpoint, causing these results on that session:
10.200.5.10/32.What caused this connectivity failure, and how should you resolve it?
--set-advertisement-groups=ALL_SUBNETS and include the existing Private NAT and PSC ranges alongside 10.200.5.10/32 in --set-advertisement-ranges.In Google Cloud, Cloud Router supports configuring custom advertised routes either at the router level (applying by default to all Border Gateway Protocol sessions on that Cloud Router) or at the individual BGP session level. When any custom advertised route is configured directly on a specific BGP session, all router-level advertised routes—including ALL_SUBNETS and any router-level custom IP ranges—are completely ignored and overridden for that session.
Running gcloud compute routers update-bgp-peer with --advertisement-mode=CUSTOM and only --set-advertisement-ranges=10.200.5.10/32 replaced the entire advertisement list for that VLAN attachment session with just the single /32 host route. By updating that BGP peer to include --set-advertisement-groups=ALL_SUBNETS and specifying all required Private NAT ranges, existing PSC endpoint prefixes, and 10.200.5.10/32 in --set-advertisement-ranges, the session resumes advertising both local subnets and every necessary custom prefix.
--add-advertisement-ranges on gcloud compute routers update avoids accidentally dropping existing prefixes.Restoring ALL_SUBNETS and consolidating all Private NAT and PSC custom ranges on the BGP peer directly fixes the route withdrawal caused by the session-level override without disrupting the rest of the NCC hub topology.
regional dynamic routing mode, which prevents custom route advertisements from propagating across BGP sessions; change the routing VPC's dynamic routing mode to global and update the NCC hub's hybrid spoke import filters.The dynamic routing mode (regional or global) of a Virtual Private Cloud (VPC) network determines the geographic scope across which Cloud Router advertises local subnet routes and installs learned dynamic routes from BGP peers. In regional mode, Cloud Router advertises only subnets in its own region and limits learned routes to that region; in global mode, it advertises and propagates routes across all regions in the VPC.
Changing the routing VPC to global dynamic routing mode will not restore the missing routing VPC subnets, Private NAT ranges, or PSC endpoint prefixes on the affected BGP session. The dynamic routing mode of a routing VPC network does not control or fix Cloud Router custom route advertisements. The routes disappeared because configuring a custom advertisement on the individual BGP peer caused that session to ignore and override all router-level advertisements.
regional or global mode.global dynamic routing enabled, running update-bgp-peer without --set-advertisement-groups=ALL_SUBNETS stops subnet advertisements on that session.On-premises hosts connected to a VLAN attachment in us-central1 were unable to reach VPC subnets or transit dynamic routes located in us-east1 while router-level advertisements were intact.
CUSTOM mode on the BGP session conflicts with NCC route propagation; switch the Cloud Router and BGP session to DEFAULT advertisement mode so Cloud Router automatically advertises all local subnets, Private NAT ranges, and routes from other VPC spokes.In DEFAULT advertisement mode, a Cloud Router automatically advertises only the subnet IP ranges that belong directly to its own VPC network (scoped by the VPC's regional or global dynamic routing mode). It is designed for straightforward hybrid connectivity where no external, static, or non-subnet prefixes need to be announced over BGP.
Switching the Cloud Router and BGP session to DEFAULT advertisement mode would permanently break reachability to 10.200.5.10/32, existing Private NAT ranges, and custom PSC endpoint prefixes that are not standard local VPC subnet routes. Additionally, DEFAULT mode does not advertise routes learned dynamically from other VPCs via VPC Network Peering or VPC spokes in NCC unless explicitly handled via NCC hybrid spoke propagation or custom ranges.
DEFAULT mode strictly limits Cloud Router announcements to subnets inside the Cloud Router's own VPC network./32 PSC VIPs are excluded in DEFAULT mode.CUSTOM settings, switching the Cloud Router itself to DEFAULT removes all custom advertisements across every BGP session.The organization only needed to advertise standard subnet ranges inside the routing VPC itself and had no Private NAT, PSC, or non-subnet IP ranges to announce to on-premises peers.
In VPC Network Peering architectures where Network Connectivity Center (NCC) is not used to link the services-access VPC, HA VPN tunnels between a transit VPC and a services-access VPC provide BGP-based transitive routing so external hybrid networks can reach Private Service Connect (PSC) endpoints.
Adding HA VPN tunnels between the services VPC spoke and the routing VPC is both unnecessary in an NCC architecture and architecturally invalid if the services VPC remains an NCC spoke. Furthermore, adding HA VPN tunnels does not resolve the BGP session override on the Cloud Interconnect VLAN attachment where update-bgp-peer dropped ALL_SUBNETS and the existing custom ranges.
The environment used VPC Network Peering between application VPCs and a transit VPC instead of NCC VPC spokes, and needed transitive routing to a separate services-access VPC hosting PSC endpoints.
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