1.What is the purpose of the docker:dind image in GitLab CI
-
A. It is used to install Docker CLI tools.
-
B. It provides a Docker daemon inside a container so jobs can run Docker commands.
-
C. It is a base image for building frontend applications.
-
D. It disables Docker TLS by default.
It provides a Docker daemon inside a container so jobs can run Docker commands.
It provides a Docker daemon inside a container so jobs can run Docker commands.
2.In a GitLab CI job using Docker-in-Docker, which variable is used to disable TLS?
-
A. DISABLE_TLS
-
B. DOCKER_TLS_DISABLE
-
C. DOCKER_TLS_CERTDIR
-
D. DOCKER_TLS_SKIP
DOCKER_TLS_CERTDIR
DOCKER_TLS_CERTDIR
3.What must be set to true in a self-hosted GitLab Runner to enable Docker-in-Docker?
-
A. docker_enable = true
-
B. privileged = true
-
C. tls_disable = true
-
D. image_pull_policy = always
privileged = true
privileged = true
4.If a Docker image is not found locally on the GitLab Runner host, what happens?
-
A. The job fails immediately.
-
B. The image is automatically built from Dockerfile.
-
C. GitLab pulls the image from Docker Hub.
-
D. GitLab uses a default image stored in the repository.
GitLab pulls the image from Docker Hub.
GitLab pulls the image from Docker Hub.
5.After a CI job using Docker completes, what happens to the Docker image used?
-
A. The image is always deleted.
-
B. The container and the image are both deleted.
-
C. Only the container is deleted; the image remains cached.
-
D. The image is stored in GitLab Registry.
Only the container is deleted; the image remains cached.
Only the container is deleted; the image remains cached.