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 3 Question 49 Discussion

Create Logical volumes with lvm.yml in all nodes according to followingrequirements.----------------------------------------------------------------------------------------* Create a new Logical volume named as 'data'* LV should be the member of 'research' Volume Group* LV size should be 1500M* It should be formatted with ext4 file-system.--> If Volume Group does not exist then it should print the message "VG Not found"--> If the VG can not accommodate 1500M size then it should print "LV Can not becreated withfollowing size", then the LV should be created with 800M of size.--> Do not perform any mounting for this LV.
A) Explanation: Solution as: # pwd /home/admin/ansible # vim lvm.yml --- - name: hosts: all ignore_errors: yes tasks: - name: lvol: lv: data vg: research size: '1500' - debug: msg: 'VG Not found' when: ansible_lvm.vgs.research is not defined - debug: msg: 'LV Can not be created with following size' when: ansible_lvm.vgs.research.size_g < '1.5' - name: lvol: lv: data vg: research size: '800' when: ansible_lvm.vgs.research.size_g < '1.5' - name: filesystem: fstype: ext4 dev: /dev/research/data :wq! # ansible-playbook lvm.yml ---syntax-check # ansible-playbook lvm.yml

RedHat EX294 Exam - Topic 3 Question 49 Discussion

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

Create Logical volumes with lvm.yml in all nodes according to following

requirements.

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

* Create a new Logical volume named as 'data'

* LV should be the member of 'research' Volume Group

* LV size should be 1500M

* It should be formatted with ext4 file-system.

--> If Volume Group does not exist then it should print the message "VG Not found"

--> If the VG can not accommodate 1500M size then it should print "LV Can not be

created with

following size", then the LV should be created with 800M of size.

--> Do not perform any mounting for this LV.

Show Suggested Answer Hide Answer
Suggested Answer: A

by Elmira at Jul 08, 2024, 07:36 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
Lavonda
9 months ago
VG Not found message is a nice touch!
upvoted 0 times
...
Belen
10 months ago
Seems straightforward, but why no mounting?
upvoted 0 times
...
Leoma
10 months ago
Wait, can it really create an 800M LV if the 1500M fails?
upvoted 0 times
...
Diane
10 months ago
Agree, but what if the VG doesn't exist?
upvoted 0 times
...
Gail
10 months ago
Just a reminder, the LV size is set to 1500M.
upvoted 0 times
...
Britt
11 months ago
I definitely recall that we shouldn't mount the logical volume, but I can't remember if we need to specify the filesystem before creating the LV.
upvoted 0 times
...
Georgeanna
11 months ago
I feel a bit uncertain about the size checks. Did we use 'size_g' for the volume group size in our practice?
upvoted 0 times
...
Christiane
11 months ago
I think we had a similar question where we had to check for volume groups. I hope I can remember the conditionals correctly.
upvoted 0 times
...
Bernardo
11 months ago
I remember we practiced creating logical volumes, but I'm not sure about the exact syntax for the debug messages.
upvoted 0 times
...
Lonny
11 months ago
No problem, I've done this kind of thing before. I'll just follow the requirements step-by-step and make sure to handle the error cases as specified.
upvoted 0 times
...
Noah
11 months ago
This seems doable, but I'm a little worried about the formatting part. I'll need to double-check the filesystem module syntax to make sure I get that right.
upvoted 0 times
...
Kara
11 months ago
Okay, I think I've got a good handle on this. I'll create the LV in the 'research' VG, and if that VG doesn't exist or can't accommodate the size, I'll print the appropriate messages and create a smaller LV.
upvoted 0 times
...
Ailene
11 months ago
Hmm, I'm a bit confused about the conditional checks for the VG and LV size. I'll need to review the Ansible documentation on those modules.
upvoted 0 times
...
Raylene
11 months ago
This looks like a straightforward LVM task, but I'll need to be careful to handle the edge cases properly.
upvoted 0 times
...
Aliza
11 months ago
I'm not entirely sure about this one. The options all sound similar, but I think Option D might be the right answer since it mentions adjusting correlation search thresholds over time.
upvoted 0 times
...
Zoila
11 months ago
Hmm, this seems like a tricky one. I'll need to think through the DTMF options carefully.
upvoted 0 times
...
Marvel
2 years ago
The solution is on point! It's like the developer had a crystal ball and foresaw all the possible issues. Impressive work!
upvoted 0 times
...
Luke
2 years ago
Looks like a well-crafted playbook. I'm curious to see how it handles the case where the VG has just enough space for an 800M LV but not 1500M.
upvoted 0 times
Willow
2 years ago
Yes, it's good that it can adjust the LV size based on available space in the VG.
upvoted 0 times
...
Reuben
2 years ago
This playbook seems to have all the scenarios covered.
upvoted 0 times
...
...
Lura
2 years ago
This is a solid solution! The only thing I would suggest is to add a task to mount the LV, just in case the user wants to use it immediately.
upvoted 0 times
...
Afton
2 years ago
The solution is comprehensive and covers all the requirements. I wonder if there's a way to make the size more flexible, like accepting it as a parameter?
upvoted 0 times
...
Angella
2 years ago
I like how the solution uses the `debug` module to print informative messages. It's a nice way to provide feedback to the user.
upvoted 0 times
...
Samira
2 years ago
The solution uses the `lvol` module, which is a nice touch. It also checks for the existence of the VG and adjusts the LV size accordingly. Very well-thought-out!
upvoted 0 times
...
Chery
2 years ago
The playbook looks good, but I'm not sure why the size is specified in M instead of G. Shouldn't it be 1.5G?
upvoted 0 times
Alverta
2 years ago
Yes, you're right. It should be specified in G for consistency.
upvoted 0 times
...
Lakeesha
2 years ago
It should be 1.5G.
upvoted 0 times
...
Latosha
2 years ago
Leonie: That makes sense, but it could be a bit confusing for some users.
upvoted 0 times
...
Fernanda
2 years ago
Maybe they wanted to keep it consistent with the rest of the playbook.
upvoted 0 times
...
Magnolia
2 years ago
The playbook looks good, but I'm not sure why the size is specified in M instead of G.
upvoted 0 times
...
Leonie
2 years ago
Yeah, it should be 1.5G instead of 1500M.
upvoted 0 times
...
Walton
2 years ago
The playbook looks good, but I'm not sure why the size is specified in M instead of G.
upvoted 0 times
...
...
Blair
2 years ago
I think it's important to understand the conditions for creating the LV with the specified size.
upvoted 0 times
...
Rima
2 years ago
This is a great question! The solution covers all the edge cases and handles the error scenarios well.
upvoted 0 times
Weldon
2 years ago
Yes, it's good to see that they considered different scenarios and provided appropriate responses.
upvoted 0 times
...
Terrilyn
2 years ago
I agree, the solution seems very thorough and well thought out.
upvoted 0 times
...
...
Margurite
2 years ago
I believe the provided solution in the explanation is clear and helpful.
upvoted 0 times
...
Nelida
2 years ago
I agree, it requires attention to detail to meet the requirements.
upvoted 0 times
...
Elmer
2 years ago
I think creating logical volumes with lvm.yml is a crucial task in the exam.
upvoted 0 times
...

Save Cancel