Questionable EX374 Exam Objectives

[Trevor]

I was looking at the EX374 exam objectives, and I was quite surprised
to see that the first 2 objectives were related to Git:
- Clone a Git repository
- Create, modify and push files in a Git repository

I didn't see a connection with an exam that has Ansible Automation Platform
as its focus.  So, I took a look at the topics/subjects covered by the course
that prepares an individual for this exam, DO374, and I was NOT surprised
that there was nothing mentioned in the course outline about Git.

Anyone got any idea why those 2 Git objectives are included in the EX374
exam?  I'm not losing any sleep over this.  It's nothing more than a curiosity
query, so  I don't want to use too much bandwidth on this posting.

Peace!!!

[Dave_ross · Accepted solution]

Hello Trevor-

I think the main reason for git goals is that with Red Hat Ansible Automation Platform you can use CI/DC and in "Code Management" phase you need to store and version the playbooks, roles, pligins, etc., on the other hand "git " became standard as "source code control version", although in the market there are different flavors such as "gitea, gitlab, github, etc.", that is why in the laboratories we have real-life exercises, cloning the repositories, create new branches, commits, etc. Simulating a real case.

Regards!

[Trevor]

Hello Dave -

Thank you for the response.  Your explanation definitely
sheds some light on my query.

[dkcbk]

DO374 course covers git. It has entire chapter about git basics. I passed the EX374 exam 2 weeks ago. All I can say is be familiar with git. Read this chapter! It covers all you have to know about git for the exam.

[rainierteope]

Congrats!

How was the exam? Will taking this course be more than enough to get a good score?

[Travis]

@Trevor -

I would also like to add to the answer that @Dave_ross provided ...

This is the Ansible "best practices" course. So yes, one of the goals is CI/CD and getting version control around the code, but more importantly, it gets you ready for development as a team as well as for Ansible Automation Controller. 

The preferred and supported method of importing playbooks and using them from Automation Controller is through the use of a "Project" which ties directly to some type of version control. Git is an industry standard that a lot of companies and organizations use for version control, but as mentioned above, there are many "flavors", we happen to use Gitlab as we could easily set it up in disconnected classroom environments. 

The beginning RH294 Ansible course (RHCE) builds up to almost the point we are creating a true "project" in that we touch on managing large projects, inventories, and even get into roles and groups. The next thing is to take our code and reuse it as well as working with larger groups to maintain the automation environment. By leveraging something like "git" we are able to accomplish all of those things. 

If you look at things like Ansible Galaxy, the original account setup and method of publishing roles was the integration and SSO with Github to create the namespace and then "importing" the Github project for the roles you are publishing. It made logical sense to setup the DO374 with the introduction to Git and understanding of Git as the version control system is crucial to managing larger automation projects and is the primary way for Ansible Automation Controller to consume and import playbooks through the use of the "Project" which is just an import from a version control system.

[Trevor]

Travis -

As always, thanks for batting in the go-ahead run!!!

Love it!!!