jeanne’s experiences with the jenkins certification beta exam

Main menu:

Topics

Recent Posts

Feeds

RSS Feed RSS - Posts

February 2016
M T W T F S S
« Dec   Mar »
1234567
891011121314
15161718192021
22232425262728
29  

Past Posts

Java/Java EE

JDBC

Other

jeanne’s experiences with the jenkins certification beta exam

February 27th, 2016 by Jeanne Boyarsky

On February 24th, I took the beta for the Jenkins Certification. This beta is different than beta exams from Oracle. In particular, it was only being offered on one day. The only choices you have are:

  • whether you want the morning or afternoon offering. It’s also only being offered in 12 cities (8 in the US and 4 in Europe). I chose the afternoon because I’ll probably be up late the night before. (yeah, I know. not ideal for taking an exam)
  • whether you want the Open Source or Enterprise version of the exam. I chose Enterprise because we use it at work and I like some of the features like templates.

This wasn’t a great time for me to study for or take an exam. The exam was held, literally the day after the robot is due for robotics team on which I mentor the programmers. This means I had little spare time and was somewhat tired. It was worth a shot though. I learned a lot getting ready for it. I also learned some things after the test when I tried them on Jenkins to see what happens in those scenarios.

For the non-beta, the exam is being offered starting in mid May.

 

How was the beta

The documentation said the exam was 60 questions in two hours for the Certified Jenkins Engineer and 90 questions in two hours for the Certified Cloudbees Jenkins Platform Engineer. Beta exams often have more questions and this one was no different. It was 85 questions in two hours for the CJE and 131 questions in two hours for the CCJPE. The time limit wasn’t a problem as most of the questions weren’t text heavy. Most people in my session for the CJE left between 90-120 minutes. I was the second to last to leave for the CCJPE with about 15 minutes left of time. I had time to go through all the questions twice.

We were advised to get there 30 minutes early to sign in and get ready. Glad I did. The first step was to “log into your Prometric account if you have one or sign up for one if you don’t.” Hmm. I knew I had a Prometric account. I used it for the old Sun exams before they switched to PearsonVUE in 2011. I also used it for the TOGAF exam in 2013. They had you in a restricted window so you couldn’t use then net. I tried what I thought might be my user id and password. After a while, they let me open a regular browser to try. I checked my email, I tried to login. Nothing. Eventually I tried registering for a new account. And it let me do so with the same email I know I used for the 2011 and 2013 exams. I suspect Prometric does separate accounts for each vendor (Sun, The Open Group, Cloudbees, etc).

Then we actually took the exam. They allowed using scrap paper and handing it to the proctor at the end. Which is good. I like to write stuff down. And since it was a beta (rather than administered by the testing center), it was paper and pen rather than reusable markers!

The actual exam was like your typical certification test. Some radio buttons. Some checkboxes where they tell you how many are correct. It was also cool to hear people chatting before the exam too since it was mainly Jenkins power users in the room.

How did I do

I passed! I am in the first batch of certified folks for this exam ever!

I’ll edit this post in 4-6 weeks when I have my score. I don’t think I passed. It’s impossible to tell for a beta though as it depends on which questions they choose to include in the exam and what the passing score ends up being.

For one thing, I chose the wrong exam if my goal was to pass. I learned more taking the CCJPE than if I had taken the CJE. But I haven’t used the Cloudbees Jenkins Operation Center in Production and knowing the Enterprise Jenkins parts well wasn’t enough to compensate for that. I’m glad I chose the CCJPE though. I learned more that way.

For another, I didn’t study in enough detail. I knew the scenarios I work with really well. I knew the concepts really well. I knew the things I played with at home studying. But then there were the parts I didn’t know. That was not enough time to study issue. While I did review flashcards at the robotics lab, I choose to prioritize mentoring the programmers on the team over hands on studying details about Jenkins.

How did I study

I recommend spending WAY more time playing with Jenkins features you are unfamiliar with to study for the exam. I didn’t do that due to lack of time. What I did do in the limited time I had available to study:

  • Week 1: 1/27-2/2
    • Decided to take exam
    • Got three out of five of the practice questions right from the PDF (they were easier than the majority of the questions on the exam by the way)
    • Read objectives in detail
    • Self assessed my strengths and weaknesses
    • Installed Jenkins locally including correct plugins
    • Played with plugins, made study outline and flashcards for chapter 1 of objectives
    • Started reading “Jenkins: The Definitive Guide” (I already owned this book and never got around to reading it)
  • Week 2: 2/3-2/9
    • Reviewed flashcards every day
    • Finished reading “Jenkins: The Definitive Guide”
    • Installed CJOC locally
    • Played with plugins, made study outline and flashcards for chapter 5 of objectives
  • Week 3: 2/10-2/16
    • Reviewed flashcards every day
    • Started reading “Continuous Delivery” (another book I owned and never got around to reading)
    • Played with plugins, made study outline and flashcards for chapters 2-3 of objectives
  • Week 4: -2/16-2/23
    • Reviewed flashcards every day
    • Finished reading “Continuous Delivery”
    • Played with plugins some more (fairly minimal though as the robot was due on 2/23) and I spent a lot of time in the lab
  • Exam day: 2/24

The study materials I created

Feel free to use these as a starting point. You need more hands on experience than just reading a study guide though.

