A team is designing a pipeline for a microservices application with three services: 'auth', 'api', and 'web'. Each service has its own build and test requirements. They want to deploy all services together to a staging environment, but only after all services have passed their tests. They also want to reuse the same build and test logic for each service. Which pipeline design is most efficient and maintainable?

Use a single job that builds and tests all services, and a separate manual job for deployment

Use a single .gitlab-ci.yml with a matrix build (parallel:matrix) to run build and test jobs for each service, followed by a deploy job

Create three separate pipelines, one for each service, each with its own build, test, and deploy stages

Create a single pipeline with one job that builds and tests all three services, then deploys them

A team is creating a pipeline for a Node.js application. They want to run linting, unit tests, and then build a Docker image. The build job should only run if the tests pass. Which pipeline configuration best achieves this?

Define a 'test' stage with lint and test jobs, and a 'build' stage with a Docker build job that depends on the test stage

Define a 'build' stage first, then a 'test' stage, with the test job depending on the build job

Define a single job that runs lint, tests, and builds the Docker image sequentially

Use a pipeline schedule to run the build job, and a separate manual test job

A team is using GitLab Runner with the Docker executor. They have a pipeline that builds a Docker image and then runs tests inside that image. They notice that the test job is failing because it cannot access the Docker daemon. What is the most likely cause and solution?

The test job does not have enough memory; increase the runner's memory limit

The runner is not configured with the correct Docker socket; mount the Docker socket into the job

The Docker image is too large; reduce the image size

The test job is running on the wrong branch; switch to the main branch

What is the primary purpose of the deployment stage in a CI/CD pipeline?

To release the built artifact to a target environment

To store the source code in a repository

To run unit tests against the code

To compile the source code into an executable

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 6)

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

29questions here

6free pages

8concepts

Questions 26–29

26expert · hard
A team is designing a pipeline for a microservices application with three services: 'auth', 'api', and 'web'. Each service has its own build and test requirements. They want to deploy all services together to a staging environment, but only after all services have passed their tests. They also want to reuse the same build and test logic for each service. Which pipeline design is most efficient and maintainable?
Select an answer first
27application · medium
A team is creating a pipeline for a Node.js application. They want to run linting, unit tests, and then build a Docker image. The build job should only run if the tests pass. Which pipeline configuration best achieves this?
Select an answer first
28expert · hard
A team is using GitLab Runner with the Docker executor. They have a pipeline that builds a Docker image and then runs tests inside that image. They notice that the test job is failing because it cannot access the Docker daemon. What is the most likely cause and solution?
Select an answer first
29foundation · easy
What is the primary purpose of the deployment stage in a CI/CD pipeline?
Select an answer first

Finished these 4 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack 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.

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

Questions 26–29

A team is creating a pipeline for a Node.js application. They want to run linting, unit tests, and then build a Docker image. The build job should only run if the tests pass. Which pipeline configuration best achieves this?

A team is using GitLab Runner with the Docker executor. They have a pipeline that builds a Docker image and then runs tests inside that image. They notice that the test job is failing because it cannot access the Docker daemon. What is the most likely cause and solution?

What is the primary purpose of the deployment stage in a CI/CD pipeline?

Keep studying — Domain 2: CI/CD Fundamentals