What is a GitLab "Runner"?

An application that executes jobs defined in a pipeline

A command-line tool for local repository debugging

A background service that monitors server performance

A specialized web browser for testing UI components

By default, how do jobs in the same "stage" execute in GitLab?

In parallel as long as there are available runners

Sequentially in the order they are written in YAML

One at a time based on the alphabetical name of the job

Only after the first job in the stage has completed

What does the "stages" keyword define at the top of the YAML file?

The execution order and grouping of pipeline jobs

The permissions levels for different project members

The list of external servers used for job distribution

The version requirements for the GitLab Runner service

What is an "Artifact" in GitLab CI/CD?

A list of files generated by a job to be used later

A snapshot of the Git history used for rollbacks

A deprecated function that is no longer used in code

A temporary log file that is deleted after a job ends

How do you prevent a job from running unless a specific condition is met?

By using the rules: keyword to define logic

By using the condition: block within the job scope

By using the check-if: syntax at the top level

By using the validate: property for shell commands

What is the "Cache" keyword used for?

To persist project dependencies between pipeline runs

To store sensitive API keys and login credentials

To save the final production build for public release

To keep a record of the terminal output for auditing

What is a "Shared Runner"?

A runner available to all projects within an instance

A runner that executes jobs from multiple Git branches

A runner that uses a shared filesystem for every job

A runner designed for collaborative live coding sessions

What does the "image" keyword specify in a job?

The Docker container used for the jobs environment

The metadata tag for identifying the project owner

The graphical icon displayed in the pipeline dashboard

The visual screenshot captured during a failing test

What is the "script" keyword in a job definition?

A list of shell commands executed by the Runner

A plain-text description of what the job performs

A reference to an external JavaScript configuration

A tool for generating automatic project documentation

What are "CI/CD Variables" in GitLab?

Custom environment settings used for configuration

Dynamic counters that track the number of job failures

A list of files that change between different commits

The internal addresses of the GitLab Runner servers

What is a "Pipeline"?

A sequence of jobs organized into different stages

A connection between the database and the web server

A tool for managing the flow of developer communication

A repository used specifically for storing binary files

What is the "allow_failure" keyword used for?

To let a pipeline continue despite a specific job error

To permit the deletion of a branch even if tests fail

To disable the error reporting for a specific project

To automatically restart a job when it crashes

What does "when: manual" do in a job?

It prevents a job from starting without user approval

It requires the Runner to be started by hand on a PC

It forces the job to execute using a local shell executor

It disables all automated triggers for the entire pipeline

What is a "GitLab Runner Executor"?

The environment type where the pipeline job is run

A user role with the permission to cancel running jobs

A security protocol for encrypting data between Runners

A script that cleans up artifacts after a build finishes

What is the "before_script" keyword?

A set of global commands that run before every job

A way to check for syntax errors before the YAML is saved

A tool for managing the order of Git commits in a branch

A script that executes only when a pipeline is cancelled

What is "Environment" management in GitLab CI/CD?

A feature to track and manage software deployment targets

A system for monitoring the hardware health of Runners

A configuration for the physical location of data centers

A method for calculating the carbon footprint of a build

What is a "Downstream Pipeline"?

A pipeline triggered by a parent or external pipeline

A pipeline that has a lower priority in the runner queue

A pipeline used exclusively for deleting old build logs

A pipeline that runs only on local developer machines

What is the purpose of "Tags" in a job definition?

To ensure a job runs on a Runner with specific traits

To assign labels to a Git commit for version release

To organize jobs into searchable categories in the UI

To notify specific team members when a job starts

What does "needs" allow you to do in GitLab CI?

To execute jobs out of stage order based on dependencies

To list the required hardware specs for a job

To specify which users must approve a deployment

To define the external libraries required by the code

What is the "Merge Request Pipeline"?

A pipeline that runs specifically on code in an MR

A tool for combining multiple GitLab user accounts

A system for automatically rewriting code for developers

A way to synchronize different repositories together

What is "GitLab Container Registry"?

A built-in service to store and manage Docker images

A database for storing raw text logs from all jobs

A public forum for sharing open-source code snippets

A tool for managing physical server hardware in a lab

What does "dependencies: []" do in a job?

It stops the job from downloading artifacts from others

