Updated RedHat EX294 Exam Dumps – No More Outdated Material

Question No: 1

MultipleChoice

Use Ansible Galaxy with a requirements file called /home/admin/ansible/roles/

install.yml to download and install roles to /home/admin/ansible/roles from the

following URLs:

http:// classroom.example.com /role1.tar.gz The name of this role should be balancer

http:// classroom.example.com /role2.tar.gz The name of this role should be phphello

Options

AExplanation:
Solution as:
# pwd
/home/admin/ansible/roles
# vim install.yml
---
- src: http://classroom.example.com/role1.tar.gz
name: balancer
- src: http://classroom.example.com/role2.tar.gz
name: phphello
:wq!
# pwd
/home/admin/ansible
# ansible-galaxy install -r roles/install.yml -p roles

Question No: 2

MultipleChoice

In /home/sandy/ansible/ create a playbook called logvol.yml. In the play create a logical volume called Iv0 and make it of size 1500MiB on volume group vgO If there is not enough space in the volume group print a message "Not enough space for logical volume" and then make a 800MiB Iv0 instead. If the volume group still doesn't exist, create a message "Volume group doesn't exist" Create an xfs filesystem on all Iv0 logical volumes. Don't mount the logical volume.

Options

AExplanation:
Solution as:

Question No: 3

MultipleChoice

Create a file called specs.empty in home/bob/ansible on the local machine as follows:

HOST=

MEMORY=

BIOS=

VDA_DISK_SIZE=

VDB_DISK_SIZE=

Create the playbook /home/bob/ansible/specs.yml which copies specs.empty to all remote nodes' path /root/specs.txt. Using the specs.yml playbook then edit specs.txt on the remote machines to reflect the appropriate ansible facts.

Options

AExplanation:
Solution as:

Question No: 4

MultipleChoice

Create a playbook called web.yml as follows:

* The playbook runs on managed nodes in the "dev" host group

* Create the directory /webdev with the following requirements:

--> membership in the apache group

--> regular permissions: owner=r+w+execute, group=r+w+execute, other=r+execute

s.p=set group-id

* Symbolically link /var/www/html/webdev to /webdev

* Create the file /webdev/index.html with a single line of text that reads:

''Development''

--> it should be available on http://servera.lab.example.com/webdev/index.html

Options

AExplanation:
Solution as:
# pwd
/home/admin/ansible/
# vim web.yml
---
- name:
hosts: dev
tasks:
- name: create group
yum:
name: httpd
state: latest
- name: create group
group:
name: apache
state: present
- name: creating directiory
file:
path: /webdev
state: directory
mode: '2775'
group: apache
- sefcontext:
target: '/webdev/index.html'
setype: httpd_sys_content_t
state: present
- name: Apply new SELinux file context to filesystem
command: restorecon -irv
- name: creating symbolic link
file:
src: /webdev
dest: /var/www/html/webdev
state: link
force: yes
- name: creating file
file:
path: /webdev/index.html
sate: touch
- name: Adding content to index.html file
copy:
dest: /webdev/index.html
content: 'Development'
- name: add service to the firewall
firewalld:
service: http
permanent: yes
state: enabled
immediate: yes
- name: active http service
service:
name: httpd
state: restarted
enabled: yes
:wq
# ansible-playbook web.yml ---syntax-check
# ansible-playbook web.yml

Question No: 5

MultipleChoice

Create an ansible vault password file called lock.yml with the password reallysafepw in the /home/sandy/ansible directory. In the lock.yml file define two variables. One is pw_dev and the password is 'dev' and the other is pw_mgr and the password is 'mgr' Create a regular file called secret.txt which contains the password for lock.yml.

Options

AExplanation:
ansible-vault create lock.yml
New Vault Password: reallysafepw
Confirm: reallysafepw

Question No: 6

MultipleChoice

