You have an application deployed in production. When a new version is deployed, some issues don't arise until the application receives traffic from users in production. You want to reduce both the impact and the number of users affected.
Which deployment strategy should you use?
To minimize the impact and number of users affected by issues in a new version of an application, the best strategy is Canary deployment. This strategy involves rolling out the new version to a small subset of users first, allowing you to monitor and address any issues before a full-scale deployment. This gradual release ensures that only a limited number of users are impacted at any time, making it easier to handle any potential problems and roll back if necessary.
I tkink it is B) Canary deployment. With Blue/green deployment there will be more users affected.
More than that, blue/green deployment affects all the users as we switch the full production to the new version in one time
exactly, plus with blue green strategy the new version is not gradually exposed to production, but canary is.
1. Reducing impact 2. Number of users affected If you want meet both of the conditions, you need to choose Canary
B is correct
answer is B to reduce impact on users because it's a progressive release
Agree B
I think it is B, but correct answer is A, hmmm....... if we think that we need to test 100% of the traffic, i.e. create a full working test, then right A, because if there is an error we can quickly go back to the old version
B is correct. Blue Green(B/G) affects all users.
For me is B. But I cannot understand why all purchased exam test with this question, put Blue/Green as correct answer. It's so clear that Canary is the rightest one 'cos forward only a few of users to new deploy (not every as blue/green) and also allow the rollback action
I think the concept of google about B/G testing is that there is a shadow running next to production that receives the same traffic as production. When this shadow is not having any errors you can update the shadow to PROD. So no user is impacted, since all possible new errors will occur in the shadow and not in prod.
Find more info here: https://cloud.google.com/architecture/implementing-deployment-and-testing-strategies-on-gke#perform_a_bluegreen_deployment
For me it's B, in Canary Deployment only a percentage of users receives the new version and therefore in case of error immediately rollback , B/G immediately the new version , Green, receive all traffic and Blue marked as deprecated
Blue/Green is 100% users to Green, Canary id progressive. B.
I think A is correct because of the switching to green only happens after you perform all the tests on it. So you can also test traffic (to satisfy the question) This is the point of blue-green deployment as far as I understood it. B is not correct because the real traffic is switched partially to new version immediately and so it effects some users. reference: https://digitalvarys.com/what-is-blue-gren-deployment/
I would go with B as it is best suited for this senario.
B: https://cloud.google.com/architecture/application-deployment-and-testing-strategies#canary_test_pattern
That's exactly what Canary Deployment is for.
B. Canary deployment: In this strategy, the new version of the application (the "canary") is rolled out to a small subset of users before it is made available to the entire user base. This allows you to monitor the performance and stability of the new version in the real-world production environment with actual traffic, but only affects a small group of users. If issues arise, the canary deployment can be rolled back with minimal impact.
this is A, Canary is a Testing strategy not a deployment strategy.