RedHat EX294 Exam - Topic 5 Question 21 Discussion

Actual exam question for RedHat's EX294 exam

Question #: 21
Topic #: 5

[All EX294 Questions]

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

HOST=

MEMORY=

BIOS=

VDA_DISK_SIZE=

VDB_DISK_SIZE=

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

AExplanation:
Solution as:

Show Suggested Answer

Suggested Answer: A

by Kris at Jan 09, 2023, 09:15 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Juliana

4 months ago

I thought we were using /etc for config files, not /root.

upvoted 0 times

...

Jolanda

4 months ago

This seems straightforward, but double-check the permissions!

upvoted 0 times

...

Roselle

4 months ago

Wait, are we sure about the path for specs.txt?

upvoted 0 times

...

Hollis

4 months ago

Totally agree, that's the right way to start!

upvoted 0 times

...

Howard

4 months ago

Just create the specs.empty file with those variables.

upvoted 0 times

...

Dominque

5 months ago

I recall something about using `copy` and `lineinfile` modules, but I can't remember the details. I hope I can figure it out during the exam.

upvoted 0 times

...

Ling

5 months ago

I'm a bit confused about how to edit the specs.txt file with the ansible facts. Do we use the `template` module for that?

upvoted 0 times

...

Leota

5 months ago

I practiced a similar question where we had to copy files to remote nodes, so I feel a bit more confident about that part.

upvoted 0 times

...

Alesia

5 months ago

I think I remember how to create the specs.empty file, but I'm not entirely sure about the exact syntax for the playbook.

upvoted 0 times

...

Eleonore

5 months ago

Ah, I see the issue now. The ArubaOS-CX switch is expecting plain-text authentication, but the third-party switch is likely configured for a different type, like MD5. I'll need to update the third-party switch's configuration to match the ArubaOS-CX switch's requirements.

upvoted 0 times

...

Barb

5 months ago

I'm feeling pretty confident about this one. The key is to use a method that allows you to collect only the order details, rather than requiring the customer to provide additional information. Option C with the Connected App Handler Apex Plugin class looks like the most direct solution.

upvoted 0 times

...

Norah

5 months ago

Okay, I've got this. The different levels of involvement are primarily divided into governance/management and responsibility/accountability. I'm confident that B is the correct answer.

upvoted 0 times

...

Alyce

9 months ago

I wonder if the exam will ask us to include error handling in case the remote nodes don't have the necessary permissions to write to the /root/specs.txt file. Gotta be prepared for those edge cases!

upvoted 0 times

...

Owen

9 months ago

This is a solid question. I'm sure the correct answer will involve using the appropriate Ansible modules to gather the system facts and then update the specs.txt file accordingly.

upvoted 0 times

Bonita

8 months ago

The solution provided in the explanation looks like the correct approach to complete this task.

upvoted 0 times

...

France

8 months ago

Yes, we should also use the setup module to gather the system facts before updating the specs.txt file.

upvoted 0 times

...

Caitlin

8 months ago

After that, we can use the lineinfile module to edit the specs.txt file on the remote machines.

upvoted 0 times

...

Rose

8 months ago

I think we need to use the copy module to create the specs.empty file on the local machine.

upvoted 0 times

...

Terrilyn

10 months ago

Haha, I bet Bob's gonna have a tough time remembering all those variable names. Should've called them something more intuitive, like 'server_memory' and 'boot_disk_size'.

upvoted 0 times

Nu

9 months ago

Maybe Bob can create some aliases for those variables to make it simpler.

upvoted 0 times

...

Talia

9 months ago

I agree, using more intuitive names would make it easier to manage.

upvoted 0 times

...

Scarlet

9 months ago

Yeah, those variable names are a bit tricky to remember.

upvoted 0 times

...

Johnathon

10 months ago

Wait, why do we need to create a separate file called specs.empty? Isn't it simpler to just write the facts directly to the specs.txt file?

upvoted 0 times

Tamar

9 months ago

Having a separate file also allows for easier troubleshooting and debugging if needed.

upvoted 0 times

...

Laticia

9 months ago

Creating a separate file makes it easier to manage and update the facts in the future.

upvoted 0 times

...

Trinidad

10 months ago

It's a good practice to have a separate file for organization and clarity.

upvoted 0 times

...

Cyril

10 months ago

Looks like a straightforward Ansible playbook to create a file with system information. I like how it uses the appropriate variables to capture the facts.

upvoted 0 times