Building a CI/CD Pipeline ECDE Practice Questions (Page 5)

Questions 21–25

1. 21expert · hard

   A company's CI/CD pipeline uses a shared build server. The security team is concerned about the risk of a compromised build server affecting the deployed applications. They want to mitigate this risk. Which measure should they implement?

   • AUse the same build agent for all projects to reduce overhead.
   • BStore build artifacts in a public repository for transparency.
   • CDisable all security scanning to speed up the build.
   • DUse isolated build agents for each project and sign the build artifacts to ensure integrity.
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   What is the key difference between continuous delivery and continuous deployment?

   • AContinuous delivery is used only for small projects, while continuous deployment is for large enterprises.
   • BContinuous delivery automates the release process up to production, but a human approves the final deployment; continuous deployment automatically deploys every change to production.
   • CContinuous delivery is the same as continuous integration, while continuous deployment is the same as continuous delivery.
   • DContinuous delivery deploys to production automatically, while continuous deployment requires manual approval.
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   Which of the following is a key benefit of implementing a CI/CD pipeline?

   • AIt eliminates the need for automated testing because the pipeline handles all quality checks.
   • BIt removes the need for version control because the pipeline tracks all changes.
   • CIt ensures that every code change is integrated and tested automatically, reducing integration issues.
   • DIt guarantees that no security vulnerabilities will ever be present in the deployed application.
   Reveal Solution Discussion Select an answer first
5. 24application · medium

   A development team wants to automate the release process so that every commit that passes all tests and security scans is automatically deployed to production without human intervention. Which deployment strategy should they implement?

   • AManual deployment, where a release engineer manually runs the deployment script after each commit.
   • BContinuous deployment, where the pipeline automatically deploys to production after all gates pass.
   • CContinuous integration, where the pipeline only builds and tests the code but does not deploy.
   • DContinuous delivery, where the pipeline automatically deploys to a staging environment but requires a manual approval for production.
   Reveal Solution Discussion Select an answer first
6. 25application · medium

   A team has integrated DAST into their CI/CD pipeline. The DAST scan runs after deployment to staging and produces a report. The team wants to track the trend of vulnerabilities over time and be alerted if the number of critical vulnerabilities increases. What should be implemented?

   • ARun DAST only when a new release is deployed to production.
   • BStore DAST results in a centralized dashboard and configure alerts based on severity thresholds.
   • CEmail the DAST report to the security team after each scan.
   • DArchive DAST reports in a shared folder for manual review.
   Reveal Solution Discussion Select an answer first