You are using Network Connectivity Center and you already have the hub configured. All VPCs in your environment need to have network connectivity to each other. All the subnet ranges are unique. You…

Question

Options

• AConfigure a star topology, add the VPC spokes to the hub, and specify all subnet ranges in the
• BConfigure a mesh topology, add the VPC spokes to the hub, and specify all subnet ranges in the
• CConfigure a mesh topology, and add the VPC spokes to the hub.
• DConfigure a star topology, and add the VPC spokes to the hub.

• A
  10% (3)
• B
  13% (4)
• C
  3% (1)
• D
  74% (23)

Explanation

In a Network Connectivity Center (NCC) setup where all VPCs in your environment need connectivity to each other, and the subnet ranges are unique, the recommended approach is to configure a star topology: Star topology with a central hub: - In a star topology, all VPC spokes are connected to a central hub. This simplifies network management and ensures that all VPCs can communicate with each other by routing traffic through the hub. - NCC's hub-and-spoke model is designed for this kind of centralized connectivity. Unique subnet ranges: - Since all subnet ranges are unique, there are no IP conflicts, and route exchange between VPCs via the hub works seamlessly. There is no need to filter or exclude subnets using excludeExportRanges. Simplifies routing: - In a star topology, routes are automatically propagated between VPCs through the hub, making it easier to manage and scale the network. Why not mesh topology? - A mesh topology involves direct connections between all VPCs, which becomes complex and harder to manage as the number of VPCs grows. In this case, a star topology provides a simpler and more scalable solution. By adding all VPC spokes to the hub, you enable full connectivity between the VPCs while maintaining a manageable and scalable network design.

No community discussion yet for this question.