[Nov 13, 2021] EX294 PDF Recently Updated Questions Dumps to Improve Exam Score [Q11-Q36]

[Nov 13, 2021] EX294 PDF Recently Updated Questions Dumps to Improve Exam Score

EX294 Dumps Full Questions with Free PDF Questions to Pass

Red Hat EX294 Exam Certification Details:

Passing Score	210 / 300
Sample Questions	Red Hat EX294 Sample Questions
Number of Questions	20
Duration	240 minutes
Exam Name	Red Hat Certified Engineer (RHCE)
Exam Code	EX294
Schedule Exam	PEARSON VUE
Exam Price	$400 USD

RedHat EX294 Exam Syllabus Topics:

Topic	Details
Topic 1	Install and configure a compatible control unit Create a static host inventory file Create a configuration file
Topic 2	Features Use system modules that work with Software package and storage, Firewall rules, storage devices, Users and groups
Topic 3	Create and configure file systems User and group management Security management
Topic 4	Create SSH keys and distribute them to managed nodes Create and use static invariants to define host groups
Topic 5	Create a simple script Configure error handling Working with roles Download and use roles from Ansible Galaxy
Topic 6	Configure local storage Operating system
Topic 7	Create an instruction manual to configure the system for a specific situation Learn to work with frequently used Ansible units
Topic 8	Create simple shell scripts that run custom Ansible commands Administrative work scenario
Topic 9	Understand and use basic tools System deployment, configuration and maintenance
Topic 10	Verify that the functional configuration is correct by using the Ansible custom command
Topic 11	Unable to create drama and playbook Install the required package Parallel management
Topic 12	Use the documentation provided to get specific information about the available modules and commands
Topic 13	To protect sensitive data, use Ansible Vault in the user guide Take advantage of additional enhancements
Topic 14	Understand the key components of Ancibel Exams, Units, Variable, Facts, Play the manual, configuration file
Topic 15	Use the variable to get the results of the command run Use the conditions to control the progress of the game
Topic 16	Create managed managed nodes Configure privilege escalation on managed nodes

NEW QUESTION 11
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".

A. /home/sandy/ansible/apache.yml

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

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

Answer: B

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.

A. Solution as:

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

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

Answer: A

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

A. Solution as:
B. Solution as:

Answer: A

NEW QUESTION 16
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. ansible-playbook users.yml -vault-password-file=secret.txt
B. ansible-playbook users.yml -vault-password-file=secret.txt

Answer: B

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

Answer: A

NEW QUESTION 18
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"