How to Advertise Spoke Subnets via Hub Cloud Router?

Your organization has a hub and spoke architecture with VPC Network Peering, and hybrid connectivity is centralized at the hub. The Cloud Router in the hub VPC is advertising subnet routes, but the on-premises router does not appear to be receiving any subnet routes from the VPC spokes. You need to resolve this issue. What should you do?

  1. Create custom routes at the Cloud Router in the spokes to advertise the subnets of the VPC spokes.
  2. Create custom routes at the Cloud Router in the hub to advertise the subnets of the VPC spokes. Source Reference Answer
  3. Create a BGP route policy at the Cloud Router, and ensure the subnets of the VPC spokes are being announced towards the on-premises environment.
  4. Create custom learned routes at the Cloud Router in the hub to advertise the subnets of the VPC spokes.

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

Examined topic: Cloud Router route advertisement behavior in hub-and-spoke architectures; common trap: assuming automatic propagation or using BGP policies instead of static custom routes.

This question tests proper Cloud Router configuration for advertising VPC subnet routes across a hub-and-spoke topology. The community consensus confirms that manually creating custom routes at the hub Cloud Router is required to propagate spoke subnets to on-premises networks.

Option C is frequently chosen because candidates assume dynamic BGP route policies can override default routing behavior, but Cloud Routers do not automatically redistribute peer VPC routes into BGP without explicit custom route definitions.

Community Discussion (4 comments)

7103685 👍 1 Selected: B
The answered checked is wrong, C
7103685 👍 1 Selected: B
Correct answer is B
Gwendal 👍 1 Selected: B
https://cloud.google.com/network-connectivity/docs/router/how-to/advertising-custom-ip
1f01b87 👍 1 Selected: B
Correct answer is B

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

In a hub-and-spoke VPC peering setup, Cloud Routers do not automatically advertise subnet routes from peer VPCs over BGP. To enable hybrid connectivity, you must explicitly define custom routes at the hub Cloud Router that match the spoke subnet ranges and set their next-hop appropriately. Once these custom routes are created, the hub Cloud Router will advertise them to your on-premises routers via BGP, resolving the missing route issue.

Why the Other Options Are Wrong

Option A fails because custom routes defined in spoke Cloud Routers only affect traffic originating from those spokes and cannot be advertised through the hub to external peers. Option C is incorrect because Cloud Routers lack traditional BGP route-map capabilities for redistributing peer routes; they rely on static custom route configurations instead. Option D is invalid since "custom learned routes" is not a supported feature in Google Cloud networking, making it a distractor.

Community Comment Notes

Several users initially debated between options B and C, highlighting the confusion around BGP policy versus static route advertisement. One comment correctly points out that the official documentation validates creating custom routes at the hub to handle this scenario. Another user notes that while BGP policies sound plausible, GCP's Cloud Router architecture strictly requires manual custom route entries for inter-VPC subnet propagation in hybrid setups.

Official Reference

https://cloud.google.com/network-connectivity/docs/router/how-to/advertising-custom-ip

Exam Strategy

Always verify whether a service automatically propagates routes before assuming dynamic protocols like BGP will handle redistribution. For GCP Cloud Router questions involving hub-and-spoke topologies, remember that explicit custom route creation at the hub is almost always required for cross-VPC advertisement.

Related Analysis

Your company has a single on-premises data center that needs

S-Grade

Your company deployed a hub and spoke architecture in Google

A-Grade

You are designing a packet mirroring policy as part of your

S-Grade

Practice All PCNE Questions

Access 80 questions with complete answers and detailed explanations.

View Full PCNE Practice Test →

← Back to PCNE Study Guide