Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Exam Professional Cloud Architect Topic 4 Question 99 Discussion

Actual exam question for Google's Professional Cloud Architect exam
Question #: 99
Topic #: 4
[All Professional Cloud Architect Questions]

You are configuring the cloud network architecture for a newly created project m Google Cloud that will host applications in Compote Engine Compute Engine virtual machine instances will be created in two different subnets (sub-a and sub-b) within a single region

* Instances in sub-a win have public IP addresses

* Instances in sub-b will have only private IP addresses

To download updated packages, instances must connect to a public repository outside the boundaries of Google Cloud You need to allow sub-b to access the external repository. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Mabel at Dec 04, 2024, 01:17 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Della
2 months ago
Option B is the way to go. Unless of course, you prefer to manually SSH into each sub-b instance to update packages. Where's the fun in that?
upvoted 0 times
...
Elsa
2 months ago
Jokes on you, the answer is obviously D. Identity Aware Proxy is the hip and trendy way to handle this kind of scenario these days!
upvoted 0 times
...
Rosendo
2 months ago
I'm not sure, but I'm leaning towards B. Seems like the easiest way to give sub-b access to the external repo without exposing those instances directly.
upvoted 0 times
Glenn
22 days ago
A) Enable Private Google Access on sub-b
upvoted 0 times
...
Jolene
24 days ago
B) Configure Cloud NAT and select sub b in the NAT mapping section
upvoted 0 times
...
Lonny
28 days ago
B) Configure Cloud NAT and select sub b in the NAT mapping section
upvoted 0 times
...
Melita
1 months ago
A) Enable Private Google Access on sub-b
upvoted 0 times
...
...
Svetlana
2 months ago
B is the correct answer. Configuring Cloud NAT is the most straightforward way to provide internet access for instances without public IPs.
upvoted 0 times
...
Christene
2 months ago
I'd go with C. A bastion host in sub-a can act as a gateway for instances in sub-b to reach the repository.
upvoted 0 times
...
Vicki
2 months ago
Option B looks like the way to go. Cloud NAT will let the instances in sub-b access the external repository without having public IPs.
upvoted 0 times
Florinda
1 months ago
That makes sense. Cloud NAT will provide the necessary network address translation for instances in sub-b to access the external repository.
upvoted 0 times
...
Miesha
1 months ago
I agree, setting up Cloud NAT for sub-b is the best solution in this scenario.
upvoted 0 times
...
Lizbeth
1 months ago
Option B looks like the way to go. Cloud NAT will let the instances in sub-b access the external repository without having public IPs.
upvoted 0 times
...
...
Rikki
2 months ago
I think B is the best option as it provides a way for instances in sub-b to access external repositories without exposing them to the public internet
upvoted 0 times
...
Bobbye
2 months ago
I'm not sure, but I think A makes more sense because it allows sub-b to access external resources securely
upvoted 0 times
...
Nicolette
2 months ago
I disagree, I believe the correct answer is B) Configure Cloud NAT and select sub-b in the NAT mapping section
upvoted 0 times
...
Makeda
3 months ago
I think the answer is A) Enable Private Google Access on sub-b
upvoted 0 times
...

Save Cancel