A development team has a shared runner provided by their GitLab instance. They need to run a job that requires a specific proprietary compiler that is not installed on the shared runner. They want to ensure this job always runs on a runner they control. What should they do?

Register a specific runner for the project and assign it the tag 'compiler'.

Use the shared runner but add the compiler installation to the job's script.

Create a group runner and assign it to the project's group.

Add a tag 'compiler' to the shared runner and use it in the job.

A company wants to use GitLab CI/CD to build and test their application. They have a GitLab instance but no runners. What is the first step they need to take to execute their pipeline jobs?

Enable shared runners in the project settings.

Install and register a GitLab Runner.

Create a .gitlab-ci.yml file with job definitions.

Set up a Kubernetes cluster for the project.

In a .gitlab-ci.yml file, how do you specify that a job should only run on a runner with the tag 'linux'?

By adding `tags: [linux]` to the job definition

By using the `only: [linux]` keyword

By setting `image: linux` in the job

By setting the `runner` keyword to 'linux'

An administrator is registering a new runner for a specific project. They have the registration token from the project's CI/CD settings. During registration, they also want to assign tags to the runner. What should they do?

Set the tags in the GitLab project settings after registration.

Edit the registration token to include the tags.

Provide the tags when prompted during 'gitlab-runner register'.

Add the tags to the project's .gitlab-ci.yml file.

What happens if a job specifies a tag that no runner has?

The job fails immediately with a 'runner not found' error

The job is skipped and marked as successful

The job stays pending until a runner with that tag becomes available

The job runs on any available runner

GitLabCertified Fundamentals Associate

Domain 4Objective 2

Understand the Role of GitLab Runner GITLAB-CERTIFIED-GIT-ASSOCIATE Practice Questions (Page 1)

Part of the Basic CI/CD Pipelines domain, which makes up ~16% of our current practice bank.

27questions here

6free pages

7concepts

Questions 1–5

1application · medium
A development team has a shared runner provided by their GitLab instance. They need to run a job that requires a specific proprietary compiler that is not installed on the shared runner. They want to ensure this job always runs on a runner they control. What should they do?
Select an answer first
2application · medium
A company wants to use GitLab CI/CD to build and test their application. They have a GitLab instance but no runners. What is the first step they need to take to execute their pipeline jobs?
Select an answer first
3foundation · easy
In a .gitlab-ci.yml file, how do you specify that a job should only run on a runner with the tag 'linux'?
Select an answer first
4application · medium
An administrator is registering a new runner for a specific project. They have the registration token from the project's CI/CD settings. During registration, they also want to assign tags to the runner. What should they do?
Select an answer first
5foundation · easy
What happens if a job specifies a tag that no runner has?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-GIT-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-GIT-ASSOCIATE” is a trademark of its owner, used for identification only.