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

Questions 26–28

1. 26expert · hard

   A team is implementing a quality gate that requires the application to have zero known critical defects before release. They have a large backlog of defects, and the team is under pressure to release a new feature. The product owner wants to release the feature while the critical defects are still open. Which approach best balances the quality gate with the business need?

   • ARequire the team to fix all critical defects before release, regardless of the business pressure.
   • BDisable the quality gate temporarily so the release can proceed.
   • CNegotiate with the product owner to define a risk-based exception process that allows release with documented mitigation and a plan to fix the defects in the next iteration.
   • DRelease the feature without any quality gate, and fix the defects after release.
   Reveal Solution Discussion Select an answer first
2. 27foundation · easy

   What is a common practice for integrating quality checks into an automated CI/CD pipeline?

   • APerforming manual code reviews after every deployment
   • BRunning static code analysis as a step in the pipeline
   • CSkipping tests to speed up the pipeline
   • DUsing a spreadsheet to track test results
   Reveal Solution Discussion Select an answer first
3. 28foundation · easy

   What is the primary purpose of a CI/CD pipeline in a DevOps context?

   • ATo provide a graphical interface for developers to manually trigger each stage of the software release process
   • BTo automate the process of delivering software changes from commit to deployment in a reliable and repeatable way
   • CTo replace the need for manual testing by automatically generating test cases from production data
   • DTo store all source code and configuration files in a central repository for version control
   Reveal Solution Discussion Select an answer first