Valid Red Hat Certified Architect (RHCA) EX447 Dumps Ensure Your Passing [Q14-Q35]

May 8, 2022 admin 0

Rate this post

Valid Red Hat Certified Architect (RHCA) EX447 Dumps Ensure Your Passing

EX447 Dumps Real Exam Questions Test Engine Dumps Training

RedHat EX447 Exam Syllabus Topics:

Topic	Details
Topic 1	Set up directories containing multiple host variable files for some of your managed hosts Create machine credentials to access inventory hosts
Topic 2	Use special variables to override the host, port, or remote user Ansible uses for a specific host Transform data with filters and plugins
Topic 3	Perform basic configuration of Ansible Tower after configuration Populate variables with data from external sources using lookup plugins
Topic 4	Write an API scriptlet to launch a job Manage inventories and credentials Create a job workflow template
Topic 5	Implement loops using structures other than simple lists using lookup plugins and filters Add those modified files back into the Git repository
Topic 6	Run a task for a managed host on a different host, then control whether facts gathered by that task are delegated to the managed host or the other host
Topic 7	Inspect, validate, and manipulate variables containing networking information with filters Update, modify and create files in a Git repository
Topic 8	Override the name used in the inventory file with a different name or IP address Create Ansible Tower users and teams and make associations of one to the other
Topic 9	Create a source control credential Control privilege execution Manage inventory variables
Topic 10	Use lookup and query functions to template data from external sources into playbooks and deployed template files

NEW QUESTION 14
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/ansiblecalledhosts.yml and install the template on dev node at

NEW QUESTION 15
Using the Simulation Program,perform the following tasks:
1. Use an ansible ad-hoc command, check the connectivity of your servers.
2. Use an ad-hoc ansible command, find the free space of your servers.
3. Use an ad-hoc ansible command, find out the memory usage of your servers.
4. Do an ls -l on the targets /var/log/messages file.
5. Tail the contents of the targets /var/log/messages file.

NEW QUESTION 16
Create a file calledrequirements.ymlin/home/sandy/ansible/rolesto install two roles. The source for the first role is geerlingguy.haproxy and geerlingguy.php. Name the first haproxy-role and the second php-role. The roles should be installed in/home/sandy/ansible/roles.

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

NEW QUESTION 18
Create the users in the fileusersjist.ymlfile provided. Do this in a playbook called users.yml located at
/home/sandy/ansible.The passwords for these users should be set using thelock.ymlfile from TASK7. When running the playbook, the lock.yml file should be unlocked withsecret.txtfile from TASK 7.
All users with the job of ‘developer’ should be created on thedevhosts, add them to the group devops, their password should be set using thepw_devvariable. Likewise create users with the job of ‘manager’ on theproxy host and add the users to the group ‘managers’, their password should be set using thepw_mgrvariable.

NEW QUESTION 19
Create a playbook calledtimesvnc.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.

NEW QUESTION 20
Using the Simulation Program, perform the following tasks:
Static Inventories Task:
1. Add a new group to your default ansible host file. call the group [ec2]
2. Add a newhost to the new group you created.
3. Add a variable to a new host entry in the /etc/ansible/hosts file. Add the following. localhost http_port=80 maxRequestsPerChild=808
4. Check to see if maxRequestsPerChild is pulled out with an ad-hoccommand.
5. Create a local host file and put a target group and then a host into it. Then ping it with an ad-hoc command.

NEW QUESTION 21
Create a file calledadhoc.shin/home/sandy/ansiblewhich will use adhoc commands to set up anew 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.

NEW QUESTION 22
Create an ansible vault password file calledlock.ymlwith the passwordreallysafepwin the
/home/sandy/ansibledirectory. In the lock.yml file define two variables. One ispw_devand the password is
‘dev’ and the other ispw_mgrand the password is ‘mgr’ Create a regular file calledsecret.txtwhich contains the password for lock.yml.

NEW QUESTION 23
In /home/sandy/ansible/create a playbook called the play create a logical volume calledIv0and make it of size 1500MiB on volume group If there is not enough space in the volume groupprinta message
“Not enough space for logical vol instead. If the volume group still doesn’t exist, create a message”Volume group doesn’t exist” filesystem on allIv0logical volumes. Don’t mount the logical volume.