QuestionQ350

Ensuring solution and operations excellence

You are creating a continuous-deployment pipeline for a project held in a Git source repository and want to make sure code changes are verified before they are deployed to production. 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.
Explanation

A deployment pipeline should promote the same identified revision through a staging environment for testing before releasing it to production. Tag-based promotion provides a controlled, traceable way to deploy the tested revision to each environment. Continuous-delivery guidance commonly deploys artifacts to preproduction environments for end-to-end tests and updates production only after those tests succeed.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!