Manage task execution and roles →mediumMultiple ChoiceObjective-mapped

EX294 Manage task execution and roles Practice Question

Exhibit

Refer to the exhibit.

```yaml
---
- hosts: all
  tasks:
    - name: Create user
      ansible.builtin.user:
        name: jdoe
        state: present
      register: user_result

    - name: Show user info
      ansible.builtin.debug:
        var: user_result
```

Refer to the exhibit. The playbook runs successfully. What will the debug task output?

⚠ Common exam trap

Red Hat often tests the misconception that the debug task outputs a simple success message or a single value, when in fact it outputs the full return dictionary from the module.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

A dictionary with details about the user, such as uid, gid, and groups.

The debug task outputs the registered variable from the user module. By default, the user module returns a dictionary containing user account details such as uid, gid, groups, and home directory when the state is 'present'. Since the playbook runs successfully, the registered variable holds this dictionary, making option B correct.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Just the username 'jdoe'.
Why it's wrong here
The variable contains more than just the name.
✓
A dictionary with details about the user, such as uid, gid, and groups.
Why this is correct
The user module returns a dictionary with user attributes.
✗
The entire playbook YAML structure.
Why it's wrong here
debug with var only prints the value of that variable.
✗
The string 'true' if the user was created successfully.
Why it's wrong here
The debug module outputs the variable content, not a simple boolean.

Go deeper

EX294 Manage task execution and roles Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question