701-100 Sample Questions Answers

Containers decouple the packaging of an application from its infrastructure.

Containers require developers to have detailed knowledge of their IT infrastructure.

Containers let developers test their software under production conditions.

Containers complicate the deployment of software and require early deployment tests.

Containers require application specific adjustment to the container platform.

A Puppet Catalog

A Puppet Playbook

A Puppet Factsheet

A Puppet Declaration

A Puppet Manifest

X-CORS-Access-Token:

Location:

Referer:

Authorization:

Access-Control-Allow-Origin

To prevent the commands from running in parallel because Docker executes all RUN statements in their own container at the same time.

To ensure the execution order of the commands because Docker might evaluate the statements of a Dockerfile in any order.

To avoid the creation of unnecessary images because Docker creates a new image for each RUN statement.

To execute both commands in the same container instance and void Docker to reset the container to the original base image.

To execute the apt-get install command only if the apt-get update command was successful because Docker does not check the success of RUN statements.

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.

Delete all volumes defined in the composer file.

Delete all containers defined in the composer file.

Delete all networks defined in the composer file.

Delete all images used in the composer file from the Docker nodes.

Delete all images built from the composer file from their registry.

Jun 30 00:36:49 headnode: new node 198.51.100.103 at clustermanager:12353

Jun 30 00:36:49 headnode clustermanager[12353]: new node 198.51.100.103

Jun 30 00:36:49 headnode clustermanager[198.51.100.103]: new node

%{SYSLOG-FROM:headnode clustermanager[12353]} new node 198.51.100.103

clustermanager[12353]: Jun 30 00:36:49 headnode new node 198.51.100.103

lineinfile

replace

patch

insert

modify

The syntactical correctness of the source code of a software component.

The formal validity of a service’s external REST API.

The integration of multiple component of the same software.

The correctness of a specific function of a software component.

The throughput, load capacity and latency of a service.

with_nodes

with_playbook

with_sequence

with_items

with_nested

output

filter

input

forward

generate

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.

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.