Free EX294 Exam Braindumps – New 2022 RedHat Pratice Exam [Q13-Q33]

NO.13 Create a role called apache in “/home/admin/ansible/roles” with the following
requirements:
–> The httpd package is installed, enabled on boot, and started.
–> The firewall is enabled and running with a rule to allow access to the web server.
–> template file index.html.j2 is used to create the file /var/www/html/index.html
with the output:
Welcome to HOSTNAME on IPADDRESS
–> Where HOSTNAME is the fqdn of the managed node and IPADDRESS is the IP-Address of
the managed node.
note: you have to create index.html.j2 file.
–> Create a playbook called httpd.yml that uses this role and the playbook runs on
hosts in the webservers host group.

NO.14 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

NO.15 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:
nodel.example.com
node2.example.com
node3.example.com
node4.example.com
node5.example.com
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.

NO.16 Install the RHEL system roles package and create a playbook called timesync.yml that:
–> Runs over all managed hosts.
–> Uses the timesync role.
–> Configures the role to use the time server 192.168.10.254 ( Hear in redhat lab
use “classroom.example.com” )
–> Configures the role to set the iburst parameter as enabled.

NO.17 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.

NO.18 Create a playbook called packages.yml that:
———————————————-
–> Installs the php and mariadb packages on hosts in the dev, test, and prod host
groups.
–> Installs the Development Tools package group on hosts in the dev host group.
–> Updates all packages to the latest version on hosts in the dev host group.

NO.19 Create an empty encrypted file called myvault.yml in /home/sandy/ansible and set the password to notsafepw. Rekey the password to iwejfj2331.

NO.20 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.

NO.21 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

NO.22 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

NO.23 Create a playbook /home/bob /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”.

NO.24 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.

NO.25 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.

NO.26 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.

NO.27 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

NO.28 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.

NO.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.

NO.30 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.

NO.31 Create Logical volumes with lvm.yml in all nodes according to following
requirements.
—————————————————————————————-
* Create a new Logical volume named as ‘data’
* LV should be the member of ‘research’ Volume Group
* LV size should be 1500M
* It should be formatted with ext4 file-system.
–> If Volume Group does not exist then it should print the message “VG Not found”
–> If the VG can not accommodate 1500M size then it should print “LV Can not be
created with
following size”, then the LV should be created with 800M of size.
–> Do not perform any mounting for this LV.

NO.32 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.

NO.33 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:
–> Download the file hwreport.empty from the URL http://classroom.example.com/
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