It prevents the job from accessing any local Git files

It indicates that the job requires no external software

It disables the network connection for the running job

What is a "Scheduled Pipeline"?

A pipeline set to run at specific intervals using cron

A pipeline that only runs when a developer is offline

A way to predict the completion time of a project

A tool for organizing developer shifts and meetings

What is the "Parallel" keyword used for in a single job?

To run multiple instances of a job for load balancing

To run a job on two different GitLab instances at once

To execute the build and deploy stages at the same time

To allow two developers to edit the same YAML file

What is "Auto DevOps"?

A set of pre-built templates for automated CI/CD

A system for automatically hiring and firing developers

A tool for generating code comments using AI models

A method for driving automated test vehicles in a lab

What is "Variables: GIT_STRATEGY" used for?

To choose between "clone" or "fetch" for repository data

To define the branching model used by the project

To change the default merge behavior of pull requests

To hide the source code from specific Runner instances

What is "Review Apps"?

Dynamic environments for previewing changes in an MR

A mobile application for rating developer performance

A system for peer-reviewing technical documentation

A tool for checking the spelling of Git commit messages

What does "interruptible: true" do?

It lets new pipelines cancel redundant older jobs

It allows the system to pause the build for maintenance

It makes the job stop whenever a developer logs in

It forces the job to wait for manual user intervention

What is the "GitLab-managed Terraform State"?

A secure backend to store Terraform infrastructure data

A list of all physical servers owned by the company

A tool for drawing network diagrams in the GitLab UI

A way to track the geographical location of Runners

Quizzes

GitLab CI/CD: Pipeline Automation Fundamentals

Prev in CI/CDGitHub Actions: Workflow Automation Essentials Next in CI/CDJenkins: CI/CD Automation & Pipeline Management

CI/CD DevOps GitLab Automation

GitLab CI/CD: Pipeline Automation Fundamentals

Mohammad Abu Mattar20 QuestionsIntermediatePublished: 11 Feb, 2026

Welcome to the GitLab CI/CD Basics Quiz! This quiz covers the fundamentals of GitLab CI/CD, including pipelines, jobs, stages, triggers, and best practices. Test your knowledge and see how well you understand this powerful automation tool.

GitLab CI/CD: Pipeline Automation Fundamentals

Test your knowledge up to 20 randomized questions

Quiz Configuration

Enterto start

You might also enjoy

Check out some of our other posts on similar topics

CI/CD: Pipeline Automation Essentials

Welcome to the CI/CD Basics Quiz! This quiz is designed to test your understanding of fundamental continuous integration and continuous delivery concepts, pipeline automation, and modern DevOps best p

#CI/CD #Continuous Integration #Continuous Deployment+6 tags

GitHub Actions: Workflow Automation Essentials

Welcome to the GitHub Actions Basics Quiz! This quiz covers the fundamentals of GitHub Actions, including workflows, jobs, steps, triggers, and best practices. Test your knowledge and see how well you

#GitHub Actions #YAML #Workflows+2 tags

Jenkins: CI/CD Automation & Pipeline Management

Welcome to the Jenkins Basics Quiz! This quiz is designed to test your understanding of fundamental Jenkins concepts, including pipeline as code, Jenkinsfile syntax, agents and stages, build automatio

#Jenkins #CI/CD #Pipeline+6 tags

ArgoCD: GitOps Automation with Kubernetes

Welcome to the ArgoCD Basics Quiz! This quiz is designed to test your understanding of fundamental ArgoCD concepts, GitOps principles, and continuous delivery best practices for Kubernetes. Each quest

#ArgoCD #GitOps #Kubernetes+6 tags

GitOps at Scale: ArgoCD, Flux & Multi-Cluster Deployments

Welcome to the GitOps at Scale Quiz! As organizations grow, managing multiple Kubernetes clusters with GitOps becomes a critical skill. This quiz will test your understanding of how to architect, depl

#Gitops #Argocd #Flux v2+11 tags

Terragrunt: Infrastructure as Code Management

Welcome to the Terragrunt Basics Quiz! This quiz is designed to test your understanding of fundamental Terragrunt concepts, including DRY configuration management, remote state handling, module depend

#Terragrunt #Terraform #IaC+6 tags

6 related posts