EX294 Dumps 2023 New RedHat EX294 Exam Questions [Q15-Q37]

EX294 Dumps 2023 New RedHat EX294 Exam Questions [Q15-Q37]

5/5 - (1 vote)

EX294 Dumps 2023 – New RedHat EX294 Exam Questions

Free EX294 braindumps download (EX294 exam dumps Free Updated)

Total Cost for the RedHat EX294 Certification Exam:

The cost of this RedHat EX294 Certification Exam is $400.

 

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

Q16. 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’

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

 
 

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

Q19. 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”

Q20. 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.
node1.example.com
node2.example.com
node3.example.com
node4.example.com
node5.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.

Q21. Generate a hosts file:
* Download an initial template file hosts.j2 from http://classroom.example.com/
hosts.j2 to
/home/admin/ansible/ Complete the template so that it can be used to generate a file with a line for each inventory host in the same format as /etc/hosts:
172.25.250.9 workstation.lab.example.com workstation
* Create a playbook called gen_hosts.yml that uses this template to generate the file /etc/myhosts on hosts in the dev host group.
* When completed, the file /etc/myhosts on hosts in the dev host group should have a line for each managed host:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
172.25.250.10 serevra.lab.example.com servera
172.25.250.11 serevrb.lab.example.com serverb
172.25.250.12 serevrc.lab.example.com serverc
172.25.250.13 serevrd.lab.example.com serverd
—————————————————————–
while practising you to create these file hear. But in exam have to download as per questation.
hosts.j2 file consists.
localhost localhost.localdomain localhost4 localhost4.localdomain4
::1
localhost localhost.localdomain localhost6 localhost6.localdomain6
——————————————————————-

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

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

 
 

Q24. Create a playbook called timesvnc.yml in /home/sandy/ansible using rhel system role timesync. Set the time to use currently configured nip with the server 0.uk.pool.ntp.org. Enable burst. Do this on all hosts.

 
 

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

Q26. Create user accounts
————————
–> A list of users to be created can be found in the file called user_list.yml
which you should download from http://classroom.example.com/user_list.yml and
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

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

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

Q29. 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
http://node5.example.com) should produce the following output:
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,
browsing to http://node3.example.com/hello.php, should produce the following output:
Hello PHP World from node3.example.com
* Similarly, browsing to http://node4.example.com/hello.php, should produce the
following output:
Hello PHP World from node4.example.com

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

Q31. 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”

 
 

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

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

 
 

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

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

Q36. 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”.

 
 

The RedHat EX294 certification exam is a highly respected certification for IT professionals who want to demonstrate their expertise in managing and deploying Linux systems. It requires hands-on experience and a deep understanding of the Linux operating system. With the increasing demand for Linux administrators in the industry, this certification can help IT professionals to enhance their career prospects and take their skills to the next level.

 

Verified EX294 dumps Q&As – Pass Guarantee Exam Dumps Test Engine: https://www.validbraindumps.com/EX294-exam-prep.html

         

Leave a Reply

Your email address will not be published. Required fields are marked *

Enter the text from the image below