CI/CD Pipeline ECDE Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   What does the term 'pipeline as code' refer to in CI/CD?

   • AStoring the pipeline configuration in a database that is accessed at runtime
   • BWriting the application code in a programming language that is compiled into a pipeline
   • CUsing a graphical interface to design the pipeline without writing any code
   • DDefining the pipeline configuration in a file that is stored in version control
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   How does a CI/CD orchestration tool typically trigger a pipeline run?

   • ABy manually running the pipeline after every code review
   • BIn response to events such as code pushes or pull requests in a version control system
   • CBy scheduling a build at the end of each sprint
   • DBy monitoring the production environment for errors
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A security audit requires that only authorized personnel can deploy to production and that all deployments are logged with the identity of the person who approved them. What should be added to the CI/CD pipeline to meet this requirement?

   • AAn approval gate in the pipeline that requires a designated approver to authorize the deployment, with audit logging enabled.
   • BA notification email sent after deployment with a list of changes.
   • CA shared password that any team member can use to trigger the deployment.
   • DA script that automatically deploys to production without any manual intervention.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A software company wants to ensure that only code that passes automated tests and security scans is deployed to production. They plan to use a CI/CD pipeline. Which sequence of stages best enforces this requirement?

   • ATest, deploy to production, then build.
   • BDeploy to production, then run tests and security scans.
   • CSecurity scan, deploy to production, then build.
   • DBuild, test, security scan, deploy to production.
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A team is designing a deployment pipeline for a web application. They need to support rolling back to a previous version quickly if a deployment fails. They also need to ensure that the exact artifact that was tested is deployed. Which combination of practices best achieves both goals?

   • AStore immutable artifacts in a repository with version tags and use a blue-green deployment strategy.
   • BRebuild the artifact from source during deployment and use a rolling deployment strategy.
   • CStore artifacts in a shared folder and use a canary deployment strategy.
   • DUse a single artifact that is overwritten on each build and deploy it with a recreate strategy.
   Reveal Solution Discussion Select an answer first