Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Network Engineer Topic 5 Question 81 Discussion

Actual exam question for Google's Professional Cloud Network Engineer exam
Question #: 81
Topic #: 5
[All Professional Cloud Network Engineer Questions]

You are a network administrator at your company planning a migration to Google Cloud and you need to finish the migration as quickly as possible, To ease the transition, you decided to use the same architecture as your on-premises network' a hub-and-spoke model. Your on-premises architecture consists of over 50 spokes. Each spoke does not have connectivity to the other spokes, and all traffic IS sent through the hub for security reasons. You need to ensure that the Google Cloud architecture matches your on-premises architecture. You want to implement a solution that minimizes management overhead and cost, and uses default networking quotas and limits. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

The correct answer is D because it meets the following requirements:

It matches the hub-and-spoke model of the on-premises network, where each spoke is a separate VPC network that is connected to a central hub VPC network.

It minimizes management overhead and cost, because VPC Network Peering is a simple and low-cost way to connect VPC networks without using any external IP addresses or VPN gateways1.

It uses default networking quotas and limits, because VPC Network Peering does not consume any quota or limit for VPN tunnels, external IP addresses, or forwarding rules2.

It prevents connectivity between the spokes, because VPC Network Peering is non-transitive by default, meaning that a spoke can only communicate with the hub, not with other spokes1.To enforce this restriction, a third-party network appliance can be used as a default gateway in each spoke VPC network, which can filter out any traffic destined for other spokes3.

Option A is incorrect because it does not minimize cost, as Cloud VPN charges for egress traffic and requires external IP addresses for the VPN gateways4.Option B is incorrect because it does not prevent connectivity between the spokes, as VPC Network Peering allows direct communication between peered VPC networks by default1. Option C is incorrect because it does not minimize cost or use default quotas and limits, for the same reasons as option A.


VPC Network Peering overview | VPC

Quotas and limits | VPC

Hub-and-spoke network architecture | Cloud Architecture Center

Cloud VPN overview | Google Cloud

Contribute your Thoughts:

Pansy
6 months ago
Could be, but isn’t Cloud VPN more secure since all the spoke traffic goes through the hub?
upvoted 0 times
...
Jackie
6 months ago
Maybe, but what about Option B, using VPC Network Peering? It might be simpler.
upvoted 0 times
...
Barney
6 months ago
But wouldn't that be a bit costly and hard to manage with all those connections?
upvoted 0 times
...
Loreen
6 months ago
I think Option A makes sense. Cloud VPN should connect everything quickly.
upvoted 0 times
...
Jackie
7 months ago
Yeah, seems a bit overwhelming. They're asking for the same hub-and-spoke model.
upvoted 0 times
...
Pansy
7 months ago
Have you seen this question about migrating to Google Cloud with over 50 spokes?
upvoted 0 times
...

Save Cancel