Continuous Integration, Continuous Testing and Continuous Delivery CT-ATT Practice Questions (Page 5)

Questions 21–25

1. 21expert · hard

   A team is deploying a new version of a service that is critical for real-time data processing. They need to ensure zero downtime and the ability to roll back instantly if the new version fails. They also want to test the new version with a small subset of traffic before rolling out to all users. Which deployment strategy best meets all these requirements?

   • ABig bang deployment
   • BCanary deployment only
   • CFeature toggles only
   • DBlue-green deployment with a canary phase
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   Which of the following is an example of a quality gate?

   • AA code review by a senior developer
   • BA manual approval from the product owner
   • CA minimum test coverage percentage that must be achieved
   • DA scheduled backup of the database
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   How does continuous delivery differ from continuous deployment?

   • AContinuous delivery automates all testing, while continuous deployment does not
   • BContinuous delivery requires a manual decision to release to production
   • CContinuous delivery does not use a CI pipeline
   • DContinuous delivery is only for small projects
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   Which stage is typically the first in a CI/CD pipeline?

   • ADeploy to production
   • BAcceptance testing
   • CRelease
   • DBuild
   Reveal Solution Discussion Select an answer first
6. 25expert · hard

   A team is struggling with a long feedback loop: developers commit code, but the CI pipeline takes 45 minutes to run the full test suite, and the results are only reported via email. Developers often continue working on new features before seeing the results, leading to multiple broken commits. Which change would most effectively shorten the feedback loop?

   • AKeep the full test suite but reduce the timeout for each test to make the pipeline faster.
   • BHave developers run the full test suite locally before committing, and only commit if it passes.
   • CSplit the test suite into fast unit tests and slower integration tests, run the unit tests on every commit, and report results in the developer's IDE or chat tool.
   • DSend the test results via email more frequently, such as after each test stage.
   Reveal Solution Discussion Select an answer first