Provide RedHat EX294 Dumps Updated Aug 30, 2022 With 35 QA’s [Q11-Q32] – IT Certification Exam Questions & Answers

4.3/5 - (3 votes)

Provide RedHat EX294 Dumps Updated Aug 30, 2022 With 35 QA’s

Latest EX294 Dumps for Success in Actual RedHat Certified

Red Hat RHCE Exam Syllabus Topics:

Section	Objectives
Install and configure an Ansible control node	– Install required packages – Create a static host inventory file – Create a configuration file – Create and use static inventories to define groups of hosts – Manage parallelism
Create Ansible plays and playbooks	– Know how to work with commonly used Ansible modules – Use variables to retrieve the results of running a command – Use conditionals to control play execution – Configure error handling – Create playbooks to configure systems to a specified state
Script administration tasks	– Create simple shell scripts – Create simple shell scripts that run ad hoc Ansible commands
Be able to perform all tasks expected of a Red Hat Certified System Administrator	– Understand and use essential tools – Operate running systems – Configure local storage – Create and configure file systems – Deploy, configure, and maintain systems – Manage users and groups – Manage security
Understand core components of Ansible	– Inventories – Modules – Variables – Facts – Plays – Playbooks – Configuration files – Use provided documentation to look up specific information about Ansible modules and commands
Use advanced Ansible features	– Create and use templates to create customized configuration files – Use Ansible Vault in playbooks to protect sensitive data

NEW QUESTION 11
Create the users in the file usersjist.yml file provided. Do this in a playbook called users.yml located at /home/sandy/ansible. The passwords for these users should be set using the lock.yml file from TASK7. When running the playbook, the lock.yml file should be unlocked with secret.txt file from TASK 7.
All users with the job of ‘developer’ should be created on the dev hosts, add them to the group devops, their password should be set using the pw_dev variable. Likewise create users with the job of ‘manager’ on the proxy host and add the users to the group ‘managers’, their password should be set using the pw_mgr variable.

NEW QUESTION 12
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.

Solution as:

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

Solution as:

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

NEW QUESTION 13
Create a role called sample-apache in /home/sandy/ansible/roles that enables and starts httpd, enables and starts the firewall and allows the webserver service. Create a template called index.html.j2 which creates and serves a message from /var/www/html/index.html Whenever the content of the file changes, restart the webserver service.
Welcome to [FQDN] on [IP]
Replace the FQDN with the fully qualified domain name and IP with the ip address of the node using ansible facts. Lastly, create a playbook in /home/sandy/ansible/ called apache.yml and use the role to serve the index file on webserver hosts.

Option

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

/home/sandy/ansible/roles/sample-apache/templates/index.html.j2

In /home/sandy/ansible/roles/sample-apache/handlers/main.yml

Option

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

/home/sandy/ansible/roles/sample-apache/templates/index.html.j2
In /home/sandy/ansible/roles/sample-apache/handlers/main.yml

