Building a CI/CD Pipeline ECDE Practice Questions (Page 7)

Questions 31–35

1. 31foundation · easy

   In a typical CI/CD pipeline, which component is responsible for storing and managing the source code of the application?

   • ABuild server (e.g., Jenkins)
   • BVersion control system (e.g., Git)
   • CArtifact repository (e.g., Nexus)
   • DDeployment target (e.g., Kubernetes cluster)
   Reveal Solution Discussion Select an answer first
2. 32application · medium

   A development team uses a self-hosted CI/CD server with a shared runner pool. The pipeline for a Java application compiles code, runs tests, and publishes artifacts to an internal repository. The team wants to ensure that secrets used during the build are not exposed to other jobs running on the same runner. What should be configured?

   • AUse the same runner for all jobs but mask the secrets in the logs.
   • BUse a dedicated runner for the pipeline and store secrets in the CI/CD server's secret vault, referencing them only in the job that needs them.
   • CStore secrets in a plain text file in the repository and read them during the build.
   • DEmbed the secrets directly in the pipeline script so they are available to all jobs.
   Reveal Solution Discussion Select an answer first
4. 33application · medium

   A DevSecOps engineer is setting up a CI/CD pipeline for a project that uses multiple cloud services. The pipeline needs to authenticate to different cloud providers and internal services. What is the most secure way to manage the required secrets?

   • AStore all secrets in environment variables in the CI server configuration.
   • BUse the same service account credentials for all environments to simplify management.
   • CUse a dedicated secrets management tool like HashiCorp Vault and integrate it with the pipeline to dynamically retrieve secrets.
   • DEncrypt the secrets in a file and commit it to the repository with a decryption key in the pipeline.
   Reveal Solution Discussion Select an answer first
5. 34expert · hard

   A team is building a CI/CD pipeline for a legacy application that has a long build time and no automated tests. They want to introduce CI/CD gradually without disrupting the current release process. Which approach should they take?

   • AStart by automating the build and adding a few smoke tests, then gradually add more stages as confidence grows.
   • BSkip CI/CD and continue with the manual release process.
   • CImplement a full CI/CD pipeline with all stages at once, including DAST and deployment automation.
   • DRewrite the entire application to be microservices before implementing CI/CD.
   Reveal Solution Discussion Select an answer first
6. 35expert · hard

   A company's CI/CD pipeline uses a shared build server that runs jobs for multiple teams. The security team discovered that a malicious job from another team could read the environment variables of a different job running on the same server. The team wants to prevent this cross-job secret leakage. What is the most effective solution?

   • AStore secrets in the repository and load them at runtime.
   • BUse a single service account for all jobs to simplify management.
   • CMask all environment variables in the logs.
   • DIsolate each pipeline's jobs in separate containers or virtual machines with no shared filesystem or process namespace.
   Reveal Solution Discussion Select an answer first