How to Easily Pass the LPI 701-100 Exam: Expert Advice

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.

cloud-config:

--- cloud-config

#!/usr/bin/cloud-init

[cloud-config]

#cloud-config

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.

It runs exactly one time in the Swarm and cannot be scaled.

It runs exactly once on each node in a Swarm.

It runs on one node by default and can be scaled to an arbitrary number of replicas.

It runs on all nodes which provide the network webnet.

It runs only on those nodes which support the network type global.

docker-c00001

2.0.17.172

container

c0023817

clever_ritchie

They accept SSH logins from the user vagrant with the password vagrant.

They accept SSH logins from the user vagrant with a publicly available SSH key pair.

The vagrant user can use sudo to obtain root privileges without additional authentication.

Their whole file system, including configuration files, is writable by any user, including vagrant.

They export their file system via NFS with full write permissions without any additional restrictions.