Pipeline Implementation and Quality Gates CT-QDO Practice Questions (Page 5)

Questions 21–25

1. 21foundation · easy

   How can feedback from pipeline monitoring be used to improve quality and process?

   • ABy requiring manual approval for every pipeline run
   • BBy increasing the number of stages in the pipeline to slow down releases
   • CBy analyzing failure trends to identify recurring issues and adjusting test strategies
   • DBy ignoring pipeline failures and focusing only on production incidents
   Reveal Solution Discussion Select an answer first
2. 22expert · hard

   A company is transitioning from a traditional release process to a DevOps model. They want to implement a CI/CD pipeline for the first time. They have a legacy application that is difficult to build and test automatically. Which approach is most appropriate for the initial implementation?

   • AUse a commercial CI/CD tool that promises to automate everything without any configuration.
   • BDesign a comprehensive pipeline with all stages and quality gates from the start.
   • CAutomate only the deployment stage and keep the build and test stages manual.
   • DStart with a simple pipeline that automates the build and runs a small set of smoke tests, then gradually add more stages and quality gates as the team gains experience.
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A team's CI pipeline builds the application and runs unit tests, but the pipeline always proceeds to deployment regardless of test results. The team wants to ensure that failed unit tests automatically stop the pipeline before deployment. Which approach should they implement?

   • AAdd a code review requirement that all tests must be approved by a senior developer before merging.
   • BConfigure the deployment stage to run the unit tests again before deploying.
   • CAdd a quality gate after the test stage that checks the test result status and fails the pipeline if tests failed.
   • DSet up a monitoring alert that notifies the team when tests fail so they can manually stop the pipeline.
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   At which pipeline stage is a quality gate commonly placed to prevent defective code from reaching production?

   • AAt the very beginning of the pipeline before any code is checked out
   • BBefore the deployment stage
   • CAfter the monitoring stage
   • DOnly in the production environment after deployment
   Reveal Solution Discussion Select an answer first
6. 25application · medium

   A team is designing a CI/CD pipeline for a web application. They want to ensure that the application is packaged as an artifact, then deployed to a staging environment for acceptance testing, and finally promoted to production only if acceptance tests pass. Which pipeline stage sequence best matches this requirement?

   • ADeploy to production → Build → Acceptance test → Deploy to staging
   • BBuild → Acceptance test → Deploy to production → Deploy to staging
   • CBuild → Deploy to staging → Acceptance test → Deploy to production
   • DAcceptance test → Build → Deploy to staging → Deploy to production
   Reveal Solution Discussion Select an answer first