PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #51
PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Question #51: Real Exam Question with Answer & Explanation
The correct answer is D: Perform a blue/green deployment, and test your new application after the deployment is. Blue/green deployment maintains two identical environments: 'blue' (current live version) and 'green' (new version). Traffic is switched from blue to green all at once. If issues arise, you instantly redirect traffic back to blue - the old environment is still running and untouch
Question
You recently deployed your application in Google Kubernetes Engine (GKE) and now need to release a new version of the application. You need the ability to instantly roll back to the previous version of the application in case there are issues with the new version. Which deployment model should you use?
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 deployment is complete.
- CPerform a canary deployment, and test your new application periodically after the new version is
- DPerform a blue/green deployment, and test your new application after the deployment is
Explanation
Blue/green deployment maintains two identical environments: 'blue' (current live version) and 'green' (new version). Traffic is switched from blue to green all at once. If issues arise, you instantly redirect traffic back to blue - the old environment is still running and untouched. Rolling deployments gradually replace instances, making instant rollback difficult. Canary deployments expose only a subset of users to the new version, but rollback is slower. A/B testing splits traffic for comparison purposes, not for safe deployment with rollback.
Topics
Community Discussion
No community discussion yet for this question.