Free Practice Questions for the LPI DevOps Tools Engineer 701-100 Exam (2026 Updated)

Combining multiple apt-get commands in one RUN statement avoids the creation of multiple intermediate images, which helps keep the image size smaller and the build process more efficient. Docker creates a new layer for each RUN instruction, so combining commands reduces the number of layers.

References: Docker Documentation - Best Practices for Writing Dockerfiles

In a Dockerfile, the ENTRYPOINT instruction is used to specify the command that will be executed when a container starts. Unlike CMD , which can be overridden by arguments provided in docker run , ENTRYPOINT ensures that the specified command is always run.

References:

Docker Documentation - ENTRYPOINT

A Logstash configuration file is typically divided into three main sections: input, filter, and output. Each section serves a distinct purpose in the data processing pipeline.

input : This section defines where Logstash will collect data from, such as files, syslog, or beats.

filter : This section processes the data collected from inputs. It can include parsing, modification, and enrichment of the data using various filter plugins.

output : This section specifies where the processed data should be sent, such as Elasticsearch, files, or other endpoints.

The other options are incorrect:

D. forward : This is not a standard section in Logstash configuration.

E. generate : This is not a standard section in Logstash configuration.

References:

Logstash Documentation - Configuration

B. When a merge conflict occurs, Git inserts conflict markers into the files to indicate the conflicting sections.

D. The files with conflicts are marked as conflicted in the repository, and you need to manually resolve the conflicts before completing the merge.

References:

Git Documentation - Merge Conflicts

Resolving Merge Conflicts

In Git, several commands are used to manage files within a repository. These include adding, removing, and moving files. The correct commands for managing files as per the options given are:

git rm : This command removes files from the working directory and the index (staging area). This is used to delete files from the repository.

git mv : This command moves or renames files in the working directory and the index. This is essentially a combination of git rm (remove) and git add (add) in one command.

The other options are not valid Git commands:

git cp and git copy : There are no Git commands for copying files directly. File copying is typically done using standard file system commands, and then using git add to track the new files.

git move : This is not a valid Git command; the correct command for moving or renaming files is git mv .

References:

Git Documentation - git rm

Git Documentation - git mv

Vagrant is a tool for building and managing virtual machine environments in a single workflow. It uses a concept called providers to manage the virtual environments. Providers are responsible for creating and managing the virtual machines. Some common providers include VirtualBox, VMware, and AWS.

Providers : Vagrant relies on external hypervisors (providers) to run virtual machines. For example, VirtualBox can be used as a provider, and Vagrant will interact with VirtualBox to create, configure, and manage the virtual machines.

A : There is no vagrant-specific hypervisor called VagrantVM.

B : Vagrant itself does not need to run within a virtual machine not controlled by Vagrant.

C : Vagrant does not ship with an embedded version of VirtualBox; it relies on installed providers.

E : Vagrant does provide mechanisms to run virtual machines using providers.

References:

Vagrant Documentation - Providers

The Logstash grok filter provided is designed to match syslog format messages and extract the IP or hostname of the new node. The pattern used is %{SYSLOGBASE} new node %{IPORHOST:node} .

B. Jun 30 00:36:49 headnode clustermanager[12353]: new node 198.51.100.103 : This message matches the provided grok pattern because it follows the syslog format and contains " new node " followed by an IP address.

The other options do not match the pattern correctly:

A : Contains additional information after the IP address.

C : Does not follow the syslog format required by SYSLOGBASE .

D : Is not in a valid log format.

E : The timestamp and hostname are out of order compared to the expected format.

References:

Elastic Documentation - Grok Filter Plugin

A. The output of git status shows changed files that have not yet been staged for the next commit.

C. It also shows files that have been staged and will be part of the next commit.

E. Additionally, it lists untracked files which are not currently under version control.

References: Git Documentation - git status

