CI/CD Pipeline ECDE Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   What is a common access control measure for CI/CD pipelines to ensure only authorized users can trigger production deployments?

   • AStoring deployment credentials in the pipeline configuration file
   • BUsing the same credentials for all pipeline stages
   • CImplementing role-based access control (RBAC) with separate roles for developers and release managers
   • DAllowing all developers to deploy to production without restrictions
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   An e-commerce platform needs to deploy a new version of its web application with zero downtime. The team wants to be able to instantly roll back to the previous version if a critical issue is detected after deployment. Which deployment strategy best meets these requirements?

   • ARolling deployment, where instances are gradually updated one by one.
   • BCanary deployment, where a small percentage of traffic is sent to the new version.
   • CBlue-green deployment, where the new version is deployed to an idle environment and traffic is switched over.
   • DRecreate deployment, where the old version is stopped and the new version is started.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A DevSecOps team is implementing a CI/CD pipeline and needs to store database credentials and API keys securely. They want to avoid hardcoding secrets in the pipeline configuration and ensure that only authorized pipeline jobs can access them. Which approach should they use?

   • AStore the secrets in a plain text file in the repository and reference it in the pipeline.
   • BUse the pipeline tool's built-in secrets management feature to store secrets and inject them as environment variables in the job.
   • CEmbed the secrets directly in the pipeline configuration file.
   • DSend the secrets to the pipeline via email to the administrator who runs the job manually.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A team wants to enforce code review on their CI/CD pipeline configuration. They want every change to the pipeline definition to require approval before it takes effect. Which practice supports this?

   • AEmail the pipeline file to the team lead for approval before uploading it manually.
   • BUse a shared network drive to store the pipeline file and rely on file permissions.
   • CStore the pipeline definition in a version-controlled file and require pull request reviews before merging.
   • DEdit the pipeline configuration directly on the CI server and save changes.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A company wants to release new features to production multiple times per day. They currently perform manual deployments after a long testing phase. What is the most effective way to achieve frequent, reliable releases?

   • AHire more manual testers to speed up the testing process.
   • BDeploy directly from developer machines to production to save time.
   • CImplement a CI/CD pipeline that automates build, test, and deployment with automated quality gates.
   • DIncrease the length of the testing phase to catch more bugs before release.
   Reveal Solution Discussion Select an answer first