Red Hat Red Hat Certifications EX294 Questions & Answers

• Question 51:

  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.

  A. Answer: See the for complete Solution below.

  Correct Answer: A

  Solution as:

  

  

• Question 52:

  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.

  A. Answer: See the for complete Solution below.

  Correct Answer: A

  Solution as:

  

• Question 53:

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

  A.

  Answer: See the for complete Solution below.

  Correct Answer: A

  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'

• Question 54:

  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.

  A. Answer: See the for complete Solution below.

  Correct Answer: A

  Solution as:

  

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

• Question 55:

  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.

  A. Answer: See the for complete Solution below.

  Correct Answer: A

  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 56:

  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.

  A. Answer: See the for complete Solution below.

  Correct Answer: A

  Solution as:

  

• Question 57:

  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.

  A. Answer: See the for complete Solution below.

  Correct Answer: A

  Solution as: ** 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

• Question 58:

  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.

  

  A. Answer: See the for complete Solution below.

  Correct Answer: A

  Solution as:

  

  

• Question 59:

  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

  A. Answer: See the for complete Solution below.

  Correct Answer: A

  Solution as:

  

• Question 60:

  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.

  

  A. Answer: See the for complete Solution below.

  Correct Answer: A

  ansible-playbook users.yml –vault-password-file=secret.txt