Create a file called requirements.yml in /home/sandy/ansible/roles a file called role.yml in /home/sandy/ansible/. The haproxy-role should be used on the proxy host. And when you curl http://node3.example.com it should display "Welcome to node4.example.com" and when you curl again "Welcome to node5.example.com" The php-role should be used on the prod host.

Options

AExplanation:
Solution as:

Check the proxy host by curl http://node3.example.com

Question No: 7

MultipleChoice

Rekey an existing Ansible vault as follows:

-----------------------------------------------

* Download Ansible vault from http:// classroom.example.com /secret.yml to /home/

admin/ansible/

* The current vault password is curabete

* The new vault password is newvare

* The vault remains in an encrypted state with the new password

Options

AExplanation:
Solution as:
# pwd
/home/admin/ansible/
# wget http://classroom.example.com/secret.yml
# chmod 0600 newpassword.txt
# ansible-vault rekey vault.yml --new-vault-password-file=newpassword.txt

Question No: 8

MultipleChoice

Create user accounts

------------------------

--> A list of users to be created can be found in the file called user_list.yml

save to /home/admin/ansible/

--> Using the password vault created elsewhere in this exam, create a playbook called

create_user.yml

that creates user accounts as follows:

--> Users with a job description of developer should be:

--> created on managed nodes in the 'dev' and 'test' host groups assigned the

password from the 'dev_pass'

variable and these user should be member of supplementary group 'devops'.

--> Users with a job description of manager should be:

--> created on managed nodes in the 'prod' host group assigned the password from

the 'mgr_pass' variable

and these user should be member of supplementary group 'opsmgr'

--> Passwords should use the 'SHA512' hash format. Your playbook should work using

the vault password file

created elsewhere in this exam.

while practising you to create these file hear. But in exam have to download as per

questation.

user_list.yml file consist:

---

user:

- name: user1

job: developer

- name: user2

job: manager

Options

AExplanation:
Solution as:
# pwd
/home/admin/ansible
# wget http://classroom.example.com/user_list.yml
# cat user_list.yml
# vim create_user.yml
---
- name:
hosts: all
vars_files:
- ./user_list.yml
- ./vault.yml
tasks:
- name: creating groups
group:
name: '{{ item }}'
state: present
loop:
- devops
- opsmgr
- name: creating user
user:
name: '{{ item.name }}'
state: present
groups: devops
password: '{{ dev_pass|password_hash ('sha512') }}'
loop: '{{ user }}'
when: (inventory_hostname in groups['dev'] or inventory_hostname in
groups['test']) and item.job == 'developer'
- name: creating user
user:
name: '{{ item.name }}'
state: present
groups: opsmgr
password: '{{ mgr_pass|password_hash ('sha512') }}'
loop: '{{ user }}'
when: inventory_hostname in groups['prod'] and item.job == 'manager'
:wq!
# ansible-playbook create_user.yml ---vault-password-file=password.txt ---syntax-check
# ansible-playbook create_user.yml ---vault-password-file=password.txt

Question No: 9

MultipleChoice

Install and configure ansible

User sandy has been created on your control node with the appropriate permissions already, do not change or modify ssh keys. Install the necessary packages to run ansible on the control node. Configure ansible.cfg to be in folder /home/sandy/ansible/ansible.cfg and configure to access remote machines via the sandy user. All roles should be in the path /home/sandy/ansible/roles. The inventory path should be in /home/sandy/ansible/invenlory.

You will have access to 5 nodes.

node3.example.com

Configure these nodes to be in an inventory file where node I is a member of group dev. nodc2 is a member of group test, node3 is a member of group proxy, nodc4 and node 5 are members of group prod. Also, prod is a member of group webservers.

Options

AExplanation:
In/home/sandy/ansible/ansible.cfg
[defaults]
inventory=/home/sandy/ansible/inventory
roles_path=/home/sandy/ansible/roles
remote_user= sandy
host_key_checking=false
[privilegeescalation]
become=true
become_user=root
become_method=sudo
become_ask_pass=false
In /home/sandy/ansible/inventory
[dev]
node 1 .example.com
[test]
node2.example.com
[proxy]
node3 .example.com
[prod]
node4.example.com
node5 .example.com
[webservers:children]
prod

