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 Associate Cloud Engineer Exam - Topic 10 Question 73 Discussion

You need to deploy an application in Google Cloud using savorless technology. You want to test a new version of the application with a small percentage of production traffic. What should you do?
A) Deploy the application lo Cloud. Run. Use gradual rollouts for traffic spelling.
B) Deploy the application lo Google Kubemetes Engine. Use Anthos Service Mesh for traffic splitting.
C) Deploy the application to Cloud functions. Saucily the version number in the functions name.
D) Deploy the application to App Engine. For each new version, create a new service.

Google Associate Cloud Engineer Exam - Topic 10 Question 73 Discussion

Actual exam question for Google's Associate Cloud Engineer exam
Question #: 73
Topic #: 10
[All Associate Cloud Engineer Questions]

You need to deploy an application in Google Cloud using savorless technology. You want to test a new version of the application with a small percentage of production traffic. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Deandrea at Dec 11, 2023, 03:29 PM

Limited Time Offer

25%

Off

Get Premium Associate Cloud Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Robt
9 months ago
Wait, you can really do gradual rollouts in Cloud Run? That's cool!
upvoted 0 times
...
Louis
10 months ago
D seems like overkill for just testing a new version.
upvoted 0 times
...
Josefa
10 months ago
C sounds a bit off, not sure about that one.
upvoted 0 times
...
Stephen
10 months ago
I think B is better for traffic splitting.
upvoted 0 times
...
Gladys
10 months ago
A is the way to go for gradual rollouts!
upvoted 0 times
...
Isabelle
10 months ago
I feel like deploying to App Engine and creating a new service for each version might be overkill for just testing a small percentage of traffic. I wonder if that's really necessary.
upvoted 0 times
...
Frank
11 months ago
I practiced a question similar to this, and I think deploying to Cloud Functions and changing the version number could be a way to manage versions, but I'm not confident that's the best method here.
upvoted 0 times
...
Sheridan
11 months ago
I'm not entirely sure, but I think using Anthos Service Mesh for traffic splitting in Kubernetes could be a solid approach too. That might be option B?
upvoted 0 times
...
Deonna
11 months ago
I remember something about gradual rollouts being a good way to test new versions with limited traffic. Maybe option A is the right choice?
upvoted 0 times
...
Rasheeda
11 months ago
I'm a bit confused by the wording of this question. What exactly is "savorless technology"? Is that a real thing, or just a weird way of saying something? I'm leaning towards Option D with App Engine, but I'm not 100% sure.
upvoted 0 times
...
Buddy
11 months ago
Okay, I've got this. Option A looks like the way to go - deploy to Cloud Run and use the built-in gradual rollout capabilities. That way I can test the new version with a small percentage of traffic without disrupting the whole production environment.
upvoted 0 times
...
Vanna
11 months ago
Hmm, this is a tricky one. I'm not sure about the "savorless technology" part - is that a typo or some new Google Cloud feature I'm not aware of? I'll have to think this through carefully.
upvoted 0 times
...
Marnie
11 months ago
I think the key here is to use a technology that supports gradual rollouts and traffic splitting, like Kubernetes or App Engine. Option B with Anthos Service Mesh sounds promising, but I'm not too familiar with that.
upvoted 0 times
...
Vallie
11 months ago
I think a trigger is the way to go. It's a reliable and efficient method for capturing deleted rows and inserting them into the history table.
upvoted 0 times
...
Ardella
11 months ago
Alright, I've got a good feeling about this. I'm going to give it my best shot.
upvoted 0 times
...
Lisandra
2 years ago
I don't know, 'saucily the version number' in Cloud Functions sounds like a bit of a hack to me. I'd want a more robust solution.
upvoted 0 times
...
Vicki
2 years ago
Hmm, I'm leaning towards option B. Using Anthos Service Mesh for traffic splitting seems like a solid approach, and it aligns with the 'savorless technology' clue.
upvoted 0 times
Kiera
2 years ago
Option B offers a solid approach for deploying and testing the application with production traffic.
upvoted 0 times
...
Inocencia
2 years ago
Using Anthos Service Mesh for traffic splitting is a smart move, especially for testing new versions.
upvoted 0 times
...
Ezekiel
2 years ago
I think option B provides a reliable solution for testing the new version with production traffic.
upvoted 0 times
...
Kati
2 years ago
Deploying to Google Kubernetes Engine with Anthos Service Mesh is a strong option for sure.
upvoted 0 times
...
Quentin
2 years ago
I agree, it's important to use the right tool for the job. Option B seems like the best fit here.
upvoted 0 times
...
My
2 years ago
Option B sounds like a good choice. Anthos Service Mesh can handle traffic splitting well.
upvoted 0 times
...
...
Marcos
2 years ago
Haha, 'saucily the version number' - I love it! But you're right, that doesn't seem like the best way to handle this.
upvoted 0 times
...
Hester
2 years ago
This question is pretty straightforward, but I'm not sure about the 'savorless technology' part. Is that a real thing in Google Cloud?
upvoted 0 times
...

Save Cancel