LPI 701-100 DevOps Tools Engineer Exam Practice Test

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.

latest

default

current

nightly

lts

Executable applications such as .exe files or .jar packages.

Copies of the contents of source code repositories.

Build configuration files such as Makefiles or Maven configurations.

Compiled packages to be installed by a Linux package manager.

Docker container images which contain an application.

Changed files that will not be part of the next commit.

Locked files which cannot be edited until the lock is released.

Changed files that will be part of the next commit.

Unchanged files which have not been edited locally.

Untracked files which are not subject to version control.

Load balancers are a security risk because they obfuscate the origin of connections.

Load balancer help to improve the availability and scalability of a service.

Load balancers are a single point of failure because they cannot be deployed redundantly.

Load balancer require access to private keys in order to be able to forward HTTPS traffic.

Load balancers cannot use connection content, such as HTTP cookies, to route traffic.

{{TargetEnvironment}}

$TargetEnvironment

%TargetEnvironment%

${params.TargetEnvironment}

$ENV{TargetEnvironment}

– rsync:src: example.txtdst: /tmp/example.txt

– copy:src: example.txtdest: /tmp/example.txt

– retrieve:src: example.txtdest: /tmp/example.txt

- cp:source: example.txtdst: /tmp/example.txt

- transfer:src: example.txtdest: /tmp/example.txt