Question No: 10

MultipleChoice

Install and configure ansible

User bob has been created on your control node. Give him the appropriate permissions on the control node. Install the necessary packages to run ansible on the control node.

Create a configuration file /home/bob/ansible/ansible.cfg to meet the following requirements:

* The roles path should include /home/bob/ansible/roles, as well as any other path that may be required for the course of the sample exam.

* The inventory file path is /home/bob/ansible/inventory.

* Ansible should be able to manage 10 hosts at a single time.

* Ansible should connect to all managed nodes using the bob user.

Create an inventory file for the following five nodes:

Configure these nodes to be in an inventory file where node1 is a member of group dev. nodc2 is a member of group test, nodc3 is a member of group proxy, nodc4 and node 5 are members of group prod. Also, prod is a member of group webservers.

Options

AExplanation:
In/home/sandy/ansible/ansible.cfg
[defaults]
inventory=/home/sandy/ansible/inventory
roles_path=/home/sandy/ansible/roles
remote_user= sandy
host_key_checking=false
[privilegeescalation]
become=true
become_user=root
become_method=sudo
become_ask_pass=false
In /home/sandy/ansible/inventory
[dev]
node 1 .example.com
[test]
node2.example.com
[proxy]
node3 .example.com
[prod]
node4.example.com
node5 .example.com
[webservers:children]
prod

Question No: 11

MultipleChoice

Create a playbook called hwreport.yml that produces an output file called /root/

hwreport.txt on all managed nodes with the following information:

------------------------------------------------------------------------------------------------------

--> Inventory host name

--> Total memory in MB

--> BIOS version

--> Size of disk device vda

--> Size of disk device vdb

Each line of the output file contains a single key-value pair.

* Your playbook should:

hwreport.empty and

save it as /root/hwreport.txt

--> Modify with the correct values.

note: If a hardware item does not exist, the associated value should be set to NONE

----------------------------------------------------------------------------------------------

while practising you to create these file hear. But in exam have to download as per

questation.

hwreport.txt file consists.

my_sys=hostname

my_BIOS=biosversion

my_MEMORY=memory

my_vda=vdasize

my_vdb=vdbsize

Options

AExplanation:
Solution as:
# pwd
/home/admin/ansible
# vim hwreport.yml
- name:
hosts: all
ignore_errors: yes
tasks:
- name: download file
get_url:
url: http://classroom.example.com/content/ex407/hwreport.empty
dest: /root/hwreport.txt
- name: vdasize
replace:
regexp: 'vdasize'
replace: '{{ ansible_facts.devices.vda.size }}'
dest: /root/hwreport.txt
register: op1
- debug:
var: op1
- name: none
replace:
regexp: 'vdasize'
replace: NONE
dest: /root/hwreport.txt
when:
op1.failed == true
- name: vdbsize
replace:
regexp: 'vdbsize'
replace: '{{ ansible_facts.devices.vdb.size }}'
dest: /root/hwreport.txt
register: op2
- debug:
var: op2
- name: none
replace:
regexp: 'vdbsize'
replace: NONE
dest: /root/hwreport.txt
when:
op2.failed == true
- name: sysinfo
replace:
regexp: '{{item.src}}'
replace: '{{item.dest}}'
dest: /root/hwreport.txt
loop:
- src: 'hostname'
dest: '{{ ansible_facts.fqdn }}'
- src: 'biosversion'
dest: '{{ ansible_facts.bios_version }}'
- src: 'memory'
dest: '{{ ansible_facts.memtotal_mb }}'
:wq!
# ansible-playbook hwreport.yml ---syntax-check
# ansible-playbook hwreport.yml

Question No: 12

MultipleChoice

Create a playbook called web.yml as follows:

* The playbook runs on managed nodes in the 'dev' host group

* Create the directory /webdev with the following requirements:

--> membership in the apache group

