Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 49 of 101
Free Preview · 101 of 335 · questions 1–101 of 335 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
The issue with using the same IP ranges as on-prem is purely a routing issue. The VPN tunnel secures the traffic between the networks(on-prem and GCP). However, the routing within each network still depends on unique IP addresses.
1. IP Address Conflicts: When you have overlapping IP ranges between your on-premises network and your Google Cloud network, you'll run into routing conflicts. Devices won't know where to send traffic, leading to connectivity problems and unreachable systems. 2. Cloud VPN and Routing: Cloud VPN creates a secure tunnel between your on-premises network and your Google Cloud Virtual Private Cloud (VPC). To ensure proper routing, each side of the connection needs to have distinct, non-overlapping IP address spaces. 3. Best Practice for Hybrid Networks: Using different IP ranges is a standard best practice for hybrid cloud setups. It prevents ambiguity and ensures that traffic flows correctly between your on-premises and cloud environments.
question is tricky. as network architect knowing gcp i have exp that you can use non-overlapping secondary ranges for vpn as well. in many migrations it is not possible to make new addressing hence you need to make them overlapping. this is why 2nd ranges are so useful. B is better choice. more realistic and possible in gcp. from overall perspective i agree to have non-overlapping but do not forget this is migration and you need to have full connectivity all the time. it is also not mentioning about what ips should be used