BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Free RedHat EX294 Exam Dumps

Here you can find all the free questions related with RedHat Red Hat Certified Engineer (RHCE) exam for Red Hat Enterprise Linux 8 Exam (EX294) exam. You can also find on this page links to recently updated premium files with which you can practice for actual RedHat Red Hat Certified Engineer (RHCE) exam for Red Hat Enterprise Linux 8 Exam . These premium versions are provided as EX294 exam practice tests, both as desktop software and browser based application, you can use whatever suits your style. Feel free to try the Red Hat Certified Engineer (RHCE) exam for Red Hat Enterprise Linux 8 Exam premium files for free, Good luck with your RedHat Red Hat Certified Engineer (RHCE) exam for Red Hat Enterprise Linux 8 Exam .
Question No: 1

MultipleChoice

Create user accounts

------------------------

--> A list of users to be created can be found in the file called user_list.yml

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

Options
Question No: 2

MultipleChoice

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.

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

Options
Question No: 3

MultipleChoice

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:

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.

Options
Question No: 4

MultipleChoice

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:

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

Options
Question No: 5

MultipleChoice

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''

Options
Question No: 6

MultipleChoice

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

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,

Hello PHP World from node3.example.com

following output:

Hello PHP World from node4.example.com

Options
Question No: 7

MultipleChoice

Create and run an Ansible ad-hoc command.

--> As a system administrator, you will need to install software on the managed

nodes.

--> Create a shell script called yum-pack.sh that runs an Ansible ad-hoc command to

create yum-repository on each of the managed nodes as follows:

--> repository1

-----------

1. The name of the repository is EX407

2. The description is 'Ex407 Description'

4. GPG signature checking is enabled

release

6. The repository is enabled

--> repository2

-----------

1. The name of the repository is EXX407

2. The description is 'Exx407 Description'

4. GPG signature checking is enabled

release

6. The repository is enabled

Options
Question No: 8

MultipleChoice

Create a playbook /home/sandy/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'.

Options
Question No: 9

MultipleChoice

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.

Options
Question No: 10

MultipleChoice

Create a file called specs.empty in home/sandy/ansible on the local machine as follows:

HOST=

MEMORY=

BIOS=

VDA_DISK_SIZE=

VDB_DISK_SIZE=

Create the playbook /home/sandy/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.

Options

Save Cancel