EX294 Practice Test 10 — 10 Questions

Question 1

Refer to the exhibit. After the playbook run fails on the 'Verify config' task, what happens to the 'restart service' handler?

Accepted Answer

The handler is not executed because the playbook failed before the end of the play.. Handlers are notified but only run at the end of the play if notified. However, if a subsequent task fails, the playbook stops, and handlers are not executed unless the 'force_handlers' option is set.

Answer

The handler runs immediately after the failed task.

Answer

The handler runs on the next playbook run.

Answer

The handler is executed because it was notified before the failure.

Question 2

A company uses a static inventory file for Ansible Tower. They need to add a new host to an existing group. Which action should they take?

Accepted Answer

Edit the inventory in the Tower UI and add the host to the group.. The company uses a static inventory file for Ansible Tower, and the Tower UI provides a built-in interface to manage static inventories. Editing the inventory in the Tower UI and adding the host to the group directly updates the underlying static inventory file and synchronizes it with Tower's database, ensuring the host is available for job runs without manual file manipulation.

Answer

Use the ansible-inventory command to add the host.

Answer

Modify the static inventory file and run a job template.

Answer

Create a new inventory and host group.

Question 3

Ansible Tower is configured with a dynamic inventory source from VMware vCenter. The playbook needs to limit execution to hosts with a specific custom attribute. How should this be achieved?

Accepted Answer

Use a smart inventory filter.. Smart inventories in Ansible Tower allow you to apply a filter (using Jinja2-style syntax) against an existing inventory source, such as a dynamic VMware vCenter source, to limit execution to hosts matching specific criteria like a custom attribute. This approach avoids modifying the source script or creating duplicate inventory sources, preserving the dynamic nature of the inventory while enabling targeted host selection.

Answer

Modify the VMware inventory script to filter hosts.

Answer

Add the required hosts manually.

Answer

Create a new inventory source with a filter.

Question 4

The deployment has 4 replicas. During a rolling update, what is the maximum number of pods that can be unavailable at any single time?

Accepted Answer

1. The default rolling update strategy for a Deployment in Kubernetes sets `maxUnavailable` to 25% of the desired replicas, rounded up. With 4 replicas, 25% equals 1, so at most 1 pod can be unavailable during the update. This ensures minimal disruption while allowing the update to proceed.

Answer

2

Answer

4

Answer

0

Answer

3

Question 5

Which THREE commands can verify the status of a rolling update on an OpenShift deployment?

Accepted Answer

oc describe deployment/. `oc describe deployment/` provides detailed information about the deployment, including the current rollout status, revision history, and conditions such as Progressing or Available. This allows you to verify whether a rolling update is in progress, has completed, or has stalled by examining fields like `Replicas`, `UpdatedReplicas`, and `Conditions`.

Answer

oc logs deployment/<name>

Answer

oc get pods -l <selector>

Question 6

An Ansible role has multiple dependencies defined in meta/main.yml. One of the dependent roles should be executed before the role's own tasks, but only if a certain condition is met. How can this be implemented?

Accepted Answer

The dependency cannot be conditional; use 'include_role' with 'when' in the tasks.. Ansible role dependencies defined in meta/main.yml do not support conditional execution; the 'dependencies' field only accepts role names or a dictionary with 'role' and optional 'vars'. To conditionally execute a role, you must use 'include_role' with a 'when' clause in the playbook or tasks, not in the metadata. This is by design because dependency resolution happens at playbook parsing time, not at runtime.

Answer

Use 'condition' field in the dependencies list.

Answer

Use 'when' condition in the role's tasks to include the dependency.

Answer

Use 'pre_tasks' in the playbook to run the conditional dependency.

Question 7

A team uses a single Ansible Tower inventory called 'Production' containing hosts for multiple environments (dev, stage, prod). They want to apply different variables to hosts based on environment. Which inventory structure meets this requirement with minimal administrative overhead?

Accepted Answer

Create groups within the inventory for each environment (e.g., 'dev', 'stage', 'prod') and assign variables at the group level.. Ansible Tower (now Red Hat Ansible Automation Platform) supports group-based variable inheritance within a single inventory. By creating groups for each environment (dev, stage, prod) and assigning variables at the group level, you can apply environment-specific variables to all hosts in that group with minimal administrative overhead. This leverages Tower's built-in group variable mechanism without requiring per-host edits or multiple inventory objects.

Answer

Assign variables directly to each host using the 'Host Variables' field in the inventory.

Answer

Add tags to each host and use the tags to filter variables in the job template.

Answer

Create separate inventories for each environment and link them to the same project.

Question 8

Which TWO Ansible playbook parameters directly control the number of host failures allowed before aborting a rolling update?

Accepted Answer

max_fail_percentage. `max_fail_percentage` directly specifies the maximum percentage of hosts that can fail during a rolling update before Ansible aborts the entire batch. Option B is correct because `any_errors_fatal` causes the playbook to stop immediately if any host in the current batch fails, effectively limiting failures to zero before aborting the rolling update.

Answer

throttle

Answer

serial

Answer

ignore_errors

Question 9

Which TWO of the following statements about Ansible roles are correct?

Accepted Answer

Variables in 'defaults/main.yml' have the lowest precedence and can be overridden by inventory variables.. Variables in defaults/main.yml have the lowest precedence and can be overridden by inventory variables. Role dependencies are defined in meta/main.yml. The other options are incorrect: pre_tasks run before roles, include_role is dynamic, and the naming convention is not mandatory.

Answer

Role names must be prefixed with 'ansible-role-' when published to Ansible Galaxy.

Answer

The 'include_role' module can only be used for static imports.

Answer

A role's tasks are executed before any 'pre_tasks' defined in the playbook.

Question 10

A team has been using Ansible Automation Controller for six months. They have a job template that runs a playbook against a static inventory. Recently, the job template started hanging indefinitely after launching. The admin checks the job output and sees: `PLAY [all] ************************` with no further output. The playbook uses `delegate_to: localhost` for some tasks. The admin executed the same playbook manually with `ansible-playbook` on the control node and it completes successfully. The controller logs show no errors. What is the most likely cause of the hang in the controller?

Accepted Answer

The execution environment used by the job template has no route to the controller's IP address on port 22.. In Ansible Automation Controller, tasks with delegate_to: localhost are executed on the controller node. The execution environment (container) typically connects to the controller's IP via SSH (port 22) to run these tasks. If the execution environment has no network route to the controller's IP on port 22, the connection times out, causing the job to hang. The manual ansible-playbook run works because it runs directly on the control node, where localhost is local and no SSH is needed. Option A is wrong because the play begins, indicating initial SSH connections succeed. Option C is wrong because the manual run succeeded, ruling out syntax errors. Option D is wrong because delegate_to localhost does not require the control node to be in the inventory.

Answer

The machine credential for the job template does not include the SSH key for the control node.

Answer

The playbook has a syntax error that only manifests when run as a job template.

Answer

The inventory for the job template does not include the control node host.