Today Red Hat announced a new pathway to become a Red Hat Certified Engineer (RHCE).
I recommend reading through the RHCE blog post and updated RHCE FAQ, but what other questions do you have about the enhanced RHCE path? We have Red Hat Certification team experts in the community, ready to answer all of your questions and offer guidance regarding RHCE.
If that is the case, then I wonder...
Why make (semi-) wholesale changes to the existing RHCE? Why not remove (or move into the RHCSA) the redunant (-ish) sections from the existing RHCE (IPv6, systemd targets, firewalld rich-rules) and put in "Ansible / automation lite?"
This , then, would seem to provide a transition into DO407.
It's a question of prioritization. Our aim is to focus on the skills and knowledge that are the most useful for the most people and oranizations. The structure of the certification program should reflect that. More knowledge is always a good thing but it's a bottomless well. What should skills and knowledge should people have first and foremost? When people certify with us and when organizations use Red Hat certification for management decisions, they are looking to and relying upon us for guidance on that question.
Automation is emerging as an essential skill. The escalating importance of automation is being driven by scale. Scale is in turn being driven by a planet full of people carrying smartphones, IoT, digital transformation in every industry, the growing ubiquity of data science methods and practices, the demands of AI and more. I suspect that it won't be long before industry will need fewer people who just know the right commands to type and more people who know how to automate processes.
Having a planet of people banging out one-off shell scripts will likewise not be enough. A cross-functional automation strategy and an automation framework that can work within such a strategy will also be increasingly necessary. The demands of scale are driving new deployment paradigms that mean server, DBA and network teams can't each approach automation atomically. Enter Ansible.
Our conviction that automation has surged in importance does not mean that the topics we have been testing and validating for RHCE are unimportant. They remain important. It comes back to what I mentioned above. We have a responsibility to curate and prioritize. Our existing RHCE exam and the System Admninistration III course will not be orphans.. They will find homes in new and existing offerings because they remain useful and relevant.
@RRR I don't know whether you work for Red Hat or not, but judging by your response, you're basically confirming that RHCE has been replaced with Ansible? I've not seen the official exam objectives, so if you can clarify that, I'd appreaciate it.
Yep, I work for Red Hat.
I'm reluctant to frame it as RHCE is now about Ansible. RHCE will become about automation. Automation is the objective and Ansible is how Red Hat does automation. The specific use cases would be Linux system automation but the principles and skills could be applied more broadly. An RHCE would have a head start on being able to automate other technologies that use Ansible for automation.
The new RHCE exam is not yet available, which is why you have not seen the exam objectives.
I'm an RHCA and IT manager , and i watched all of the new early access docs, and the new RHCE credentential will not be value much.
Currently when i interview a candidate with RHCE credential, i know that he is all around player that worked hard and familiar also with apache/mysql/bind/postfix/iscsi/smb/teaming/automounter etc..
Those skills are very important (and from my side - especially for ISP organizations).
I agree that ansible is important skill today, but instead of dropping lot of important materials, you can just add one or 2 chapters of ansible to the current great program, and make RHCE better than ever.
So for my opinion, the new program very disappointing.
I suspect knowing at least some of those skills won't go away in the new RHCE. I think we just might have to learn new ways to do those things at scale.
You must first understood how something works manually before you can begin to effectively automate it, after all.
I am not disappointed, I'm excited about a more efficient way to do these things.
All the best,