Continuous Testing Tools DSE Practice Questions (Page 10)

Questions 46–50

1. 46foundation · easy

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

   • ATo automatically fix any defects found during testing
   • BTo provide a graphical interface for test results
   • CTo block the pipeline if certain testing or security criteria are not met
   • DTo replace the need for manual testing
   Reveal Solution Discussion Select an answer first
2. 47foundation · easy

   How do continuous testing tools facilitate rapid remediation for developers?

   • ABy delaying the report until the end of the sprint
   • BBy hiding low-severity issues to reduce noise
   • CBy automatically deploying fixes to production
   • DBy providing detailed, contextual information about the vulnerability and its location
   Reveal Solution Discussion Select an answer first
4. 48application · medium

   A team uses a popular open-source library that was recently found to have a critical vulnerability. They want to prevent any build that includes this vulnerable version from being deployed. Which action should they take in their CI pipeline?

   • ARun a DAST scan on the application to detect the vulnerability in the running system.
   • BManually check the library version in every developer's local environment before merging.
   • CRemove the library from the codebase immediately without checking for alternatives.
   • DAdd an SCA policy that fails the build if the library version matches the known vulnerable version.
   Reveal Solution Discussion Select an answer first
5. 49foundation · easy

   What is the primary purpose of continuous testing in a DevSecOps pipeline?

   • ATo provide continuous feedback on quality and security risks throughout the delivery pipeline
   • BTo ensure that all tests are executed in a production environment
   • CTo replace all manual testing with automated testing
   • DTo eliminate the need for a separate security testing phase
   Reveal Solution Discussion Select an answer first
6. 50expert · hard

   A team has a CI pipeline that runs unit tests, SAST, and SCA on every commit. They notice that the pipeline frequently fails due to flaky unit tests, which blocks the SAST and SCA results from being reported. Developers are ignoring the pipeline because it is unreliable. What is the best way to maintain security testing while addressing the flaky test problem?

   • ARemove the quality gate so the pipeline always passes regardless of test results.
   • BSeparate the security scans (SAST and SCA) from the unit test job so they run independently and report results even if unit tests fail.
   • CIncrease the number of retries for unit tests in the pipeline.
   • DDisable the unit tests until they are fixed and run only SAST and SCA.
   Reveal Solution Discussion Select an answer first