Role of DevSecOps in the CI/CD Pipeline DSE Practice Questions (Page 7)

Questions 31–35

1. 31foundation · easy

   What is a key measure to secure the CI/CD pipeline itself against unauthorized changes?

   • AUsing the same credentials for all pipeline users to simplify administration.
   • BImplementing strong access control and multi-factor authentication for the pipeline management interface.
   • CAllowing all developers to directly modify the production pipeline without review.
   • DDisabling audit logging to reduce storage costs.
   Reveal Solution Discussion Select an answer first
2. 32expert · hard

   A team is using multiple security tools in their CI/CD pipeline. They are receiving too many false positives, causing developers to ignore the results. Which strategy is most effective to improve the signal-to-noise ratio?

   • AIncrease the severity threshold so only critical findings are reported.
   • BSend all findings to a separate security dashboard that developers rarely check.
   • CTune the security tools to reduce false positives and prioritize findings based on exploitability and business impact.
   • DDisable all security tools except for one that has the fewest false positives.
   Reveal Solution Discussion Select an answer first
4. 33application · medium

   A development team uses a Jenkins pipeline to build and deploy a Java application. The security team wants to ensure that known vulnerable dependencies are caught before the application is packaged into an artifact. Which stage-level integration best achieves this?

   • AAdd an OWASP Dependency-Check step in the build stage that fails the build on critical vulnerabilities.
   • BRun a SAST scan in the post-build stage and send the report to the security team for manual review.
   • CConfigure the Jenkins server to use LDAP authentication for all users.
   • DDeploy the application to a staging environment and run a DAST scan against it.
   Reveal Solution Discussion Select an answer first
5. 34expert · hard

   A team is migrating from a monthly release cycle to continuous delivery. They want to ensure that every change that reaches production has passed security checks, but they also want to avoid slowing down the pipeline. Which strategy best balances speed and security?

   • ASkip security checks for small changes and run them only for large features.
   • BRun fast security checks (SAST, secret scanning) on every commit, and run slower checks (DAST, dependency scanning) on a nightly or pre-release basis.
   • CRun all security checks on every commit, including full DAST and penetration tests.
   • DRun all security checks only at the end of the release cycle, as before.
   Reveal Solution Discussion Select an answer first
6. 35application · medium

   A team is setting up a CI/CD pipeline for a containerized application. They want to ensure that the container image is secure before it is deployed. Which security control should be integrated at the container build stage?

   • ARuntime application self-protection (RASP).
   • BDynamic application security testing (DAST).
   • CContainer image scanning for known vulnerabilities.
   • DInteractive application security testing (IAST).
   Reveal Solution Discussion Select an answer first