Topic 1 Question 162
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?
Connect all the spokes to the hub with Cloud VPN.
Connect all the spokes to the hub with VPC Network Peering.
Connect all the spokes to the hub with Cloud VPN. Use a third-party network appliance as a default gateway to prevent connectivity between the spokes.
Connect all the spokes to the hub with VPC Network Peering. Use a third-party network appliance as a default gateway to prevent connectivity between the spokes.
ユーザの投票
コメント(8)
- 正解だと思う選択肢: C
Correct answer is C. Forget the points about non-transitive routing that folks are making. The key point is in the question that they want to stay within the GCP quotas and limits. VPC peering max is 25. The customer has 50 spokes in their on-premises hub-n-spoke design and the want to "replicate" that design in the cloud. VPC peering won't work as 50 is beyond the limit. Answer is C.
👍 43fd692e2024/10/11 - 正解だと思う選択肢: C
VPC Network Peering connections are limited to 25 connections per VPC network.
👍 3gonlafer2024/02/18 Can't be VPC peering. Google VPC supports up to 25 peering connections per VPC, here we need to connect 50 spokes. C is correct
👍 2PeppaPig2024/02/15
シャッフルモード