CI/CD Pipeline ECDE Practice Questions (Page 8)

Questions 36–40

1. 36application · medium

   A DevSecOps team wants to store database credentials and API keys used by their CI/CD pipeline. They need to ensure secrets are not exposed in logs or source code, and access is restricted to specific pipeline jobs. What is the most appropriate way to manage these secrets?

   • AUse a dedicated secrets management tool integrated with the pipeline, referencing secrets by name in job configuration.
   • BStore secrets in a plain text file in the repository and read them during the build.
   • CShare secrets via email to all developers and ask them to set them manually in each job.
   • DEmbed secrets directly in the pipeline configuration file as environment variables.
   Reveal Solution Discussion Select an answer first
2. 37application · medium

   A team wants to test a new feature in production with a small subset of real users before rolling it out to everyone. They also need to monitor error rates and be able to stop the test quickly if problems occur. Which deployment strategy fits this requirement?

   • ARolling deployment that replaces instances one by one without traffic splitting.
   • BRecreate deployment that stops the old version and starts the new one.
   • CCanary deployment that routes a small percentage of traffic to the new version.
   • DBlue-green deployment that switches all traffic at once.
   Reveal Solution Discussion Select an answer first
4. 38expert · hard

   A DevSecOps team is migrating from a Jenkins pipeline defined in the UI to pipeline as code. They have multiple teams sharing the same Jenkins instance, and each team wants to manage its own pipeline without affecting others. They also need to enforce security scanning on all pipelines. Which approach best satisfies these requirements?

   • ACreate a single global Jenkinsfile that all teams must use, with no customization allowed.
   • BLet each team configure their own Jenkins jobs in the UI without any shared components.
   • CUse a single Jenkinsfile per team but require them to manually add security scanning steps.
   • DCreate a shared Jenkins library with common security scanning steps and have each team define their own Jenkinsfile in their repository, using the shared library.
   Reveal Solution Discussion Select an answer first
5. 39application · medium

   A team wants their CI pipeline to start automatically whenever a developer pushes code to any branch in their Git repository, but they want to skip the pipeline for documentation-only changes to save resources. Which approach should they use?

   • ARequire developers to manually trigger the pipeline after each push.
   • BUse a webhook that triggers the pipeline only when a pull request is merged.
   • CConfigure the pipeline to trigger on push events and use a path filter to skip runs when only documentation files change.
   • DSet up a scheduled job that runs the pipeline every hour regardless of changes.
   Reveal Solution Discussion Select an answer first
6. 40application · medium

   A development team wants to ensure that every commit to the main branch triggers an automated build and a set of unit tests, and that only commits that pass these tests are merged into the main branch. They are using a Git-based version control system and want to enforce this policy without requiring developers to run tests locally. Which approach should they implement?

   • AConfigure a branch protection rule that requires a status check from a CI pipeline that runs on pull requests.
   • BSet up a webhook that triggers a build only when a tag is pushed to the repository.
   • CCreate a nightly scheduled build that compiles the code and runs tests on the latest main branch.
   • DRequire developers to run a pre-commit hook that executes the unit tests locally before pushing.
   Reveal Solution Discussion Select an answer first