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

Questions 6–10

1. 6application · medium

   A team notices that their CI pipeline frequently fails at the integration test stage, but they only find out when they check the pipeline dashboard manually. They want to be notified immediately when a pipeline fails so they can respond quickly. Which practice should they adopt?

   • ASet up a weekly report that summarizes pipeline failures and sends it to management.
   • BConfigure the CI/CD tool to send automated notifications (e.g., email, chat, or SMS) to the team when a pipeline run fails.
   • CRequire developers to check the pipeline dashboard at the start of each day.
   • DAdd a step in the pipeline that pauses for 10 minutes after each stage so the team can watch the logs.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   A team wants to use pipeline metrics to identify bottlenecks in their CI/CD process. They have access to pipeline execution logs and dashboards. Which metric would be most useful for identifying a bottleneck in the build stage?

   • AThe average duration of the build stage over the last week.
   • BThe number of commits pushed to the repository each day.
   • CThe number of developers on the team.
   • DThe total number of pipeline runs in a month.
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A team is implementing a quality gate that requires the application to pass a set of acceptance tests before release. However, the acceptance tests are flaky and sometimes fail due to timing issues. The team wants to reduce the impact of flaky tests without removing the gate. Which approach is most appropriate?

   • AInvestigate the root cause of the flakiness and fix the tests, while temporarily allowing a limited number of retries for known flaky tests.
   • BRemove the flaky tests from the acceptance test suite.
   • CDisable the quality gate until the tests are stable.
   • DIncrease the timeout for the acceptance tests to reduce flakiness.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   An organization wants to automate the execution of static code analysis, unit tests, and integration tests every time a developer pushes code to the main branch. They also want the pipeline to stop if any of these checks fail. Which tooling approach best satisfies this requirement?

   • AUse a CI/CD platform that supports pipeline definitions with stages for static analysis, unit tests, and integration tests, and configure failure conditions to stop the pipeline.
   • BUse a build server that only compiles the code and relies on the deployment team to run tests after deployment.
   • CSet up a cron job that runs the tests nightly and emails the results to the team.
   • DAsk developers to run the checks manually before pushing and document the results in a shared spreadsheet.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A team is implementing a quality gate that requires at least 90% of new code to be covered by unit tests. They want to enforce this gate in the pipeline. Which implementation is most appropriate?

   • AAsk developers to estimate coverage and include the estimate in the pull request description.
   • BUse a coverage tool that reports the coverage percentage and configure the pipeline to fail if the percentage is below 90%.
   • CRun coverage analysis only on the main branch after deployment.
   • DUse a code review process where reviewers manually check if tests cover 90% of new code.
   Reveal Solution Discussion Select an answer first