Google Exam Associate Cloud Engineer Topic 2 Question 96 Discussion

Actual exam question for Google's Associate Cloud Engineer exam

Question #: 96
Topic #: 2

[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?

ADeploy the application lo Cloud. Run. Use gradual rollouts for traffic spelling.

BDeploy the application lo Google Kubemetes Engine. Use Anthos Service Mesh for traffic splitting.

CDeploy the application to Cloud functions. Saucily the version number in the functions name.

DDeploy the application to App Engine. For each new version, create a new service.

Show Suggested Answer

Suggested Answer: A

by Hershel at Sep 19, 2024, 09:50 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Margarita

2 months ago

I'm curious about Option B. Using Kubernetes Engine and Anthos Service Mesh could be a really powerful combo for testing new versions.

upvoted 0 times

Novella

29 days ago

C) Deploy the application to Cloud functions. Saucily the version number in the functions name.

upvoted 0 times

...

Hortencia

1 months ago

B) Deploy the application lo Google Kubemetes Engine. Use Anthos Service Mesh for traffic splitting.

upvoted 0 times

...

Alishia

2 months ago

A) Deploy the application lo Cloud. Run. Use gradual rollouts for traffic spelling.

upvoted 0 times

...

Linette

2 months ago

Haha, 'savorless technology'? I think you mean 'serverless', but I like the sound of that. Option A seems like a good starting point.

upvoted 0 times

Dorethea

2 months ago

Dorethea: I agree, gradual rollouts for traffic splitting sounds like a safe way to test the new version.

upvoted 0 times

...

Brandon

2 months ago

Brandon: Yeah, 'savorless' does sound interesting. Option A does seem like a good starting point.

upvoted 0 times

...

Alline

2 months ago

Haha, 'savorless technology'? I think you mean 'serverless', but I like the sound of that.

upvoted 0 times

...

Marge

3 months ago

Hmm, I'm not sure about Option C. Putting the version number in the function name feels a bit hacky to me.

upvoted 0 times

...

Quentin

3 months ago

That's a good point, Micaela. Both options A and B seem like viable solutions for testing the new version of the application.

upvoted 0 times

...

Jamal

3 months ago

I'd go with Option D. Creating a new service for each version on App Engine keeps things nice and organized.

upvoted 0 times

...

Jacqueline

3 months ago

Option B sounds like the way to go. Using Anthos Service Mesh for traffic splitting seems like a robust and flexible solution.

upvoted 0 times

Johnson

2 months ago

Yes, Google Kubernetes Engine provides a reliable environment for deploying and managing applications.

upvoted 0 times

...

Shawn

2 months ago

I think deploying the application to Google Kubernetes Engine is a good choice for this scenario.

upvoted 0 times

...

Laura

2 months ago

I agree, Anthos Service Mesh can help manage the traffic splitting effectively.

upvoted 0 times

...

Ernest

2 months ago

Option B sounds like the way to go. Using Anthos Service Mesh for traffic splitting seems like a robust and flexible solution.

upvoted 0 times

...

Maira

2 months ago

I agree, Anthos Service Mesh can help with managing traffic and ensuring a smooth deployment process.

upvoted 0 times

...

Mitsue

2 months ago

Option B sounds like the way to go. Using Anthos Service Mesh for traffic splitting seems like a robust and flexible solution.

upvoted 0 times

...

Micaela

3 months ago

I disagree, I believe option B is the way to go. Using Anthos Service Mesh for traffic splitting can also achieve the same goal.

upvoted 0 times

...

Quentin

3 months ago

I think the best option is A. Gradual rollouts can help test the new version with a small percentage of production traffic.

upvoted 0 times

...