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

- Free Preparation Discussions

RedHat Exam EX294 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

Contribute your Thoughts:

Marvel
3 months 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
3 months 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 months ago
Yes, it's good that it can adjust the LV size based on available space in the VG.
upvoted 0 times
...
Reuben
3 months ago
This playbook seems to have all the scenarios covered.
upvoted 0 times
...
...
Lura
3 months 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
3 months 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
3 months 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
3 months 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
3 months 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 months ago
Yes, you're right. It should be specified in G for consistency.
upvoted 0 times
...
Lakeesha
2 months ago
It should be 1.5G.
upvoted 0 times
...
Latosha
2 months ago
Leonie: That makes sense, but it could be a bit confusing for some users.
upvoted 0 times
...
Fernanda
3 months ago
Maybe they wanted to keep it consistent with the rest of the playbook.
upvoted 0 times
...
Magnolia
3 months ago
The playbook looks good, but I'm not sure why the size is specified in M instead of G.
upvoted 0 times
...
Leonie
3 months ago
Yeah, it should be 1.5G instead of 1500M.
upvoted 0 times
...
Walton
3 months ago
The playbook looks good, but I'm not sure why the size is specified in M instead of G.
upvoted 0 times
...
...
Blair
4 months ago
I think it's important to understand the conditions for creating the LV with the specified size.
upvoted 0 times
...
Rima
4 months ago
This is a great question! The solution covers all the edge cases and handles the error scenarios well.
upvoted 0 times
Weldon
3 months ago
Yes, it's good to see that they considered different scenarios and provided appropriate responses.
upvoted 0 times
...
Terrilyn
3 months ago
I agree, the solution seems very thorough and well thought out.
upvoted 0 times
...
...
Margurite
4 months ago
I believe the provided solution in the explanation is clear and helpful.
upvoted 0 times
...
Nelida
4 months ago
I agree, it requires attention to detail to meet the requirements.
upvoted 0 times
...
Elmer
4 months ago
I think creating logical volumes with lvm.yml is a crucial task in the exam.
upvoted 0 times
...

Save Cancel