Continuous Testing Tools DSE Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   What is the main purpose of reports generated by continuous testing tools?

   • ATo provide developers with actionable feedback on issues found
   • BTo automatically fix the vulnerabilities
   • CTo replace the need for any further testing
   • DTo store test results for compliance only
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   How do continuous testing tools typically integrate with version control systems?

   • ABy manually copying code to a testing server
   • BBy triggering tests automatically on code commits or pull requests
   • CBy requiring developers to run tests locally before committing
   • DBy replacing the version control system
   Reveal Solution Discussion Select an answer first
4. 13expert · hard

   A team wants to enforce a minimum 80% test coverage and no high-severity SAST findings before code can be merged. However, some legacy modules have very low coverage and would block all changes. The team wants to improve security without halting development. Which approach best balances enforcement and progress?

   • AExempt legacy modules from all testing requirements permanently.
   • BApply the quality gate to new and modified code only, using diff-based coverage, while tracking legacy coverage separately for improvement.
   • CLower the coverage threshold to 50% for all code to avoid blocking any changes.
   • DRequire 100% coverage for all code immediately, blocking any change that does not meet it.
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   A team is introducing continuous testing into a legacy project that has no automated tests. Management wants to see immediate security improvements but developers are resistant because they fear the pipeline will constantly fail. Which approach is most likely to succeed?

   • ARequire 100% test coverage and all security scans to pass from the first day.
   • BDelay continuous testing until the team rewrites the entire application.
   • CStart with a small set of high-value security tests (e.g., SAST on new code and SCA on dependencies) and gradually expand coverage as the team gains confidence.
   • DRun all tests in a separate environment and only report results to management.
   Reveal Solution Discussion Select an answer first
6. 15application · easy

   A team's CI pipeline currently runs unit tests only when a developer manually triggers it. They want to ensure that every commit to the main branch is automatically tested and that the build fails if tests fail. Which configuration should they implement?

   • ARun tests only in the nightly build and report results the next morning.
   • BKeep the manual trigger but add a reminder email to developers to run tests.
   • CRun tests on a schedule but do not fail the build if tests fail.
   • DConfigure the CI system to watch the repository and trigger the pipeline on every push to the main branch, with a build failure on test failure.
   Reveal Solution Discussion Select an answer first