VPC, hybrid and producer VPC spokes, star and mesh topologies, Private NAT and Private Service Connect connection propagation, spoke filters, and monitoring and troubleshooting a hub.
Try each one before opening the answer. Every option is explained, with the Google Cloud documentation page that proves it.
Question 1 · choose 1
Two VPC networks, finance and partners, may exchange traffic only through a third-party firewall appliance, and the appliance must learn and advertise routes with BGP so that new subnets need no manual route changes. The network team wants to manage this connectivity with Network Connectivity Center. Which topology meets the requirement?
AA Router appliance spoke on each of the appliance's two interfaces, each peering by BGP with its network's Cloud Router
BBoth networks as VPC spokes of one hub with the mesh topology, and the appliance VM placed in the finance network as a gateway
CBoth networks as VPC spokes of one hub, with export filters that exclude every subnet range of each network
DVPC Network Peering between the networks, with static routes for each peer subnet whose next hop is the appliance
Show the answer and why
AA Router appliance spoke on each of the appliance's two interfaces, each peering by BGP with its network's Cloud Router
Correct
In this topology each Cloud Router learns the other network's subnets only from the appliance, so traffic between the networks crosses it.
BBoth networks as VPC spokes of one hub with the mesh topology, and the appliance VM placed in the finance network as a gateway
Incorrect
VPC spokes import each other's subnet routes directly, so traffic between them would bypass the appliance.
CBoth networks as VPC spokes of one hub, with export filters that exclude every subnet range of each network
Incorrect
Excluding all subnets removes the connectivity altogether; export filters don't steer traffic through an appliance.
DVPC Network Peering between the networks, with static routes for each peer subnet whose next hop is the appliance
Incorrect
A local static route can't have a destination that matches or fits within a peering subnet route, so the peered subnets can't be steered to the appliance.
NCC's VPC-to-VPC topology with a third-party appliance uses the Router appliance feature: the appliance VM has an interface in each VPC network, each interface becomes a Router appliance spoke, and the appliance exchanges routes by BGP with a Cloud Router in each network. The networks see each other only through routes learned from the appliance.
A VPC network is already a VPC spoke of the Network Connectivity Center hub hub-prod. A team now wants to add the same network as a VPC spoke of a second hub, hub-shared. What happens?
AIt joins both hubs, and routes from both hubs are merged in the network
BIt joins hub-shared, as long as both hubs use the same preset topology
CIt joins hub-shared only as a hybrid spoke
DIt can't join: a VPC spoke can be connected to only one hub at a time
Show the answer and why
AIt joins both hubs, and routes from both hubs are merged in the network
Incorrect
A VPC spoke can be connected to only one hub at a time.
BIt joins hub-shared, as long as both hubs use the same preset topology
Incorrect
The topology isn't the condition; one hub at a time is the rule.
CIt joins hub-shared only as a hybrid spoke
Incorrect
Hybrid spokes are VLAN attachments, HA VPN tunnels or Router appliance VMs, not VPC networks.
DIt can't join: a VPC spoke can be connected to only one hub at a time
Correct
The VPC spokes overview states that a VPC spoke can be connected to one hub at a time.
VPC spokes can be in the hub's project or in other projects and organizations, but each VPC network can be a spoke of only one hub at a time. Hybrid spokes are built from VLAN attachments, HA VPN tunnels or Router appliance VMs.
A spoke administrator in project app-a creates a VPC spoke for her network on a Network Connectivity Center hub that lives in the networking team's project. The spoke doesn't become active. What is the expected next step?
AThe spoke administrator must re-create the spoke in the hub's project
BA hub administrator must review and accept the spoke proposal
CThe networking team must peer its network with app-a's network first
DThe spoke activates by itself after the hub's route table refreshes
Show the answer and why
AThe spoke administrator must re-create the spoke in the hub's project
Incorrect
VPC spokes can be in a different project, or even organization, from the hub.
BA hub administrator must review and accept the spoke proposal
Correct
A VPC spoke in another project starts as a proposal that a hub administrator must approve before it becomes active.
CThe networking team must peer its network with app-a's network first
Incorrect
VPC spokes replace pairwise peering; no peering is needed for the spoke.
DThe spoke activates by itself after the hub's route table refreshes
Incorrect
Only spokes created in the hub's own project are added immediately.
When a spoke administrator creates a VPC spoke in the hub's project, NCC adds it immediately. In a different project, NCC creates a spoke proposal, which a hub administrator must review and approve before the spoke becomes active.
A VPC spoke on a Network Connectivity Center hub has a subnet that uses a privately used public IPv4 range (PUPI), and no export filters were set on the spoke. Other spokes reach the spoke's RFC 1918 subnets but not the PUPI subnet. What explains this?
ANCC never exchanges subnet routes that use privately used public IPv4 address ranges
BThe other spokes need import filters that accept the PUPI range
CThe default include export ranges of a VPC spoke cover only private IPv4 ranges
DPUPI subnets are exported only when the hub uses the star topology
Show the answer and why
ANCC never exchanges subnet routes that use privately used public IPv4 address ranges
Incorrect
VPC spokes support privately used public IPv4 addresses; they need to be included in the export filter.
BThe other spokes need import filters that accept the PUPI range
Incorrect
VPC spokes support only export filters; the range is held back on the exporting side.
CThe default include export ranges of a VPC spoke cover only private IPv4 ranges
Correct
Without include export ranges, a VPC spoke exports only private IPv4 subnet ranges, so a PUPI range must be added to its include export ranges.
DPUPI subnets are exported only when the hub uses the star topology
Incorrect
The preset topology doesn't decide which ranges a spoke exports.
If a VPC spoke has no include export ranges, NCC treats it as if ALL_PRIVATE_IPV4_RANGES had been specified, which covers only private IPv4 subnet ranges. Adding the PUPI CIDR, or ALL_IPV4_RANGES, to the spoke's include export ranges exports the PUPI subnet to the hub.