Deanna
Community Manager
Community Manager
  • 2,856 Views

Welcome to the Developing Advanced Automation with Red Hat Ansible Automation (DO374) group!

We are excited to launch a space dedicated to the Red Hat Training course Developing Advanced Automation with Red Hat Ansible Automation Platform!

To gain the most value from this group - click the "Join Group" button in the upper right hand corner of the group home page.

We encourage group members to collaborate in this group to discuss topics, ask questions, share best practices and tips, provide course feedback, and share their accomplishments as it relates to DO374.

Read more about Developing Advanced Automation with Red Hat Ansible Automation Platform here.

--
Deanna
Labels (2)
24 Replies
TM
Flight Engineer Flight Engineer
Flight Engineer
  • 1,789 Views

Hi,

I like this.
I've just added the EX374 to the list of certifications I'm aiming to get in the coming months.

Tshimanga

Chetan_Tiwary_
Moderator
Moderator
  • 1,770 Views

Hello @TM !

All the best for your exam preparation! 

Do check the exam objectives here : https://www.redhat.com/en/services/training/red-hat-certified-specialist-developing-automation-ansib... and prepare based on this from the DO374 course. 

This exam mainly  tests your ability to create Ansible playbooks to perform common system administration tasks. Please let us know in case you have any queries or any issues during the course progress and we will assist you!

Please also provide your valuable feedback to other learners as well who wish to go for this training and exam. 

0 Kudos
  • 425 Views

Hello, is the exam grading only focused on knowing how to configure and use Ansible, the Controller and the Automation Hub with best practices? Or is it also
directly grading Linux administration skills (such as logical volumes, networking, etc)?
Thanks in advance!
0 Kudos
Fran_Garcia
Starfighter Starfighter
Starfighter
  • 341 Views

Have a look at the exam objectives for EX374: https://www.redhat.com/en/services/training/red-hat-certified-specialist-developing-automation-ansib... .

 

This is about understanding and being able to develop new Ansible code that achieves a task, not about system administration.

0 Kudos
shashi01
Moderator
Moderator
  • 1,714 Views

Hello @TM 

That's fantastic news! Congratulations on adding the EX374 certification to your list of goals. It's always great to see someone committed to advancing their skills and knowledge. Best of luck with your preparations.

0 Kudos
Exorcista
Cadet
Cadet
  • 1,202 Views

Guided Exercise: Implementing Recommended Ansible Practices
final script, line
name: {{ web_package }}
I think must be
name: "{{ web_package }}"

Right?
shashi01
Moderator
Moderator
  • 1,196 Views

Hello @Exorcista 

Thanks for reaching out.

Right.

Suggestion to use name: "{{ web_package }}" is typically the safer and more reliable approach, especially in more complex playbooks or when the exact values of variables aren't known in advance. This approach minimizes the risk of unexpected behavior due to variable content.

0 Kudos
Trevor
Starfighter Starfighter
Starfighter
  • 1,189 Views

Hello Exorcista,

You are CORRECT!!!

On the line

         name:  {{ web_package }}

name    -> repreents the  key
{{ web_package }}     -> represents the value

When you start a value - in your example {{ web_package }} - by referencing a 
variable, you MUST quote the variable to create a valid YAML syntax!!!
If you do not quote the variable expression - {{ web_package }} - the YAML 
parser cannot interpret the syntax.   That is, the YAML parser will have to guess
if the item is a variable, or if it's the start of a YAML dictionary.  The YAML parser
doesn't play this guessing game!!!

Again, your are CORRECT - the expression {{ web_package }} MUST be
enclosed between quotes!!!  Failure to do so will get you something that you
don't care to see when excuting your playbook:  ERROR

 

Trevor "Red Hat Evangelist" Chandler
Chetan_Tiwary_
Moderator
Moderator
  • 1,183 Views

It is important to note that you only need to quote the variable expression if it is at the start of the value. If the variable expression is in the middle or at the end of the value, you do not need to quote it.

meaning: strings in YAML only need quotation if the beginning of the value can be misinterpreted as a data type or the value contains a colon (:), which could be misinterpreted as a key.

 

Join the discussion
You must log in to join this conversation.