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

Questions 26–29

1. 26expert · hard · select all that apply

   A team is integrating automated tests into their CI/CD pipeline. They have a large legacy codebase with poor testability, and the existing tests are slow and flaky. They want to improve the reliability and speed of their test automation. Which two practices would be most effective? (Select all that apply.)

   • ADelete the flaky tests to keep the pipeline stable.
   • BIncrease the timeout for all tests to reduce flakiness.
   • CRefactor the code to improve testability, and introduce test doubles to isolate units.
   • DRun the full test suite in parallel on multiple machines to reduce execution time.
   Check answers Discussion Select an answer first
2. 27foundation · easy

   How is test automation typically integrated into a CI/CD pipeline?

   • AAs a manual step triggered by a tester
   • BAs a stage that runs automatically after the build
   • CAs a one-time activity before the first release
   • DAs a replacement for the build stage
   Reveal Solution Discussion Select an answer first
4. 28foundation · easy

   What is the purpose of a quality gate in a CI/CD pipeline?

   • ATo decide whether a build can proceed to the next stage
   • BTo deploy the build to production automatically
   • CTo replace the need for testing
   • DTo automatically fix defects in the code
   Reveal Solution Discussion Select an answer first
5. 29expert · hard

   A team is adopting CI, but the developers are reluctant to commit to the main branch frequently because the full build and test suite takes 30 minutes. They worry that frequent commits will cause long queues and slow feedback. The team has a mix of unit tests (2 minutes) and integration tests (25 minutes). Which approach best balances the need for frequent integration with fast feedback?

   • ARun the unit tests on every commit, and run the integration tests on a separate pipeline that is triggered after the unit tests pass, but do not block the commit on the integration tests.
   • BHave developers run the full test suite locally before committing, and only commit if it passes.
   • CRequire the full build and test suite to pass on every commit before merging, accepting the 30-minute wait.
   • DReduce the frequency of commits to once a day to minimize the number of times the full suite runs.
   Reveal Solution Discussion Select an answer first