• To ensure you get the most out of your CIN membership and stay connected with the latest updates, we are asking all members to update their community profiles. Please take a few moments to log in and: • Complete all sections of your profile • Review your current information for accuracy • Enter an alternative email address if desired (CIN requires your valid business email address for your training organization). Keeping your profile up to date helps us better serve you, ensures your account is correctly linked with CompTIA’s CRM, streamlines processes, enhances communication, and guarantees you never miss out on valuable CIN opportunities. Thank you for taking this important step! step!

CIN TTT Series: AutoOps+ V1

Join us for the new CompTIA Expansion Series certification launch for AutoOps+ V1! Our guest instructor, @Tyler Harris, will lead us through the six-session series covering the exam objectives and provide hands on examples as you strengthen your DevOps skills pertaining to cybersecurity. We will discuss how to cover the content with students and suggest various labs to let students gain hands-on experience as they prepare for certification.

CompTIA AutoOps+ validates your skills to automate, secure, and optimize IT operations across cloud and hybrid environments. As part of CompTIA’s new Expansion Series, AutoOps+ is designed to augment your core IT competencies with specialized expertise in automation, scripting, and infrastructure management. Gain hands-on experience to bridge traditional IT roles with modern DevOps practices.

What: CIN TTT Series: AutoOps+ V1
When: June 23rd - July 9th, 10:00 AM - 12:00 PM CT
Who: Tyler Harris, Instructor, ARIMA Consulting, LLC
Where: ON24
Register Here

View attachment 2637
Registered! Looking forward to this one.
 
I'm going through the on-demand for session 1 right now.

Bit of feedback: I'm not a fan that, for logging on Linux, the demo was done with Syslog and /var/log. That's a rather outdated way of working as most modern Linuxen use Journald for their logs. At least the big brand names which students will encounter in the enterprise do so.

I also didn't like that in the JSON vs YAML discussion, it was framed as "JSON is for data, YAML for commands". That's incorrect.

Both JSON, YAML as well as XML are formats for passing data, in the shape of key-value pairs, lists, dictionaries, etc. They all pass data. The fact that Docker uses a Dockerfile's data as build instructions does not make the YAML file "commands", just like Ansible playbooks aren't "commands".

Finally, in the on-demand recording, many times when Tyler's speaking about showing something on his screen, the recording shows the slides; not his screen. For example the Git-section, around the 88 minute mark.
 
Last edited:
I'm going through the on-demand for session 1 right now.

Bit of feedback: I'm not a fan that, for logging on Linux, the demo was done with Syslog and /var/log. That's a rather outdated way of working as most modern Linuxen use Journald for their logs. At least the big brand names which students will encounter in the enterprise do so.

I also didn't like that in the JSON vs YAML discussion, it was framed as "JSON is for data, YAML for commands". That's incorrect.

Both JSON, YAML as well as XML are formats for passing data, in the shape of key-value pairs, lists, dictionaries, etc. They all pass data. The fact that Docker uses a Dockerfile's data as build instructions does not make the YAML file "commands", just like Ansible playbooks aren't "commands".

Finally, in the on-demand recording, many times when Tyler's speaking about showing something on his screen, the recording shows the slides; not his screen. For example the Git-section, around the 88 minute mark.
Thanks for the feedback Tess. I appreciate the heads up about the slides\screen share in the on-demand.