Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

RedHat EX294 Exam - Topic 6 Question 54 Discussion

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 vdbEach line of the output file contains a single key-value pair.* Your playbook should:--> Download the file hwreport.empty from the URL http://classroom.example.com/hwreport.empty andsave 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 perquestation.hwreport.txt file consists.my_sys=hostnamemy_BIOS=biosversionmy_MEMORY=memorymy_vda=vdasizemy_vdb=vdbsize
A) Explanation: Solution as: # pwd /home/admin/ansible # vim hwreport.yml - name: hosts: all ignore_errors: yes tasks: - name: download file get_url: url: http://classroom.example.com/content/ex407/hwreport.empty dest: /root/hwreport.txt - name: vdasize replace: regexp: 'vdasize' replace: '{{ ansible_facts.devices.vda.size }}' dest: /root/hwreport.txt register: op1 - debug: var: op1 - name: none replace: regexp: 'vdasize' replace: NONE dest: /root/hwreport.txt when: op1.failed == true - name: vdbsize replace: regexp: 'vdbsize' replace: '{{ ansible_facts.devices.vdb.size }}' dest: /root/hwreport.txt register: op2 - debug: var: op2 - name: none replace: regexp: 'vdbsize' replace: NONE dest: /root/hwreport.txt when: op2.failed == true - name: sysinfo replace: regexp: '{{item.src}}' replace: '{{item.dest}}' dest: /root/hwreport.txt loop: - src: 'hostname' dest: '{{ ansible_facts.fqdn }}' - src: 'biosversion' dest: '{{ ansible_facts.bios_version }}' - src: 'memory' dest: '{{ ansible_facts.memtotal_mb }}' :wq! # ansible-playbook hwreport.yml ---syntax-check # ansible-playbook hwreport.yml

RedHat EX294 Exam - Topic 6 Question 54 Discussion

Actual exam question for RedHat's EX294 exam
Question #: 54
Topic #: 6
[All EX294 Questions]

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:

--> Download the file hwreport.empty from the URL http://classroom.example.com/

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

Show Suggested Answer Hide Answer
Suggested Answer: A

by Anastacia at Sep 13, 2024, 02:57 PM

Limited Time Offer

25%

Off

Get Premium EX294 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Royal
7 months ago
This is a solid approach, but I'm not sure about the error handling part.
upvoted 0 times
...
Aaron
8 months ago
Wait, does it really set values to NONE if the hardware is missing?
upvoted 0 times
...
Portia
8 months ago
I think the URL in the playbook is wrong.
upvoted 0 times
...
Val
8 months ago
Totally agree, but what if vdb doesn't exist?
upvoted 0 times
...
Raymon
8 months ago
Sounds straightforward, just need to pull the right facts.
upvoted 0 times
...
Janine
9 months ago
I recall we had to use a loop for replacing multiple values in a file, so I hope I can remember how to set that up correctly in this playbook.
upvoted 0 times
...
Arlette
9 months ago
I feel confident about downloading the file with get_url, but I’m worried I might mix up the variables for memory and BIOS version in the output.
upvoted 0 times
...
Hayley
9 months ago
I think we did a similar question where we had to check for device sizes, but I’m not clear on how to handle the "NONE" value if a device doesn’t exist.
upvoted 0 times
...
Ashley
9 months ago
I remember we practiced creating playbooks that gather system information, but I’m a bit unsure about the exact syntax for the replace module.
upvoted 0 times
...
Velda
9 months ago
This exam question looks pretty straightforward, but I want to make sure I don't miss anything. I'm going to carefully read through the requirements one more time to make sure I understand exactly what I need to do. Then I'll start building out the playbook step-by-step.
upvoted 0 times
...
Elinore
9 months ago
Okay, I think I've got a good strategy for this. First, I'll use the get_url module to download the hwreport.empty file. Then, I'll use the replace module to swap out the placeholders with the actual system facts. And if any of the hardware items don't exist, I'll set the value to "NONE". Feels like a good plan!
upvoted 0 times
...
Junita
9 months ago
Hmm, I'm a bit confused about the part where we need to set the values to "NONE" if the hardware item doesn't exist. Not sure how to handle that properly in the playbook. Might need to do some research on the Ansible replace module.
upvoted 0 times
...
Annmarie
9 months ago
This looks like a pretty straightforward task. I think I can handle this - just need to download the file, replace the placeholders with the actual system information, and save the output. Shouldn't be too difficult.
upvoted 0 times
...
Madelyn
1 year ago
The playbook looks great, but I'm a little worried about the `ignore_errors` setting. What if something goes wrong during the execution, and we miss important information in the output file? Maybe we could add some error handling instead.
upvoted 0 times
Simona
1 year ago
Yes, using 'block' and 'rescue' will make the playbook more robust and reliable during execution.
upvoted 0 times
...
Desiree
1 year ago
Adding error handling will definitely make the playbook more robust and reliable.
upvoted 0 times
...
Lashandra
1 year ago
That's a good idea. We can also use 'block' and 'rescue' keywords to group tasks and handle errors more efficiently.
upvoted 0 times
...
Charlene
1 year ago
We could also consider using 'block' and 'rescue' to group tasks and handle errors more efficiently.
upvoted 0 times
...
Shenika
1 year ago
We can add a 'failed_when' condition to the tasks to handle errors and ensure important information is not missed.
upvoted 0 times
...
Graciela
1 year ago
That's a good point. We should make sure to capture any errors that occur during the execution.
upvoted 0 times
...
Myra
1 year ago
We can add a 'failed_when' condition to the tasks to handle errors more effectively.
upvoted 0 times
...
...
Doug
1 year ago
Eve
upvoted 0 times
Evan
1 year ago
What should be done if a hardware item does not exist?
upvoted 0 times
...
Melynda
1 year ago
What is the next step after creating the playbook?
upvoted 0 times
...
...
Oliva
1 year ago
Yes, the playbook steps are well explained with the necessary tasks.
upvoted 0 times
...
Quentin
1 year ago
I agree, but the solution provided seems clear.
upvoted 0 times
...
Oliva
1 year ago
I think this question is tricky.
upvoted 0 times
...

Save Cancel