LPI DevOps Tools Engineer Exam Summary:
Exam Name | LPI DevOps Tools Engineer |
Exam Code | 701-100 |
Exam Price | $200 (USD) |
Duration | 90 Mins |
Number of Questions | 60 |
Passing Score | 500 / 800 |
Sample Questions | LPI DevOps Tools Engineer Sample Questions |
Practice Exam | LPI 701-100 Certification Practice Exam |
LPI 701-100 Exam Syllabus Topics:
Topic | Details |
Software Engineering | |
Modern Software Development (weight: 6) |
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: ◉ Understand and design service based applications The following is a partial list of the used files, terms and utilities: ◉ REST, JSON |
Standard Components and Platforms for Software (weight: 2) |
Weight: 2 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. OpenStack service components are used as a reference implementation. Key Knowledge Areas: ◉ Features and concepts of object storage The following is a partial list of the used files, terms and utilities: ◉ OpenStack Swift |
Source Code Management (weight: 5) |
Weight: 5 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: ◉ Understand Git concepts and repository structure The following is a partial list of the used files, terms and utilities: ◉ git |
Continuous Integration and Continuous Delivery (weight: 5) |
Weight: 5 Description: Candidates should understand the principles and components of a continuous integration and continuous delivery pipeline. Candidates should be able to implement a CI/CD pipeline using Jenkins, including triggering the CI/CD pipeline, running unit, integration and acceptance tests, packaging software and handling the deployment of tested software artifacts. This objective covers the feature set of Jenkins version 2.0 or later. Key Knowledge Areas: ◉ Understand the concepts of Continuous Integration and Continuous Delivery The following is a partial list of the used files, terms and utilities: ◉ Step, Node, Stage |
Container Management | |
Container Usage (weight: 7) |
Weight: 7 Description: Candidates should be able to build, share and operate Docker containers. This includes creating Dockerfiles, using a Docker registry, creating and interacting with containers as well as connecting containers to networks and storage volumes. This objective covers the feature set of Docker version 17.06 or later. Key Knowledge Areas: ◉ Understand the Docker architecture The following is a partial list of the used files, terms and utilities: ◉ docker |
Container Deployment and Orchestration (weight: 5) |
Weight: 5 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 in conjunction with an existing Docker Swarm cluster as well as using an existing Kubernetes cluster. This objective covers the feature sets of Docker Compose version 1.14 or later, Docker Swarm included in Docker 17.06 or later and Kubernetes 1.6 or later. Key Knowledge Areas: ◉ Understand the application model of Docker Compose The following is a partial list of the used files, terms and utilities: ◉ docker-compose |
Container Infrastructure (weight: 4) |
Weight: 4 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: ◉ Use Docker Machine to setup a Docker host The following is a partial list of the used files, terms and utilities: ◉ docker-machine |
Machine Deployment | |
Virtual Machine Deployment (weight: 4) |
Weight: 4 Description: Candidates should be able to automate the deployment of a virtual machine with an operating system and a specific set of configuration files and software. Key Knowledge Areas: ◉ Understand Vagrant architecture and concepts, including storage and networking The following is a partial list of the used files, terms and utilities: ◉ vagrant |
Cloud Deployment (weight: 2) |
Weight: 2 Description: Candidates should be able to configure IaaS cloud instances and adjust them to match their available hardware resources, specifically, disk space and volumes. Additinally, candidates should be able to configure instances to allow secure SSH logins and prepare the instances to be ready for a configuration management tool such as Ansible. Key Knowledge Areas: ◉ Understanding the features and concepts of cloud-init, including user-data and initializing and configuring cloud-init |
System Image Creation (weight: 2) |
Weight: 2 Description: Candidates should be able to create images for containers, virtual machines and IaaS cloud instances. Key Knowledge Areas: ◉ Understand the functionality and features of Packer The following is a partial list of the used files, terms and utilities: ◉ packer |
Configuration Management | |
Ansible (weight: 8) |
Weight: 8 Description: Candidates should be able to use Ansible to ensure a target server is in a specific state regarding its configuration and installed software. This objective covers the feature set of Ansible version 2.2 or later. Key Knowledge Areas: ◉ Understand the principles of automated system configuration and software installation The following is a partial list of the used files, terms and utilities: ◉ ansible.cfg |
Other Configuration Management Tools (weight: 2) |
Weight: 2 Description: Candidates should understand the main features and principles of important configuration management tools other than Ansible. Key Knowledge Areas: ◉ Basic feature and architecture knowledge of Puppet. The following is a partial list of the used files, terms and utilities: ◉ Manifest, Class, Recipe, Cookbook |
Service Operations | |
IT Operations and Monitoring (weight: 4) |
Weight: 4 Description: Candidates should understand how IT infrastructure is involved in delivering a service. This includes knowledge about the major goals of IT operations, understanding functional and nonfunctional properties of an IT services and ways to monitor and measure them using Prometheus. Furthermore candidates should understand major security risks in IT infrastructure. This objective covers the feature set of Prometheus 1.7 or later. Key Knowledge Areas: ◉ Understand goals of IT operations and service provisioning, including nonfunctional properties such as availability, latency, responsiveness The following is a partial list of the used files, terms and utilities: ◉ Prometheus, Node exporter, Pushgateway, Alertmanager, Grafana |
Log Management and Analysis (weight: 4) |
Weight: 4 Description: Candidates should understand the role of log files in operations and troubleshooting. They should be able to set up centralized logging infrastructure based on Logstash to collect and normalize log data. Furthermore, candidates should understand how Elasticsearch and Kibana help to store and access log data. Key Knowledge Areas: ◉ Understand how application and system logging works The following is a partial list of the used files, terms and utilities: ◉ logstash |
0 comments:
Post a Comment