Free EX374 sample questions

Correct answer: Configure Step A with a success transition to Step B and a failure transition to Step C. Configure both Step B and Step C with an 'Always' transition to Step D.

In Ansible Automation Controller workflows, transitions determine the flow based on the result of the previous node. An 'Always' transition ensures that the target node executes regardless of the source node's status (success or failure). By linking both the success path (Step B) and failure path (Step C) to Step D with 'Always', you guarantee the notification runs in both scenarios. graph TD A[Step A: Check Load] -->|Success| B[Step B: Patch] A -->|Failure| C[Step C: Ticket] B -->|Always| D[Step D: Notify] C -->|Always| D

Correct answer: Create `bindep.txt` for OS packages and reference it under `dependencies.system` in the definition file.

Ansible Builder uses `bindep.txt` to define system-level (RPM/Deb) dependencies. In the `execution-environment.yml` definition file, this is referenced under the `dependencies` section using the `system` key. Python dependencies go in `requirements.txt` referenced by the `python` key.

Correct answer: Use a `lookup` plugin within a `template` or `copy` module's `content` parameter. The task itself runs on the remote host, but the lookup executes locally on the controller.

Lookup plugins in Ansible ALWAYS execute on the control node (localhost). By using a lookup to fetch data (e.g., `lookup('community.general.postgresql_query', ...)`), the data is retrieved locally. You can then use the `copy` module with the `content` parameter (populated by the lookup) to write the file on the remote host. No `delegate_to` is needed for the task itself because the file write action must happen on the target.

Correct answer: keyed_groups: - key: tags.Environment prefix: env

The `keyed_groups` option allows you to create groups based on the values of variables (in this case, tags). By specifying `key: tags.Environment`, the plugin will create groups like `env_production` or `env_staging`. If the key does not exist for a host, that host is simply not added to a keyed group (effectively remaining in `ungrouped` or `all` depending on context), satisfying the requirement.

Correct answer: The repository will be cloned if it does not exist. If it exists, no changes will be pulled from the remote, even if the remote branch has updates.

When `update: no` is set, the git module checks if the destination directory contains a git repository. If it does, the module stops and does not pull new changes. It only clones the repository if the destination is empty/missing. This is useful for 'clone once' scenarios.

Correct answer: {{ interfaces | selectattr('active', 'equalto', true) | selectattr('speed', 'gt', 500) | map(attribute='name') | list }}

This chain correctly filters the list first by the 'active' attribute (must be true), then filters that result by the 'speed' attribute (must be greater than 500), and finally maps the result to extract only the 'name' attribute.