New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Professional Cloud DevOps Engineer Exam - Topic 10 Question 14 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 14
Topic #: 10
[All Professional Cloud DevOps Engineer Questions]

You need to deploy a new service to production. The service needs to automatically scale using a Managed Instance Group (MIG) and should be deployed over multiple regions. The service needs a large number of resources for each instance and you need to plan for capacity. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Joesph
3 months ago
Monitoring with Stackdriver is a smart move, but not the only step!
upvoted 0 times
...
Lorita
3 months ago
n1-highcpu-96 seems like overkill for most services.
upvoted 0 times
...
Charlena
3 months ago
Surprised that deploying in one region is even an option.
upvoted 0 times
...
Pansy
4 months ago
Totally agree, can't overlook quota limits!
upvoted 0 times
...
Bobbye
4 months ago
Option C is crucial for capacity planning.
upvoted 0 times
...
Jamika
4 months ago
Deploying in one region with a global load balancer sounds familiar, but I’m not convinced it meets the requirement for multiple regions.
upvoted 0 times
...
Rusty
4 months ago
I feel like validating resource requirements against quota limits is crucial, but I can't recall if that was emphasized enough in our studies.
upvoted 0 times
...
Alishia
4 months ago
I think we practiced a question about monitoring resources with Stackdriver Trace, but I’m not clear on how that directly relates to planning for capacity in this scenario.
upvoted 0 times
...
Evelynn
5 months ago
I remember we discussed the importance of choosing the right machine type for scaling, but I'm not sure if n1-highcpu-96 is the best choice for our needs.
upvoted 0 times
...
Whitley
5 months ago
I'm pretty confident this is a straightforward one. Option C seems like the best choice - create the release view, set it as default, and use the release pipeline to tag the packages rather than promoting them. That way, you're keeping things simple and only exposing the tested packages.
upvoted 0 times
...
Michal
5 months ago
Hmm, this seems like a tricky one. I'll need to think carefully about the tables that HTML servers regularly poll for changes.
upvoted 0 times
...
Bambi
5 months ago
The salience model is definitely about power, urgency, and legitimacy, as described in option D. That's the key framework I remember for identifying the most important stakeholders to focus on.
upvoted 0 times
...
Wade
5 months ago
Wasn't there a practice question about CAPWAP modes? I feel like "Disconnected" might apply here, but it seems too simplistic for this scenario.
upvoted 0 times
...

Save Cancel