Exam Professional Cloud DevOps Engineer topic 1 question 7 discussion

i guess A

Ans A https://spinnaker.io/guides/user/canary/best-practices/#compare-canary-against-baseline-not-against-production You might be tempted to compare the canary deployment against your current production deployment. Instead always compare the canary against an equivalent baseline, deployed at the same time. The baseline uses the same version and configuration that is currently running in production, but is otherwise identical to the canary: Same time of deployment Same size of deployment Same type and amount of traffic In this way, you control for version and configuration only, and you reduce factors that could affect the analysis, like the cache warmup time, the heap size, and so on.

Explanation taking into account the in-memory cache: In-memory Cache Impact: The in-memory cache loading at start time means that both the canary and the current production version could have different data in their caches. This difference could skew the comparison if you compare the canary directly to the existing production version (Option C). Leveling the Playing Field: By deploying a fresh instance of the current production version (Option A), you ensure that both the canary and the comparison baseline have the same starting point in terms of cache data. This makes the comparison more accurate and reliable.

Answer A

Ans: A

and apply " a new deployment production " for analysis is against canary test purpose.

i think i will go with D the baseline version must have : Ensure that the baseline and production versions of your application are identical. Deploy the baseline version at the same time that you deploy the canary. Ensure that the baseline deployment (such as the number of application instances and autoscaling policies) matches the canary deployment. Use the baseline version to serve the same traffic as the canary. in this case , the " new deployment of production" as a baseline version is violating the third rules ? the new deployment of production is not matching canary deployment

A is correct

A is right You might be tempted to compare the canary deployment against your current production deployment. Instead always compare the canary against an equivalent baseline, deployed at the same time. The baseline uses the same version and configuration that is currently running in production, but is otherwise identical to the canary: Same time of deployment Same size of deployment Same type and amount of traffic In this way, you control for version and configuration only, and you reduce factors that could affect the analysis, like the cache warmup time, the heap size, and so on.

A is the answer. https://cloud.google.com/architecture/application-deployment-and-testing-strategies#canary_test_pattern We recommend that you compare the canary against an equivalent baseline and not the live production environment.

answer is A

Ans : A

Correct with most comments here. It must be A.

A is ok

A is correct!!!

A is the correct answer

Ans : A