CI/CD Pipeline ECDE Practice Questions (Page 4)

Questions 16–20

1. 16expert · hard

   A team is migrating their CI/CD pipeline from a manually configured Jenkins server to a pipeline-as-code approach using GitHub Actions. They need to ensure that the pipeline logic is reusable across multiple repositories and that secrets are managed centrally. Which approach should they take?

   • ACopy the workflow file into each repository and store secrets in each repository's settings.
   • BUse a Jenkinsfile in each repository and trigger it from GitHub Actions.
   • CStore the workflow in a shared drive and manually copy it to each repository when changes are needed.
   • DCreate a composite action or reusable workflow in a central repository and reference it from each repository's workflow file, using GitHub Environments to store secrets.
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A company's CI pipeline produces a signed software package. The deployment pipeline must verify the signature before deploying to production. They also need to ensure that the package has not been tampered with since it was built. What is the best practice?

   • AStore only the package in the artifact repository and trust that it is unchanged.
   • BUse a shared network drive to store the package and rely on file permissions for security.
   • CVerify the signature only at build time and not at deployment.
   • DStore the package and its signature in an artifact repository and have the deployment pipeline verify the signature before deployment.
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   What is the primary role of the 'deploy' stage in a CI/CD pipeline?

   • ATo compile the source code into executable binaries
   • BTo write unit tests for the application
   • CTo install and configure the application in a target environment
   • DTo store the source code in a version control system
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A company runs a critical application that must maintain high availability. They want to deploy new versions with minimal risk and be able to test the new version with a small percentage of real traffic before full rollout. However, they also need to be able to roll back instantly if a problem is detected. Which strategy should they choose?

   • ARecreate deployment with a backup restore.
   • BCanary deployment with automated rollback based on health checks.
   • CRolling deployment with manual rollback.
   • DBlue-green deployment with a full traffic switch.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A startup wants to reduce the time between writing code and getting feedback from automated tests. They currently run tests manually after all developers finish their features. What is the primary benefit of adopting continuous integration?

   • AAutomatically building and testing every code change as soon as it is committed.
   • BRequiring developers to manually trigger builds after merging all features.
   • CRunning tests only at the end of the sprint to save resources.
   • DDeploying every commit directly to production without any testing.
   Reveal Solution Discussion Select an answer first