Select Two (Multi-Select) Questions

The inventory source is empty

Why wrong: Job starts but may fail with no hosts.

The user is a system auditor

Why wrong: Auditors can have launch permissions.

The execution environment image tag is 'latest'

Why wrong: Tag 'latest' is acceptable.

Use the debug module with verbosity to output passwords.

Why wrong: Debug exposes sensitive data.

Avoid using become: yes on tasks that access secrets.

Why wrong: Privilege escalation does not directly protect secrets.

Store credentials in plain text in the inventory.

Why wrong: Plain text is not secure.

Set 'stdout_callback = actionable' in ansible.cfg.

Why wrong: This changes callback but does not hide sensitive data.

Use 'name: "Sensitive task"' but keep the task body visible.

Why wrong: The task name does not hide output.

Use 'tags: never' on sensitive tasks.

Why wrong: Tags control task execution, not output visibility.

Use 'strategy: free' to allow hosts to run tasks independently.

Why wrong: The free strategy bypasses the ordered batch control, which can lead to inconsistent states.

Use 'gather_facts: no' to speed up the playbook.

Why wrong: Speeding up does not improve coordination or safety; fact gathering is often needed for conditional logic.

Set 'any_errors_fatal: true' to stop the update on the first failure.

Why wrong: This stops the entire update prematurely, which is not ideal for rolling updates; better to handle failures gracefully.

`system_packages:`

Why wrong: Not a valid directive; system packages are specified under 'dependencies: system:'.

`python_requirements:`

Why wrong: Not a valid directive; Python dependencies are listed under 'dependencies: python:'.

Use ansible-galaxy collection install command in a pre-build script.

Why wrong: Pre-build scripts are not the recommended way; ansible-builder uses the execution-environment.yml definition.

Use a 'galaxy.yml' file in the build context.

Why wrong: galaxy.yml defines a collection's metadata, not how to include it in an EE.

Include collections in the base image directly.

Why wrong: While possible, this is not a standard method and is not recommended for maintainability.

Use the controller UI to export configuration via `dumpconfig`.

Why wrong: There is no built-in dumpconfig feature in the UI.

Execute `awx-manage backup` on the controller node.

Why wrong: `awx-manage` does not have a backup command.

Use `invoke-rc.d automation-controller backup`

Why wrong: This command is not part of AAP management.

`map`

Why wrong: Incorrect; map is a filter.

`select`

Why wrong: Incorrect; select is a filter for lists.

`default`

Why wrong: Incorrect; sets defaults for variables.

`ternary`

Why wrong: Incorrect; used for conditional expressions.

`regex_replace`

Why wrong: Incorrect; used for string replacement, not list manipulation.

Assigning a specific credential to the job template.

Why wrong: Credentials provide authentication, not host limiting.

Using the 'Tags' field to include only certain tasks.

Why wrong: Tags filter tasks, not hosts.

Setting the 'Source Control Branch' in the project.

Why wrong: Branch controls code version, not host selection.

Host variables are the only way to define variables for a host

Why wrong: Host variables can be overridden by group variables or facts.

Groups cannot be members of other groups

Why wrong: Groups can be children of other groups.

Dynamic inventory sources cannot produce groups

Why wrong: Dynamic inventory sources often return group structures.

"fields": [{"id": "password", "type": "string", "label": "Password"}]

Why wrong: Not needed when using SSH key authentication.

"fields": [{"id": "key_type", "type": "string", "label": "Key Type"}]

Why wrong: Unnecessary additional field.

Use inventory host variables to mark hosts for early update and use conditional tasks.

Why wrong: This is possible but not a standard 'rolling out' technique; it's a manual workaround.

Use the --forks=1 option to update one host at a time.

Why wrong: forks controls task parallelism, not host batch ordering.

Use the 'strategy: random' directive in the playbook.

Why wrong: Ansible does not have a 'random' strategy.

Monitor cluster health via `oc get clusterversion` after each node update.

Why wrong: While monitoring is important, it is a verification step, not a practice for minimizing downtime or rollback.

Place nodes in the same Availability Zone to simplify rollback.

Why wrong: Nodes should be distributed across AZs for resilience; this does not simplify rollback.

Use the '--check' command-line option.

Why wrong: --check performs a dry run (no changes) but does not filter tasks.

Use the '--step' command-line option.

Why wrong: --step pauses after each task but does not skip tasks.

Rescue tasks are executed on all hosts in the play.

Why wrong: Rescue runs only on hosts where the block failed.

Blocks cannot be nested.

Why wrong: Blocks can be nested inside other blocks.

A block can have multiple rescue sections.

Why wrong: A block can have at most one rescue section.

rescue

Why wrong: rescue is for block error handling, not per-item loop behavior.

always

Why wrong: always is part of block error handling and runs regardless of task state, not loop-specific.

Defaults are only loaded if no vars are defined.

Why wrong: Defaults are always loaded regardless of other variables.

Defaults have higher priority than variables defined in the playbook.

Why wrong: Playbook variables have higher priority than defaults.

Defaults cannot be overridden.

Why wrong: Defaults are designed to be overridden by variables with higher priority.

Role handlers are shared across all roles in the play.

Why wrong: Handlers are namespaced per role and not automatically shared.

Role variables in vars/main.yml can be overridden by playbook vars.

Why wrong: Role vars have higher priority than playbook vars, so they override playbook vars, not the other way.

Roles can only be used in a playbook's roles section.

Why wrong: Roles can also be invoked using include_role or import_role in tasks.

include_vars

Why wrong: include_vars includes variable files, not task files.

add_host

Why wrong: add_host adds hosts to inventory, not task files.

include_role

Why wrong: include_role includes an entire role, not just task files.