Google Professional Cloud Network Engineer
Get started today
Ultimate access to all questions.
Ultimate access to all questions.
Your organization recently redesigned its cloud environment to use Network Connectivity Center. However, when attempting to add a new VPC named vpc-dev as a spoke, an error occurred due to a conflict with an existing spoke and the IP range of a VPC named vpc-pre-prod. You need to resolve this issue quickly to complete the migration efficiently. What should you do?
Explanation:
The error occurs because the IP range of the new VPC spoke (vpc-dev) overlaps with an existing spoke (vpc-pre-prod). Network Connectivity Center requires non-overlapping IP ranges across spokes to avoid routing conflicts. To resolve this efficiently, the correct approach is to exclude the conflicting IP ranges from being advertised by the new spoke (vpc-dev) using the --exclude-export-ranges flag when creating the spoke. This ensures the hub does not receive duplicate routes for the overlapping range, allowing vpc-dev to be added without disrupting the existing vpc-pre-prod spoke. Deleting subnets (Option A) or removing the existing spoke (Option D) would cause unnecessary downtime or reconfiguration. Option C incorrectly suggests modifying the hub instead of the spoke.