Answer-first summary for fast verification
Answer: Use Jenkins to monitor tags in the repository. Deploy staging tags to a staging environment for testing. After testing, tag the repository for production and deploy that to the production environment.
Option D is the correct answer. The question asks for a solution where code changes can be verified before being deployed to production. Option D uses Jenkins to monitor tags in the repository, deploy staging tags to a staging environment for testing, and only after successful testing, tag the repository for production and deploy it to the production environment. This approach ensures that code changes are tested before being released to production, which aligns with the requirement of verifying changes prior to deployment. Options A, B, and C involve deploying directly to production without a prior comprehensive testing phase, which does not meet the requirement outlined in the question.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You are tasked with building a continuous deployment pipeline for a project stored in a Git source repository. The objective is to ensure that all code changes can be thoroughly verified and tested before being deployed to the production environment to minimize risks and maintain stability. What should you do?
A
Use Spinnaker to deploy builds to production using the red/black deployment strategy so that changes can easily be rolled back.
B
Use Spinnaker to deploy builds to production and run tests on production deployments.
C
Use Jenkins to build the staging branches and the master branch. Build and deploy changes to production for 10% of users before doing a complete rollout.
D
Use Jenkins to monitor tags in the repository. Deploy staging tags to a staging environment for testing. After testing, tag the repository for production and deploy that to the production environment.
No comments yet.