A team is setting up a new CI/CD pipeline for a Python application. They want the pipeline to run unit tests, package the application into a wheel file, and make that wheel available to a later deployment job. Which pipeline structure best satisfies this requirement?

A single 'deploy' stage that runs tests, builds, and deploys, with no artifact storage

A single job that runs tests, builds the wheel, and deploys it directly to production

A 'build' stage that creates the wheel, and a 'test' stage that runs pytest after the build

Two stages: a 'test' stage with a job that runs pytest, and a 'build' stage with a job that creates the wheel and stores it as an artifact

A team is setting up a pipeline for a Ruby on Rails application. They want to run database migrations, run the test suite, and then build a Docker image. The migrations should run before the tests. Which pipeline structure is most appropriate?

A 'test' stage with a job that runs migrations and tests, and a 'build' stage

A 'prepare' stage with a migration job, a 'test' stage with a test job, and a 'build' stage with a Docker build job

A single job that runs migrations, tests, and builds the Docker image

A 'build' stage first, then a 'test' stage that runs migrations and tests

A company has a pipeline that builds a Java application and deploys it to a staging server for testing, then to production. The deployment to production should only happen after a manual approval. Which pipeline design best meets this requirement?

A 'test' stage that deploys to staging, and a 'build' stage that deploys to production

A single 'deploy' stage with a job that deploys to both staging and production

A single 'deploy' job that runs automatically and deploys to production first, then staging

A 'deploy' stage with a job for staging, and a separate 'production' stage with a job that has a 'when: manual' rule

How can a pipeline be triggered at a specific time without any code changes?

Using a manual job in the pipeline

GitLabCertified CI/CD Associate

Domain 2Objective 1

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

Part of the Domain 2: CI/CD Fundamentals domain, which makes up ~30% of our current practice bank.

29questions here

6free pages

8concepts

Questions 16–20

16application · medium
A team is setting up a new CI/CD pipeline for a Python application. They want the pipeline to run unit tests, package the application into a wheel file, and make that wheel available to a later deployment job. Which pipeline structure best satisfies this requirement?
Select an answer first
17foundation · easy
Which GitLab feature allows a pipeline to be automatically started when a developer pushes a commit to a specific branch?
Select an answer first
18application · medium
A team is setting up a pipeline for a Ruby on Rails application. They want to run database migrations, run the test suite, and then build a Docker image. The migrations should run before the tests. Which pipeline structure is most appropriate?
Select an answer first
19application · medium
A company has a pipeline that builds a Java application and deploys it to a staging server for testing, then to production. The deployment to production should only happen after a manual approval. Which pipeline design best meets this requirement?
Select an answer first
20foundation · easy
How can a pipeline be triggered at a specific time without any code changes?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-CICD-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitLab. “GITLAB-CERTIFIED-CICD-ASSOCIATE” is a trademark of its owner, used for identification only.