1500 Questions | Red Hat Certified Engineer (RHCE) 2026

Creating Ansible Plays and Playbooks (Core Weight): * Mastering YAML syntax, variables, loops, conditionals, and handlers.

Using Ansible Modules for System Tasks: * Automating software repositories, package management, services, and firewall rules.

Advanced Automation Features: * Implementing Jinja2 templates, using Ansible Vault for secrets, and managing parallelism.

Roles and Content Collections: * Structuring automation with roles and leveraging Ansible Galaxy and Collections.

Storage and Network Automation: * Configuring LVM, file systems, and network interfaces across multiple managed nodes.

B) Creating a file named datacentre_east inside the group_vars/ directory.

C) Hardcoding the variable into every individual task in the playbook.

D) Adding the variable to the [all:vars] section of the global inventory.

E) Using a shell script to export the variable to the environment.

F) Placing the variable in a file named all.yml inside host_vars/.

Correct Answer: B

Explanation:

B) Correct: Using group_vars/ allows you to manage variables cleanly outside of the main inventory file, making it easier to maintain as the infrastructure grows.

C) Incorrect: This is poor practice (DRY principle violation) and makes updates extremely difficult.

D) Incorrect: This would apply the variable to every host, not just the specific datacentre_east group.

E) Incorrect: Ansible does not automatically source environment variables for playbook execution in this manner.

F) Incorrect: host_vars is for individual host overrides, and all.yml would target every host.

B) It checks the file's timestamp and only runs if the file is older than 24 hours.

C) It uses a regex match to see if the string already exists before attempting an update.

D) It requires the force: yes parameter to be set for every run.

E) It asks the user for confirmation via the CLI before modifying the file.

F) It compares the file size against a pre-calculated MD5 hash.

Correct Answer: C

Explanation:

B) Incorrect: Timestamps are not a reliable indicator of specific content status.

C) Correct: The module is designed to be idempotent; it searches for the line/regex and only makes a change (reporting changed: true) if the line is missing or different.

D) Incorrect: force: yes is often a default or used for overwriting, but isn't the primary logic for line existence.

E) Incorrect: Ansible is an automation tool; it does not stop for manual prompts unless explicitly configured with pause.

F) Incorrect: While hashes are used in the template or copy modules, lineinfile scans the text content specifically.

B) any_errors_fatal: false at the play level.

C) max_fail_percentage: 100% at the play level.

D) force_handlers: yes in the configuration.

E) connection: local to bypass the network check.

F) wait_for: timeout=0.

Correct Answer: B

Explanation:

B) Correct: By default, Ansible continues on remaining hosts if one fails. Setting any_errors_fatal: false (the default behavior) ensures a single node failure doesn't abort the entire automation run.

C) Incorrect: This is a valid keyword but is typically used to stop a play if too many hosts fail, rather than ensuring it continues.

D) Incorrect: Handlers are for service restarts after changes, not for connectivity error handling.

E) Incorrect: This would run the task on the control node, not the managed nodes.

F) Incorrect: This would likely cause the task to fail immediately without solving the connectivity issue.

This is a huge original question bank with 1,500 unique technical scenarios.

You get direct support from me if you get stuck on a logic puzzle.

Each question has a detailed explanation for every option (A through F).

Mobile-compatible with the Udemy app for studying on the go.

30-days money-back guarantee if you're not satisfied.