LPI 701-100 Based on Real Exam Environment

Microservices facilitate the replacement of the implementation of a specific functionality.

Microservices applications are hard to scale because microservice architecture allow only one instance of each microservice.

Integration tests for microservices are not possible until all microservices forming a specific application are completely developed.

Interaction between microservices can be slower that the interaction of similar components within a monolithic application.

Within one application, individual microservices can be updated and redeployed independent of the remaining microservices.

A Puppet Catalog

A Puppet Playbook

A Puppet Factsheet

A Puppet Declaration

A Puppet Manifest

cloud-init provides the cloud-init-worker command which has to be invoked periodically within the running instance.

cloud-init provides systemd units which must be included in several stages of the booting process of the instance.

cloud-init provides its own startup mechanism which replaces the instance’s original init system, such as systemd.

cloud-init provides a Linux kernel module that must be included and loaded in the instance’s initramfs.

cloud-init provides the cloud-init-daemon service which is launched during startup and keeps the instance in sync with the desired configuration.

Vagrant uses a vagrant-specific hypervisor called VagrantVM.

Vagrant has to be run within a running virtual machine which is not controlled by Vagrant.

Vagrant ships with an embedded version of VirtualBox.

Vagrant uses so-called provides which control external hypervisors such as VirtualBox.

Vagrant generates virtual machine images but does not provide a mechanism to run them.