Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.

Unlimited Access

Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.

Exam Professional Cloud Architect topic 1 question 50 discussion

Actual exam question from Google's Professional Cloud Architect
Question #: 50
Topic #: 1
[All Professional Cloud Architect Questions]

You are migrating your on-premises solution to Google Cloud in several phases. You will use Cloud VPN to maintain a connection between your on-premises systems and Google Cloud until the migration is completed. You want to make sure all your on-premise systems remain reachable during this period. How should you organize your networking in Google Cloud?

  • 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
Show Suggested Answer Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
newbie2020
Highly Voted 4 years, 3 months ago
Ans is C, https://cloud.google.com/vpc/docs/using-vpc "Primary and secondary ranges can't conflict with on-premises IP ranges if you have connected your VPC network to another network with Cloud VPN, Dedicated Interconnect, or Partner Interconnect."
upvoted 129 times
Smart
4 years, 2 months ago
Agreed!
upvoted 2 times
...
AD2AD4
3 years, 11 months ago
Perfect.. Exact find in link.
upvoted 2 times
...
elaineshi
1 year, 11 months ago
agree, any ip range, shall use filewall rule to communicate, instead of setting same IP range, which is a mess to control.
upvoted 2 times
...
Sundeepk
3 years, 10 months ago
from the above link - it clearly states - "Primary and secondary ranges for subnets cannot overlap with any allocated range, any primary or secondary range of another subnet in the same network, or any IP ranges of subnets in peered networks." once we create a VPN, they all are part of the same network . Hence option C is correct
upvoted 13 times
...
...
KouShikyou
Highly Voted 4 years, 6 months ago
I think C is correct.
upvoted 21 times
JoeShmoe
4 years, 5 months ago
Agree with C. Secondary IP range still can't overlap
upvoted 10 times
AWS56
4 years, 3 months ago
".... and Google Cloud until the migration is completed." Taking this as the key, the intention is to remove the connection b/w on-prem and GCP once the migration is done. and then the secondary IPs will act as primary. So I will choose D
upvoted 3 times
tartar
3 years, 8 months ago
C is ok
upvoted 10 times
MaxNRG
2 years, 6 months ago
B, The key points here: - migrating in several phases - use Cloud VPN until the migration is completed - all your on-premise systems remain reachable during this period
upvoted 2 times
...
...
zanfo
2 years, 7 months ago
how to manage the routing table in VPC if is present a subnet with the same network of vpn remote net? the correct answer is C
upvoted 1 times
...
...
...
kumarp6
3 years, 5 months ago
Yes C it is
upvoted 2 times
...
nitinz
3 years, 1 month ago
C, no brainer. You have on-prem <--> VPN <---> GCP only way this data flow to work in non-over lapping subnets. You can stretch subnets at layer 7 but you wont be able to route it via VPN.
upvoted 4 times
...
...
heretolearnazure
Most Recent 8 months, 1 week ago
C is correct
upvoted 1 times
...
JC0926
1 year, 1 month ago
Selected Answer: B
Using an IP range on Google Cloud that does not overlap with the range used on-premises (option C) is a good choice to avoid IP address conflicts. However, it is important to use the same IP range as the on-premises applications for the primary IP range to ensure that the on-premises systems remain accessible. Therefore, using the same IP range on Google Cloud as on-premises for the primary IP range and using a secondary range that does not overlap with the range used on-premises can avoid IP address duplication and ensure that the on-premises systems remain accessible. Hence, option B is the better choice.
upvoted 3 times
...
omermahgoub
1 year, 4 months ago
The recommended approach for organizing your networking in Google Cloud to ensure that all your on-premises systems remain reachable during the migration is option C: Use an IP range on Google Cloud that does not overlap with the range you use on-premises. When using Cloud VPN to establish a connection between your on-premises systems and Google Cloud, it is important to ensure that the IP ranges used in your on-premises systems and Google Cloud do not overlap. If the IP ranges overlap, it can cause conflicts and make it difficult to route traffic between your on-premises systems and Google Cloud. To avoid IP range conflicts, you should use an IP range on Google Cloud that is different from the range you use on-premises. This will ensure that all your on-premises systems remain reachable during the migration.
upvoted 2 times
omermahgoub
1 year, 4 months ago
Option A: Using the same IP range on Google Cloud as you use on-premises is not a recommended approach, as it can cause IP range conflicts and make it difficult to route traffic between your on-premises systems and Google Cloud. Option B: Using the same IP range on Google Cloud as you use on-premises for your primary IP range and a secondary range that does not overlap with the range you use on-premises is not a recommended approach, as it can still cause IP range conflicts and make it difficult to route traffic between your on-premises systems and Google Cloud. Option D: Using an IP range on Google Cloud that does not overlap with the range you use on-premises for your primary
upvoted 1 times
...
...
megumin
1 year, 5 months ago
Selected Answer: C
ok for C
upvoted 1 times
...
zr79
1 year, 6 months ago
no overlapping
upvoted 1 times
...
AzureDP900
1 year, 6 months ago
C. Use an IP range on Google Cloud that does not overlap with the range you use on-premises
upvoted 1 times
...
marksie1988
1 year, 7 months ago
Selected Answer: C
C, IP should never overlap if avoidable. double nat is nasty
upvoted 1 times
...
ZLT
1 year, 10 months ago
Selected Answer: C
The correct answer is C
upvoted 2 times
...
Barry123456
1 year, 10 months ago
Selected Answer: C
C Why would you ever create an IP overlap?
upvoted 1 times
...
jonty4gcp
2 years ago
Selected Answer: C
Answer is C
upvoted 1 times
...
Davidik79
2 years, 1 month ago
Selected Answer: C
From here: https://cloud.google.com/vpc/docs/create-modify-vpc-networks "Primary and secondary ranges can't conflict with on-premises IP ranges if you have connected your VPC network to another network with Cloud VPN, Dedicated Interconnect, or Partner Interconnect."
upvoted 1 times
...
[Removed]
2 years, 2 months ago
Selected Answer: C
I got similar question on my exam.
upvoted 3 times
...
Sreedharveluru
2 years, 3 months ago
ANS - C Primary and secondary ranges for subnets cannot overlap with any allocated range, any primary or secondary range of another subnet in the same network, or any IPv4 ranges of subnets in peered networks.
upvoted 2 times
...
OrangeTiger
2 years, 3 months ago
Is D corecct?! Really? I agree with C is correct.
upvoted 2 times
...
vincy2202
2 years, 4 months ago
C is the correct answer
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...