Use this quick start guide to collect all the information about LPI DevOps Tools Engineer (701-200) Certification exam. This study guide provides a list of objectives and resources that will help you prepare for items on the 701-200 LPI DevOps Tools Engineer - 701 exam. The Sample Questions will help you identify the type and difficulty level of the questions and the Practice Exams will make you familiar with the format and environment of an exam. You should refer this guide carefully before attempting your actual LPI DevOps Tools Engineer certification exam.
The LPI DevOps Tools Engineer certification is mainly targeted to those candidates who want to build their career in Open Technology domain. The LPI DevOps Tools Engineer exam verifies that the candidate possesses the fundamental knowledge and proven skills in the area of LPI DevOps Tools Engineer.
LPI DevOps Tools Engineer Exam Summary:
| Exam Name | LPI DevOps Tools Engineer |
| Exam Code | 701-200 |
| Exam Price | $200 (USD) |
| Duration | 90 mins |
| Number of Questions | 60 |
| Passing Score | 500 / 800 |
| Books / Training | DevOps Tools Engineer |
| Schedule Exam | Pearson VUE |
| Sample Questions | LPI DevOps Tools Engineer Sample Questions |
| Practice Exam | LPI 701-200 Certification Practice Exam |
LPI 701-200 Exam Syllabus Topics:
| Topic | Details |
|---|---|
Software Engineering |
|
| Modern Software Development |
Weight: 6
Description: Candidates should be able to design software solutions suitable for modern runtime environments. Candidates should understand how services handle data persistence, sessions, status information, transactions, concurrency, security, performance, availability, scaling, load balancing, messaging, monitoring and APIs. Furthermore, candidates should understand the implications of agile and DevOps on software development. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
| Standard Components and Platforms for Software |
Weight: 3
Description: Candidates should understand services offered by common cloud platforms. They should be able to include these services in their application architectures and deployment toolchains and understand the required service configurations. Furthermore, the candidate should be aware of the commonly used open source implementations of the various services. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
| Source Code Management |
Weight: 6
Description: Candidates should be able to use Git to manage and share source code. This includes creating and contributing to a repository as well as the usage of tags, branches and remote repositories. Furthermore, the candidate should be able to merge files and resolve merging conflicts. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
| Continuous Integration and Continuous Delivery |
Weight: 3
Description: Candidates should understand the principles and components of a continuous integration and continuous delivery pipeline. Candidates should understand how CI/CD pipelines support the development and release of software and how they integrate with source code repositories and the target runtime environment. Furthermore, candidates should be aware of commonly used CI/CD platforms. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
| Software Composition, Licensing and Open Source |
Weight: 2
Description: Candidates should understand the principles of software licenses. This includes how software from multiple authors and sources are combined to implement a specific service and how licensing affects such compositions. Furthermore, the candidate should understand the concepts of open source software, including the most important aspects of common open source licenses. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
Application Container |
|
| Application Container Management |
Weight: 5
Description: Candidates should be able to operate Docker and Podman containers. This includes creating and interacting with containers as well as connecting containers to networks and storage volumes. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
| Container Orchestration |
Weight: 3
Description: Candidates should be able to run and manage multiple containers that work together to provide a service. This includes the orchestration of Docker containers using Docker Compose. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
| Container Image Building |
Weight: 5
Description: Candidates should be able to set up a runtime environment for containers. This includes running containers on a local workstation as well as setting up a dedicated container host. Furthermore, candidates should be aware of other container infrastructures, storage, networking and container specific security aspects. This objective covers the feature set of Docker version 17.06 or later and Docker Machine 0.12 or later. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
Kubernetes |
|
| Kubernetes Architecture and Usage |
Weight: 4
Description: Candidates should understand the major components of Kubernetes. Furthermore, candidates should be able to interact with an existing Kubernetes platform to retrieve information about the current Kubernetes state, and create, modify and delete resources. Key Knowledge Areas:
Partial list of the used files, terms and utilities:
|
| Basic Kubernetes Operations |
Weight: 7
Description: Candidates should be able to set up applications running on Kubernetes. This includes understanding the most important kinds of Kubernetes resources, including their most important properties. Key Knowledge Areas:
Partial list of the used files, terms and utilities:
|
| Kubernetes Package Management |
Weight: 2
Description: Candidates should be able to use Helm to install software on Kubernetes. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
Security and Observability |
|
| Cloud Native Security |
Weight: 4
Description: Candidates should understand the major kinds of IT threats against cloud native infrastructure, as well as common approaches to prevent such attacks and mitigate their risk. This includes handling security aspects of foreign software as well as common standards for authentication and authorization. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
| Prometheus Monitoring |
Weight: 6
Description: Candidates should understand the role of monitoring for application and IT infrastructures. They should be familiar with the architecture and components of Prometheus. The candidate should be able to set up Prometheus and use PromQL to query monitoring data. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
| Log Management and Analysis |
Weight: 2
Description: Candidates should understand the role of log files in operations and troubleshooting. They should be understand the major properties and features of commonly used Open Source logging stacks. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
| Tracing |
Weight: 2
Description: Candidates should understand the concepts and importance of tracing and be familiar with the architecture of OpenTelemetry. Key Knowledge Areas:
The following is a partial list of the used files, terms and utilities:
|
To ensure success in LPI DevOps Tools Engineer certification exam, we recommend authorized training course, practice test and hands-on experience to prepare for LPI DevOps Tools Engineer - 701 (701-200) exam.
