Automation in CI/CD CT-QDO Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   What is the primary goal of regression testing in a CI/CD pipeline?

   • ATo test new features for the first time
   • BTo detect unintended changes and ensure stability
   • CTo measure the performance of the CI/CD pipeline itself
   • DTo replace all other types of testing
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Why are automated regression tests particularly valuable in a CI/CD pipeline?

   • AThey are only run once before release
   • BThey guarantee that no defects will be released
   • CThey can be run frequently and consistently with every build
   • DThey eliminate the need for any manual testing
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A team's automated regression tests require a large, complex dataset that takes 30 minutes to generate. The team wants to keep the CI pipeline fast while ensuring the tests have the data they need. They also need to ensure the data is consistent across test runs. What is the best strategy?

   • AUse a smaller dataset that can be generated quickly, even if it reduces test coverage.
   • BPre-generate the dataset and store it as a versioned artifact, then restore it quickly in the pipeline before tests run.
   • CGenerate the dataset in parallel with the test execution to save time.
   • DGenerate the dataset from scratch in every pipeline run to ensure freshness.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A team is adding automated regression tests to their CI pipeline. They have a set of tests that depend on a specific test data configuration. To ensure the tests run reliably, what should they do?

   • AAutomate the setup of the test data configuration as part of the regression test execution.
   • BSkip the tests if the configuration is not set up.
   • CMake the tests independent of the configuration by hardcoding the data in the test code.
   • DDocument the required configuration and ask testers to set it up manually before each run.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A DevOps team must provide real-time quality reporting to multiple stakeholders with different needs: developers want detailed test failure logs, while management wants high-level trend dashboards. The team has limited resources and cannot maintain two separate reporting systems. What is the best approach?

   • ACreate two separate reports: one detailed for developers and one summary for management, and maintain them independently.
   • BSend all detailed test logs to management and let them filter out what they need.
   • CProvide only the high-level trend dashboard to everyone, including developers.
   • DImplement a single reporting platform that provides role-based views: detailed logs for developers and aggregated trend dashboards for management.
   Reveal Solution Discussion Select an answer first