Lpi 701-100 Practice Exams
Last updated on Oct 21,2026- Exam Code: 701-100
- Exam Name: Linux Professional Institute DevOps Tools Engineer Exam 701
- Certification Provider: Lpi
- Latest update: Oct 21,2026
You are working in an Agile development team using the Scrum framework. The team is facing difficulties completing sprint goals because requirements keep changing.
What is the BEST way to handle this situation?
- A . Extend sprint durations to accommodate changing requirements
- B . Cancel the sprint and start over with updated requirements
- C . Educate stakeholders about Agile principles and work with them to define a clear Product Backlog
- D . Move incomplete work to the next sprint without informing the Product Owner
C
Explanation:
Agile embraces change, but uncontrolled changes can disrupt sprint goals. The Product Backlog should be well-managed to ensure clear priorities before the sprint starts. Educating stakeholders on Agile principles helps them understand the importance of backlog refinement and sprint commitments. Cancelling sprints (option B) should be a last resort.
A security audit has revealed that sensitive database credentials were accidentally hardcoded into an Ansible playbook.
What is the BEST way to securely manage credentials in future deployments?
- A . Store credentials in plain text but restrict file permissions
- B . Use Ansible Vault to encrypt sensitive variables
- C . Hardcode credentials in an environment variable
- D . Write the credentials into a script and execute it before running Ansible
B
Explanation:
– Ansible Vault allows encrypting sensitive data, ensuring credentials are not exposed in playbooks.
– Option A is incorrect because plain text storage is always a security risk.
– Option C is incorrect because environment variables can be exposed in process lists.
– Option D is incorrect because running an unencrypted script does not secure credentials.
Your development team is using Kubernetes and wants to ensure that database data persists even if a Pod is deleted or restarted.
Which Kubernetes feature should be used?
- A . ConfigMap
- B . EmptyDir
- C . Persistent Volume (PV) with Persistent Volume Claim (PVC)
- D . In-Memory Storage
C
Explanation:
Kubernetes Pods are ephemeral, meaning that when a Pod is restarted, its local storage is lost. To persist data, Persistent Volumes (PVs) and Persistent Volume Claims (PVCs) should be used.
– Solution: Create a Persistent Volume Claim:
– apiVersion: v1
– kind: PersistentVolumeClaim
– metadata:
– name: my-pvc
– spec:
– accessModes:
– – ReadWriteOnce
– resources:
– requests:
– storage: 1Gi
– Why this works:
o PVs provide long-term storage that is independent of Pods.
o Even if a Pod is deleted, data is retained and can be re-attached to a new Pod.
A system administrator wants to configure multiple servers using Puppet.
What is the role of the Puppet Master?
- A . It runs configurations directly on each node
- B . It generates and distributes configuration catalogs to Puppet agents
- C . It stores passwords for managed servers
- D . It replaces Ansible’s functionality
B
Explanation:
– The Puppet Master is the central server that compiles configuration catalogs and sends them to Puppet agents.
– Option A is incorrect because Puppet Master does not directly run configurations.
– Option C is incorrect because Puppet does not store passwords.
– Option D is incorrect because Puppet and Ansible have different architectures.
What is the key difference between Continuous Delivery and Continuous Deployment?
- A . Continuous Delivery automates testing, while Continuous Deployment does not
- B . Continuous Deployment requires manual approval for release, while Continuous Delivery does not
- C . Continuous Delivery ensures software is always ready for deployment, but Continuous Deployment automatically deploys it
- D . Continuous Deployment only applies to on-premise infrastructure
C
Explanation:
Continuous Delivery (CD) ensures that code is always in a deployable state but requires manual approval for release. Continuous Deployment (CD) goes one step further by automatically deploying the software to production.
Your company uses Prometheus and Grafana to monitor server health. The CPU usage on one of the production servers suddenly spikes to 100%. You need to quickly identify which process is consuming the most CPU.
What is the BEST command to use?
- A . iostat -x 1
- B . top
- C . netstat -tulnp
- D . vmstat 1
B
Explanation:
– top provides a real-time view of CPU usage, showing which processes consume the most resources.
– Option A (iostat -x 1) is incorrect because it monitors disk I/O, not CPU usage.
– Option C (netstat -tulnp) is incorrect because it displays network connections, not CPU processes.
– Option D (vmstat 1) is incorrect because it gives general CPU statistics but does not show which processes are causing high CPU load.
You are responsible for deploying an application using Docker. The application runs in a container, but each time the container stops, all the stored data is lost.
How can you ensure that the application’s data persists even after the container is restarted?
- A . Use the –restart=always flag when running the container
- B . Use a Docker Volume to store data persistently
- C . Use the –privileged flag to keep the container running
- D . Store data inside the container’s root filesystem
B
Explanation:
Containers are stateless by default, meaning all data inside the container is lost when the container stops or is deleted.
– Docker Volumes provide persistent storage, ensuring that data is stored outside the container’s lifecycle.
– The correct approach is to use the -v or –mount option to attach a volume.
Example:
docker volume create mydata
docker run -d -v mydata:/app/data mycontainer
– This ensures that data inside /app/data persists across restarts.
A Kubernetes administrator wants to define a Persistent Volume (PV) in a cluster.
Which of the following configurations is required?
- A . apiVersion: v1, kind: PersistentVolume, and spec.capacity.storage
- B . apiVersion: v1, kind: Service, and spec.ports
- C . apiVersion: apps/v1, kind: Deployment, and spec.template
- D . apiVersion: networking.k8s.io/v1, kind: Ingress, and spec.rules
A
Explanation:
A Persistent Volume (PV) in Kubernetes requires apiVersion: v1, kind: PersistentVolume, and spec.capacity.storage, which defines the amount of storage allocated.
A development team is using Docker for containerized applications. They notice that application builds take longer due to dependencies being downloaded repeatedly.
What is the BEST way to optimize Docker build times?
- A . Use a multi-stage build and cache dependencies properly
- B . Remove all unused dependencies from the application
- C . Always build the image from scratch using –no-cache
- D . Use a single-layer Dockerfile to reduce build complexity
A
Explanation:
Docker builds can be optimized by leveraging multi-stage builds, where dependencies are installed in an intermediate stage and copied to the final image. Proper layer caching ensures that unchanged dependencies do not need to be re-downloaded on every build. Using –no-cache (option C) would increase build times instead of optimizing them.
A DevOps engineer needs to deploy identical infrastructure across multiple cloud environments (AWS, Azure, and GCP). The solution must be scalable, automated, and maintainable.
What is the BEST tool to use?
- A . AWS CloudFormation
- B . Ansible
- C . Terraform
- D . Bash scripting
C
Explanation:
Terraform is a multi-cloud Infrastructure as Code (IaC) tool that allows defining infrastructure using code and deploying it across AWS, Azure, and GCP.
CloudFormation (Option A) is AWS-specific.
Ansible (Option B) is mainly for configuration management, not infrastructure provisioning.
Bash scripting (Option D) lacks scalability and maintainability for large cloud environments.