[Oct 21, 2021] Passing Key To Getting EX294 Certified Exam Engine PDF [Q12-Q36]

[Oct 21, 2021] Passing Key To Getting EX294 Certified Exam Engine PDF

EX294 Exam Dumps Pass with Updated Oct-2021 Tests Dumps

Red Hat RHCE Exam Syllabus Topics:

Section	Objectives
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
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
Work with roles	- Create roles - Download roles from an Ansible Galaxy and use them
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
Use advanced Ansible features	- Create and use templates to create customized configuration files - Use Ansible Vault in playbooks to protect sensitive data
Use Ansible modules for system administration tasks that work with:	- Software packages and repositories - Services - Firewall rules - File systems - Storage devices - File content - Archiving - Scheduled tasks - Security - Users and groups
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
Script administration tasks	- Create simple shell scripts - Create simple shell scripts that run ad hoc Ansible commands
Configure Ansible managed nodes	- Create and distribute SSH keys to managed nodes - Configure privilege escalation on managed nodes - Validate a working configuration using ad hoc Ansible commands

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

A. 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'
B. 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'

Answer: B

NEW QUESTION 13
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. Solution as:
B. Solution as:

Answer: B

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

A. - 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
B. - 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

Answer: B

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

Answer: A

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

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_ask_pass=false
In /home/sandy/ansible/inventory
[dev]
node 1 .example.com
[test]
node2.example.com
node4.example.com
node5 .example.com
[webservers:children]
prod
B. 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

Answer: B

NEW QUESTION 17
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. Solution as:
B. Solution as:

Answer: B

NEW QUESTION 18
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. Solution as:
B. Solution as:

Answer: A

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