I wrote both of these entirely before taking the exam. There are some objectives in the word document were I wrote that I wasn’t sure what they meant. After taking the exam, I’m still not sure! Hopefully these objectives are re-worded to be clearer.

Comments

Comment from Francois
Posted: February 28, 2016 at 11:09 am

Jeanne,

Congratulations for this great article and for taking the test last Wednesday. Thank you as well for taking the time to share these additional tools/guides.

I have had the chance and the privilege to supervise the creation and implementation of the Jenkins Certification program at CloudBees (both CJE/Jenkins open source and CCJPE/CloudBees Jenkins Platform). The exam last Wednesday was the first time when candidates were actually able to take these tests, beyond the numerous internal reviews and alpha tests at CloudBees.

I’d like to highlight a few points from your article. First, certification requires preparation and self-assessment. This, by itself, is already a very interesting added value. It “pushes” each candidate to better understand what he/she truly knows and what he/she doesn’t. As we all know, before aiming high, one needs to assess him/herself as honestly as possible. The second point that I always like to highlight is that the test itself is an assessment. Of course, the ultimate goal is to be certified, hence the need to prepare and study, but a failure is not a disaster. It is simply a message that tells you in a relatively precise manner what/where you need to improve. The last and third point I’d like to underline is related to study versus practice. This Certification is definitely not about attending a training and/or reading a book and then be ready to take the test. Of course, trainings and books are definitely great ways to learn. But nothing replaces hands-on practice. In short, you need both. And because this Certification is a *professional* certification, we have made sure that exam questions were in line with this dual objective of knowledge and practice.

This is what matters in the end, finding practical ways to get better at what you (like to) do. Individuals who accept the challenge of certification will therefore benefit, ie it will make them better. As a consequence, the community of Jenkins users at large will benefit, as well as all the organizations, be they corporations or not-for-profit, which employ such individuals. This is the virtuous circle of certification.

One side note about next steps of the Certification program… Last Wednesday was a one-off event where people had to come at a predefined date/time and in specific locations (12 in the US and EU). Moving forward, the Certification exams, both CJE (Jenkins open source) and CCJPE/CloudBees Jenkins Platform) will be available through Prometric, a well-known Test/Certification service provider. This means that candidates will know take the test individually, in the test center of their choice (hundreds of them around the world) and at a date/time of their choice too. Registrations will open on March 15 and first available test date will be May 12.

Thank you again for this post.

Francois Dechery
VP Customer Success
CloudBees

Comment from Jeanne Boyarsky
Posted: March 28, 2016 at 9:03 pm

I passed!

Comment from Tracy Conn
Posted: March 28, 2016 at 9:11 pm

Congrats Jeanne!

Comment from Mohit Gadkari
Posted: May 12, 2016 at 2:30 pm

Thanks a lot Jeanne, I gave CJE exam today and your notes really helped me to pass the same.

Comment from Kalyan Ram Koduru
Posted: May 13, 2016 at 9:38 pm

I took my CJE exam on 05/13 and passed 🙂 To be honest, I use Jenkins every-day and did not prepare for the exam at all 🙂 However, I realized that i could have scored little better if I’d prepared for the exam. Most of the questions are really interesting and had to read twice to ensure that i knew the exact answer.

Comment from angela
Posted: May 23, 2016 at 9:36 pm

whats the passing score for this exam.

Comment from Jeanne Boyarsky
Posted: May 23, 2016 at 10:57 pm

Angela,
I don’t know the passing score as Cloudbees hasn’t announced it. I do know someone passed with a 72%: https://pbs.twimg.com/media/CiT-udQUUAAKeoD.jpg

Comment from Saranya
Posted: May 28, 2016 at 7:27 am

As I checked with cloud bees team, the passing score was mentioned by them as 66- 67 %

Comment from Jeanne Boyarsky
Posted: May 28, 2016 at 1:56 pm

Thanks for finding that out and sharing Saranya!

Pingback from Becoming a Certified Jenkins Engineer in One month – Successful Programmer
Posted: June 2, 2016 at 2:17 am

[…] my Java certification coach Jeanne Boyarsky who had the same time frame as I do and she was able to pass the beta exam for CJE. I trust her because Jeanne along with Scott Selikoff wrote two study guides that are precious for […]

Comment from Murali
Posted: July 24, 2016 at 10:13 am

I took the CCJPE exam last week and passed. Thanks to Jeanne for her study notes. They were very helpful. It is advisable to take the 14 day evaluation version of CJE/CJOC (I used the Docker version), if you want to get hands-on practice on the section#5 content.

Comment from Claus Nielsen
Posted: September 1, 2016 at 1:34 pm

Thanks a lot for your notes ! I’ve worked with Jenkins since it birth (and Hudson before) – I only read your notes and passed with 83% – without your notes I would not have passed. THANKS !

Comment from Mahtab
Posted: March 12, 2017 at 5:13 am

Hey Jeane, just to confirm. We need to pass only this certification to get Certified Jenkins Engineer cert.

Comment from Murali Bala
Posted: April 23, 2017 at 9:39 am

Jeane, Thanks for the wonderful write up and study notes. I just passed my CloudBees Jenkins Certified Engineer Exam based on 2.19.4 last week.
It was not an easy exam by any stretch. Folks preparing for the exam will find this Gitbook very useful – https://www.gitbook.com/book/muralibala/cloudbees-certified-jenkins-engineer-2017/details

Write a comment