The command docker service create --name myweb --network webnet --mode global nginx creates a Docker Swarm service named myweb using the nginx image. The --mode global option specifies that the service should run exactly once on each node in the Swarm cluster.

Global Mode : When a service is created in global mode, Docker Swarm ensures that exactly one instance of the service runs on each node. This is useful for tasks that should run on all nodes, such as monitoring agents.

The other options are incorrect:

A : It does not run exactly one time in the Swarm; it runs once on each node.

C : This describes the replicated mode, not the global mode.

D : The service runs on all nodes, not just those providing the webnet network.

E : There is no network type called global .

References:

Docker Documentation - Service Create

Docker Documentation - Swarm Services

Packer is a tool for creating machine and container images for multiple platforms from a single source configuration. A Packer template consists of various sections, but the builders section is mandatory.

builders : This section defines the builders that Packer will use to create the machine images. It specifies the platform, source image, and configuration required to build the final image.

The other sections are optional but can be included for more complex configurations:

A. images : Not a standard section in Packer templates.

B. provisioners : Optional section used for provisioning the image after it is built.

D. variables : Optional section for defining variables to be used in the template.

E. post-processors : Optional section for defining actions to be taken after the image is built.

References:

Packer Documentation - Template

When a Docker container is started and the Dockerfile contains both COPY and VOLUME instructions as follows:

COPY data/ /data/

VOLUME /data

C. Existing files from /data/ in the image are copied to the new volume : Docker will copy the contents of /data in the image into the volume when the container is started. This ensures that the initial state of the volume includes the files that were copied into /data during the build process.

E. A new volume is created and mounted to /data/ within the new container : Docker creates a new volume if none is specified and mounts it to /data in the container. This volume persists data outside the container ' s lifecycle.

The other options are incorrect:

A : Files in /data/ in the image are made available in the running container via the volume.

B : Changes to files within /data/ do not affect the Docker image; they only affect the volume.

D : Docker does not raise an error when mounting a volume to a directory that already contains data.

References:

Docker Documentation - Managing Data in Containers

The correct answers to the question " Which of the statements below are true about the volume created by the following command? docker run -v /data -ti debian " are:

D. The /data volume can be attached to another Docker container. E. If the command is run a second time, another volume for /data is created.

When you run docker run -v /data -ti debian , Docker creates a volume for /data inside the container. This volume can be managed in the following ways:

Volume Attachment : Volumes are designed to be shared between containers. The volume /data can be attached to other Docker containers, allowing them to read from and write to the same data store.

Multiple Volumes : If you run the command again, Docker will create a new volume for /data , as volumes are specific to the container instance unless explicitly shared.

The other options are incorrect:

A : The new volume does not contain a copy of the complete container ' s base image; it is an empty volume.

B : The volume containing the container’s root filesystem is not retained until the /data volume is deleted.

C : Volumes are persistent and are not discarded when the container terminates unless explicitly removed.

References:

Docker Documentation - Manage Data in Containers

The ansible-vault command is used to manage and store sensitive data in encrypted files within Ansible. This allows users to keep variables, passwords, and other confidential information secure by encrypting them in a file.

References: Ansible Documentation - Ansible Vault

Reference https://www.ibm.com/developerworks/library/mw-1608-tost-trs/index.html

When retrieving a Docker container image from a registry, Docker pulls multiple layers that make up the image. Each layer represents a set of filesystem changes or additions, and these layers are stacked on top of each other to form the complete image.

References: Docker Documentation - Images

A. Microservices architecture allows different services to be developed, deployed, and replaced independently, facilitating the replacement of specific functionalities without impacting the entire system.

D. Due to the network latency and overhead associated with inter-service communication, interaction between microservices can indeed be slower than the interaction of components within a monolithic application.

E. One of the significant advantages of microservices is the ability to update and redeploy individual services independently, which helps in faster iteration and deployment cycles.

References:

Microservices Architecture

Microservices vs Monolithic Architecture