DevOps Principles and Pipelines DSE Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   What is the primary purpose of continuous integration (CI)?

   • ATo create release branches for each feature
   • BTo frequently merge code changes into a shared repository and run automated builds and tests
   • CTo automatically deploy every code change to production
   • DTo manually review and approve all code changes before merging
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A DevSecOps team is designing a pipeline for a web application. They want to run SAST, dependency scanning, and DAST. The application must be deployed to a staging environment before DAST can run. However, the team also wants to fail the pipeline as early as possible to save time. Which pipeline design best balances early failure with the need for DAST?

   • ARun SAST and dependency scanning in the build stage, then deploy to staging and run DAST in the test stage.
   • BRun SAST and DAST in the build stage, and dependency scanning in the deploy stage.
   • CRun all security scans only after deploying to production.
   • DRun DAST in the build stage, then SAST and dependency scanning in the test stage.
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   Which security check is commonly integrated into the build or test stage of a CI/CD pipeline to analyze source code for vulnerabilities?

   • ARuntime application self-protection (RASP)
   • BStatic Application Security Testing (SAST)
   • CDynamic Application Security Testing (DAST)
   • DPenetration testing
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A team is building a CI/CD pipeline for a microservices application. They want to run security scans on each service and deploy them independently. However, they also want to ensure that the entire system is tested together before any service is released to production. Which pipeline design best meets both requirements?

   • ARun per-service pipelines with build, security scans, and unit tests, then deploy all services to a shared staging environment for integration testing before production.
   • BRun all services through a single monolithic pipeline that builds and tests everything together.
   • CDeploy each service to production immediately after its own tests pass, without integration testing.
   • DRun security scans only on the shared staging environment after all services are deployed.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A company wants to ensure that every code change that passes automated tests is automatically deployed to a production-like staging environment, but a human must approve the final production deployment. Which practice should they implement?

   • ARelease management, where a release engineer manually deploys to staging and production.
   • BContinuous delivery, with automated deployment to staging and a manual approval gate before production.
   • CContinuous integration, with automated builds and tests but no deployment to staging.
   • DContinuous deployment, with automated deployment to both staging and production.
   Reveal Solution Discussion Select an answer first