Objective: Identify the Key Components Needed for a CI/CD Pipeline GITLAB-CERTIFIED-CICD-ASSOCIATE Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   A team wants to run a pipeline that deploys a containerized application to a Kubernetes cluster. The pipeline jobs need to authenticate to the cluster. What is the most appropriate way to provide the necessary credentials to the pipeline?

   • AAsk each developer to manually enter the credentials when the pipeline runs
   • BHardcode the Kubernetes credentials in the .gitlab-ci.yml file
   • CStore the credentials as CI/CD variables in the GitLab project settings
   • DCreate a new Kubernetes cluster for each pipeline run
   Reveal Solution Discussion Select an answer first
2. 2application · easy

   A team wants to run a nightly build of their application at 2:00 AM every day, regardless of whether any code changes were pushed. Which GitLab CI/CD feature should they use?

   • AA pipeline schedule configured with a cron expression
   • BA rule that runs the pipeline when a merge request is created
   • CA manual pipeline run from the GitLab UI
   • DA pipeline trigger using a webhook from an external service
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which component of a GitLab CI/CD pipeline groups related jobs that must complete before the next group begins?

   • AScript
   • BRunner
   • CStage
   • DArtifact
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   A company has a pipeline that deploys to a production environment. They want to ensure that only the pipeline can access the production secrets, and that developers cannot view them. They also want to rotate the secrets regularly. Which combination of GitLab features best supports this?

   • AStore secrets in a file in the repository and use a script to decode them
   • BUse a secrets manager like HashiCorp Vault integrated with GitLab, and reference secrets in the production job only
   • CUse the same CI/CD variable for all environments and change it when needed
   • DStore secrets as masked CI/CD variables and rotate them manually every month
   Reveal Solution Discussion Select an answer first
6. 5foundation · easy

   How are dependencies typically managed in a GitLab CI/CD pipeline?

   • ABy using environment variables to define dependency versions
   • BBy using a dependency management tool and caching dependencies between jobs
   • CBy manually copying dependencies to each runner
   • DBy storing all dependencies in the Git repository
   Reveal Solution Discussion Select an answer first