Your organization recently re-architected your cloud environment to use Network Connectivity Center. However, an error occurred when you tried to add a new VPC, named vpc-dev, as a spoke. The error…

Question

Options

• ADelete the VMs associated with the conflicting subnets, then delete the conflicting subnets in vpc-
• BExclude the conflicting IP range by using the --exclude-export-ranges flag when creating the VPC
• CExclude the conflicting IP range by using the --exclude-export-ranges flag in the hub when
• DRemove the conflicting VPC spoke for vpc-pre-prod from the set of VPC spokes in Network

• A
  3% (1)
• B
  74% (29)
• C
  15% (6)
• D
  8% (3)

Explanation

When adding a new VPC as a spoke in Network Connectivity Center, IP address space conflicts between spokes will block the operation. The correct resolution is to use the --exclude-export-ranges flag when adding vpc-dev as a spoke, which explicitly excludes the overlapping IP ranges from being exported to the hub. This avoids disrupting the existing vpc-pre-prod spoke and completes the migration efficiently. Option A is destructive (deleting VMs/subnets). Option C incorrectly applies the flag at the hub level. Option D removes the existing vpc-pre-prod spoke entirely, which is more disruptive than necessary.

No community discussion yet for this question.