NEW QUESTION 14
Create a playbook called issue.yml in /home/sandy/ansible which changes the file /etc/issue on all managed nodes: If host is a member of (lev then write “Development” If host is a member of test then write “Test” If host is a member of prod then write “Production”

Solution as:

NEW QUESTION 15
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

NEW QUESTION 16
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

NEW QUESTION 17
Create a playbook called regulartasks.yml which has the system that append the date to /root/datefile every day at noon. Name is job ‘datejob’

NEW QUESTION 18
Create an Ansible vault to store user passwords as follows:
* The name of the vault is valut.yml
* The vault contains two variables as follows:
– dev_pass with value wakennym
– mgr_pass with value rocky
* The password to encrypt and decrypt the vault is atenorth
* The password is stored in the file /home/admin/ansible/password.txt

NEW QUESTION 19
Create a file called packages.yml in /home/sandy/ansible to install some packages for the following hosts. On dev, prod and webservers install packages httpd, mod_ssl, and mariadb. On dev only install the development tools package. Also, on dev host update all the packages to the latest.

Option

** NOTE 1 a more acceptable answer is likely ‘present’ since it’s not asking to install the latest state: present
** NOTE 2 need to update the development node
– name: update all packages on development node
yum:
name: ‘*’
state: latest

Option

NEW QUESTION 20
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.

Solution as:

NEW QUESTION 21
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.

Solution as:

NEW QUESTION 22
Create a playbook called webdev.yml in ‘home/sandy/ansible. The playbook will create a directory Avcbdev on dev host. The permission of the directory are 2755 and owner is webdev. Create a symbolic link from /Webdev to /var/www/html/webdev. Serve a file from Avebdev7index.html which displays the text “Development” Curl http://node1.example.com/webdev/index.html to test

NEW QUESTION 23
Create a playbook that changes the default target on all nodes to multi-user tarqet. Do this in playbook file called target.yml in /home/sandy/ansible

– name: change default target
hosts: all
tasks:
– name: change target
file:
src: /usr/lib/systemd/system/multi-user.target dest: /etc/systemd/system/default.target state: link

– name: change default target
hosts: all
– name: change target
file:
src: /usr/lib/systemd/system/multi-user.target dest: /etc/systemd/system/default.target state: link

NEW QUESTION 24
Create an empty encrypted file called myvault.yml in /home/sandy/ansible and set the password to notsafepw. Rekey the password to iwejfj2221.

NEW QUESTION 25
Create a role called sample-apache in /home/sandy/ansible/roles that enables and starts httpd, enables and starts the firewall and allows the webserver service. Create a template called index.html.j2 which creates and serves a message from /var/www/html/index.html Whenever the content of the file changes, restart the webserver service.
Welcome to [FQDN] on [IP]
Replace the FQDN with the fully qualified domain name and IP with the ip address of the node using ansible facts. Lastly, create a playbook in /home/sandy/ansible/ called apache.yml and use the role to serve the index file on webserver hosts.

NEW QUESTION 26
Modify file content.
————————
Create a playbook called /home/admin/ansible/modify.yml as follows:
* The playbook runs on all inventory hosts
* The playbook replaces the contents of /etc/issue with a single line of text as
follows:
–> On hosts in the dev host group, the line reads: “Development”
–> On hosts in the test host group, the line reads: “Test”
–> On hosts in the prod host group, the line reads: “Production”

NEW QUESTION 27
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.

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

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

NEW QUESTION 28
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

Solution as:

NEW QUESTION 29
Create a file in /home/sandy/ansible/ called report.yml. Using this playbook, get a file called report.txt (make it look exactly as below). Copy this file over to all remote hosts at /root/report.txt. Then edit the lines in the file to provide the real information of the hosts. If a disk does not exist then write NONE.

NEW QUESTION 30
Create a file called adhoc.sh in /home/sandy/ansible which will use adhoc commands to set up a new repository. The name of the repo will be ‘EPEL’ the description ‘RHEL8’ the baseurl is ‘https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rmp’ there is no gpgcheck, but you should enable the repo.
* You should be able to use an bash script using adhoc commands to enable repos. Depending on your lab setup, you may need to make this repo “state=absent” after you pass this task.

chmod 0117 adhoc.sh
vim adhoc.sh
#I/bin/bash
ansible all -m yum_repository -a ‘name=EPEL description=RHEL8
baseurl=https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rmp gpgcheck=no enabled=yes’

chmod 0777 adhoc.sh
vim adhoc.sh
#I/bin/bash
ansible all -m yum_repository -a ‘name=EPEL description=RHEL8
baseurl=https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rmp gpgcheck=no enabled=yes’

NEW QUESTION 31
Create a playbook called regulartasks.yml which has the system that append the date to /root/datefile every day at noon. Name is job ‘datejob’

Solution as:

NEW QUESTION 32
Create a file called requirements.yml in /home/sandy/ansible/roles to install two roles. The source for the first role is geerlingguy.haproxy and geerlingguy.php. Name the first haproxy-role and the second php-role. The roles should be installed in /home/sandy/ansible/roles.