Google Cloud Certified Associate Cloud Engineer Practice

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the Google Cloud Certified Associate Cloud Engineer Exam with flashcards and multiple choice questions. Each question includes hints and explanations to help you study effectively. Get ready to pass your certification exam!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.

Your team has some new functionality that they want to roll out slowly so they can monitor for errors. The change contains some significant changes to the user interface. You've chosen to use traffic splitting to perform a canary deployment. You're going to start by rolling out the code to 15% of your users. How should you go about setting up traffic splitting?

A. Deploy the new version. Split the traffic using an IP or cookie based distribution.
B. Use the gcloud app deploy command with the distribution flag to deploy and split the traffic in one command.
C. Deploy the new version using the no-promote flag. Split the traffic using a random distribution.
D. Deploy the new version using the no-promote flag. Split the traffic using distribution.

The correct answer is: D. Deploy the new version using the no-promote flag. Split the traffic using distribution.

Setting up traffic splitting for a canary deployment involves deploying the new version of the application while ensuring that the previous version remains accessible. The approach of using the no-promote flag during the deployment is crucial here. This flag allows the new version to be deployed without instantly routing all traffic to it. By doing so, you maintain the ability to gradually control the percentage of traffic that is used to test the new functionality, which is essential for monitoring and mitigating errors. In this scenario, opting to split the traffic using a distribution method indicates that you can finely tune the flow of traffic to the new version of the application. This ensures that only the predetermined percentage, in this case, 15%, of users receive the new version. This controlled rollout enables effective monitoring and helps catch any potential issues early before a wider release. Other approaches, like using IP or cookie-based distribution or deploying with gcloud app deploy without the no-promote flag, would result in an immediate promotion of the new version to users without the ability to monitor its impact carefully. These alternatives do not provide the same level of control over traffic distribution, which is critical for a canary deployment strategy.