Answer-first summary for fast verification
Answer: Use an IP range on Google Cloud that does not overlap with the range you use on-premises
The correct answer is C because Google Cloud documentation explicitly states that primary and secondary IP ranges cannot conflict with on-premises IP ranges when connected via Cloud VPN, Dedicated Interconnect, or Partner Interconnect. This prevents routing conflicts and ensures proper traffic flow between on-premises and cloud environments. Option A is incorrect as using the same IP range causes immediate routing conflicts. Option B is incorrect because even the primary range cannot overlap with on-premises ranges. Option D is incorrect as the secondary range also cannot overlap with on-premises ranges. The community discussion strongly supports C with 82% consensus, citing official documentation and emphasizing that overlapping IP ranges create routing issues that prevent connectivity.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You are migrating your on-premises solution to Google Cloud in phases and will use Cloud VPN to maintain connectivity. How should you design your Google Cloud networking to ensure all on-premises systems remain reachable during the entire migration?
A
Use the same IP range on Google Cloud as you use on-premises
B
Use the same IP range on Google Cloud as you use on-premises for your primary IP range and use a secondary range that does not overlap with the range you use on-premises
C
Use an IP range on Google Cloud that does not overlap with the range you use on-premises
D
Use an IP range on Google Cloud that does not overlap with the range you use on-premises for your primary IP range and use a secondary range with the same IP range as you use on-premises
No comments yet.