You recently deployed your application in Google Kubernetes Engine, and now need to release a new version of your application. You need the ability to instantly roll back to the previous version in ca

Question

Options

• APerform a rolling deployment, and test your new application after the deployment is complete.
• BPerform A/B testing, and test your application periodically after the new tests are implemented.
• CPerform a blue/green deployment, and test your new application after the deployment is.
• DPerform a canary deployment, and test your new application periodically after the new version is

• A
  5% (1)
• B
  9% (2)
• C
  82% (18)
• D
  5% (1)

Explanation

A blue/green deployment maintains two complete, identical production environments: the current version ('blue') receives all live traffic, while the new version ('green') is deployed in parallel. After verifying the green environment, traffic is switched over instantly. If issues arise, rollback is achieved by switching traffic back to the blue environment - this is immediate and requires no redeployment. This satisfies the requirement to 'instantly roll back.' Option A (rolling deployment) gradually replaces old pods with new ones; rollback requires another rolling deployment cycle, which is not instant. Option B (A/B testing) is for comparing feature variants with subsets of users and is not a rollback strategy. Option D (canary deployment) gradually shifts a small percentage of traffic to the new version; rollback is possible but not instant because the new version is incrementally active across the fleet.

No community discussion yet for this question.