Amazon DOP-C02 - Questions & Answers

Shapshots shared with other users are usable in full by the recipient, including but limited to the ability to base modified volumes and snapshots.

References:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-modifying-snapshotpermissions.html

A security group is tied to a region and can be assigned only to instances in the same region.
You can't enable an instance to communicate with an instance outside its region using security group rules. Traffic from an instance in another region is seen as WAN bandwidth.

References:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/resources.html

Ansible provides a method to only run a task when a condition is met using the `when' declarative. With gather facts enabled, the play has access to the distribution name of the Linux system, thus, tasks can be
tailored to a specific distribution and ran only when the condition is met, e.g.: ` - when: ansible_os_family
== "Debian"'.

References:
http://docs.ansible.com/ansible/playbooks_conditionals.html

We use the variable's name to reference the variable which we encapsulate in curly brackets `{{ }}';
however, the YAML syntax dictates that a string beginning with a curly bracket denotes a dictionary value.
To get around this, it is proper to wrap the variable declaration in quotes.

References:
http://docs.ansible.com/ansible/playbooks_variables.html#hey-wait-a-yaml-gotcha

While all four answers provided are correct, only B is the best choice. Ansible offers the ability to assign variables to groups of hosts in the inventory file. When the playbook is ran it will use the variables assigned to the group, even all the groups are specified in a single playbook run. The respective variables will be available to the play. This is easiest method to run, maintain and write.

References:
http://docs.ansible.com/ansible/intro_inventory.html#group-variables

Variable names can contain letters, numbers and underscores and should always start with a letter. Invalid variable examples, `host first ref', `1st_host_ref''.

References:
http://docs.ansible.com/ansible/playbooks_variables.html#what-makes-a-valid-variable-name

Ansible Playbooks are a series of plays and must contain at a minimum, one play. A play generally consists of hosts to run on, a list of tasks, variables and roles, and any additional instructions, such as connection type, fact gathering, remote username, etc. that the tasks will need to complete. The only requirement for a valid play is to declare the hosts.
References:
http://docs.ansible.com/ansible/playbooks_intro.html

Each task that Ansible runs calls a module. When Ansible uses modules, it copies the module to the remote target system. In the error above it attempted to copy it to the remote user's home directory and found that either the home directory or the `.ansible' directory were not writeable and thus could not
continue.

References:
http://docs.ansible.com/ansible/modules_intro.html

Ansible does not require a client/server architecture and makes all remote connections over SSH. Ansible utilizes the Paramiko Python libraries for SSH when the native system OpenSSH libraries do not meet the requirements.
Also note, Ansible does require Python be installed on the target host. When the target host is Windows, it uses WinRS

References:
http://docs.ansible.com/ansible/intro_getting_started.html#remote-connection-information

Ansible's inventory can only be specified on the command line, the Ansible configuration file or in environment variables.

References:
http://docs.ansible.com/ansible/intro_inventory.html