--> regular permissions: owner=r+w+execute, group=r+w+execute, other=r+execute

s.p=set group-id

* Symbolically link /var/www/html/webdev to /webdev

* Create the file /webdev/index.html with a single line of text that reads:

''Development''

Options

AExplanation:
Solution as:
# pwd
/home/admin/ansible/
# vim web.yml
---
- name:
hosts: dev
tasks:
- name: create group
yum:
name: httpd
state: latest
- name: create group
group:
name: apache
state: present
- name: creating directiory
file:
path: /webdev
state: directory
mode: '2775'
group: apache
- sefcontext:
target: '/webdev/index.html'
setype: httpd_sys_content_t
state: present
- name: Apply new SELinux file context to filesystem
command: restorecon -irv
- name: creating symbolic link
file:
src: /webdev
dest: /var/www/html/webdev
state: link
force: yes
- name: creating file
file:
path: /webdev/index.html
sate: touch
- name: Adding content to index.html file
copy:
dest: /webdev/index.html
content: 'Development'
- name: add service to the firewall
firewalld:
service: http
permanent: yes
state: enabled
immediate: yes
- name: active http service
service:
name: httpd
state: restarted
enabled: yes
:wq
# ansible-playbook web.yml ---syntax-check
# ansible-playbook web.yml

Question No: 13

MultipleChoice

Create a playbook called balance.yml as follows:

* The playbook contains a play that runs on hosts in balancers host group and uses

the balancer role.

--> This role configures a service to loadbalance webserver requests between hosts

in the webservers host group.curl

--> When implemented, browsing to hosts in the balancers host group (for example

Welcome to node3.example.com on 192.168.10.z

--> Reloading the browser should return output from the alternate web server:

Welcome to node4.example.com on 192.168.10.a

* The playbook contains a play that runs on hosts in webservers host group and uses

the phphello role.

--> When implemented, browsing to hosts in the webservers host group with the URL /

hello.php should produce the following output:

Hello PHP World from FQDN

--> where FQDN is the fully qualified domain name of the host. For example,

Hello PHP World from node3.example.com

following output:

Hello PHP World from node4.example.com

Options

AExplanation:
Solution as:
# pwd
/home/admin/ansible/
# vim balancer.yml
---
- name: Including phphello role
hosts: webservers
roles:
- ./roles/phphello
- name: Including balancer role
hosts: balancer
roles:
- ./roles/balancer
:wq!
# ansible-playbook balancer.yml --syntax-check
# ansible-playbook balancer.yml

Question No: 14

MultipleChoice

Create and run an Ansible ad-hoc command.

--> As a system administrator, you will need to install software on the managed

nodes.

--> Create a shell script called yum-pack.sh that runs an Ansible ad-hoc command to

create yum-repository on each of the managed nodes as follows:

--> repository1

-----------

1. The name of the repository is EX407

2. The description is 'Ex407 Description'

4. GPG signature checking is enabled

release

6. The repository is enabled

--> repository2

-----------

1. The name of the repository is EXX407

2. The description is 'Exx407 Description'

4. GPG signature checking is enabled

release

6. The repository is enabled

Options

AExplanation:
Solution as:
# pwd
/home/admin/ansible
# vim yum-pack.sh
#!/bin/bash
ansible all -m yum_repository -a 'name=EX407 description='Ex407 Description'
baseurl=http://content.example.com/rhel8.0/x86_64/dvd/BaseOS/ gpgcheck=yes
gpgkey=http://content.example.com/rhel8.0/x86_64/dvd/RPM-GPG-KEY-redhat-release
enabled=yes'
ansible all -m yum_repository -a 'name=EXX407 description='Exx407 Description'
baseurl=http://content.example.com/rhel8.0/x86_64/dvd/AppStream/ gpgcheck=yes
gpgkey=http://content.example.com/rhel8.0/x86_64/dvd/RPM-GPG-KEY-redhat-release
enabled=yes'
:!wq
# chmod +x yum-pack.sh
# bash yum-pack.sh
# ansible all -m command -a 'yum repolist all'

Question No: 15

MultipleChoice

Create a playbook /home/sandy/ansible/motd.yml that runs on all inventory hosts and docs the following: The playbook should replaee any existing content of/etc/motd in the following text. Use ansible facts to display the FQDN of each host

On hosts in the dev host group the line should be 'Welcome to Dev Server FQDN'.

On hosts in the webserver host group the line should be 'Welcome to Apache Server FQDN'.

On hosts in the database host group the line should be 'Welcome to MySQL Server FQDN'.

Options

AExplanation:
/home/sandy/ansible/apache.yml

/home/sandy/ansible/roles/sample-apache/tasks/main.yml

Question No: 16

MultipleChoice

In /home/sandy/ansible/ create a playbook called logvol.yml. In the play create a logical volume called Iv0 and make it of size 1500MiB on volume group vgO If there is not enough space in the volume group print a message 'Not enough space for logical volume' and then make a 800MiB Iv0 instead. If the volume group still doesn't exist, create a message 'Volume group doesn't exist' Create an xfs filesystem on all Iv0 logical volumes. Don't mount the logical volume.

Options

AExplanation:
Solution as:

Question No: 17

MultipleChoice

Create a file called specs.empty in home/sandy/ansible on the local machine as follows:

HOST=

MEMORY=

BIOS=

VDA_DISK_SIZE=

VDB_DISK_SIZE=

Create the playbook /home/sandy/ansible/specs.yml which copies specs.empty to all remote nodes' path /root/specs.txt. Using the specs.yml playbook then edit specs.txt on the remote machines to reflect the appropriate ansible facts.

Options

AExplanation:
Solution as:

Question No: 18

MultipleChoice

Create a jinja template in /home/sandy/ansible/ and name it hosts.j2. Edit this file so it looks like the one below. The order of the nodes doesn't matter. Then create a playbook in /home/sandy/ansible called hosts.yml and install the template on dev node at /root/myhosts

Options

AExplanation:
Solution as:

Question No: 19

MultipleChoice

Install and configure ansible

User sandy has been created on your control node. Give him the appropriate permissions on the control node. Install the necessary packages to run ansible on the control node.

Create a configuration file /home/sandy/ansible/ansible.cfg to meet the following requirements:

* The roles path should include /home/sandy/ansible/roles, as well as any other path that may be required for the course of the sample exam.

* The inventory file path is /home/sandyansible/inventory.

* Ansible should be able to manage 10 hosts at a single time.

* Ansible should connect to all managed nodes using the sandy user.

Create an inventory file for the following five nodes:

Configure these nodes to be in an inventory file where node1 is a member of group dev. nodc2 is a member of group test, nodc3 is a member of group proxy, nodc4 and node 5 are members of group prod. Also, prod is a member of group webservers.

Options

AExplanation:
In/home/sandy/ansible/ansible.cfg
[defaults]
inventory=/home/sandy/ansible/inventory
roles_path=/home/sandy/ansible/roles
remote_user= sandy
host_key_checking=false
[privilegeescalation]
become=true
become_user=root
become_method=sudo
become_ask_pass=false
In /home/sandy/ansible/inventory
[dev]
node 1 .example.com
[test]
node2.example.com
[proxy]
node3 .example.com
[prod]
node4.example.com
node5 .example.com
[webservers:children]
prod

Question No: 20

MultipleChoice

In /home/sandy/ansible/ create a playbook called logvol.yml. In the play create a logical volume called Iv0 and make it of size 1500MiB on volume group vgO If there is not enough space in the volume group print a message "Not enough space for logical volume" and then make a 800MiB Iv0 instead. If the volume group still doesn't exist, create a message "Volume group doesn't exist" Create an xfs filesystem on all Iv0 logical volumes. Don't mount the logical volume.

Options

ASolution as:

BSolution as:

Free RedHat EX294 Exam Dumps August 2026