This article is a part of my DevNet Expert Journey blog series
- Part 1: Decision
- Part 2: Intensive Study Period - Part 1
- Part 3: Intensive Study Period - Part 2
- Part 4: 1st Exam Attempt
- Part 5: 2nd Exam Attempt
- Part 6: This post
- Part 7: 4th Exam Attempt
Intro #
After my second attempt at the DevNet Expert lab exam, I was left feeling disappointed and a bit lost. I had managed to improve my score compared to my first try, but even a better score wasn’t enough to pass. It was frustrating - not because I didn’t work hard, but because I wasn’t sure where to focus next.
I kept asking myself the same questions: What should I study now? What am I missing? After putting so much time and energy into preparing, the uncertainty of what to catch up on felt overwhelming.
Turning Weakness into Strength #
I had a general sense of where the issue lay, but with my goldfish memory (I just can’t memorize text by heart) - it was difficult to recall the exam questions and identify which topics I didn’t fully understand.
However, I’ve come to see this as an advantage - weak memory for questions, materials from the exam is actually an advantage. That might sound a little crazy.
It forces me to truly understand the technology and base my answers on that knowledge, rather than memorization.
Finding Rest in Blogging #
In the first few days after the exam, I decided to finally catch up on my blog. I released a post describing my preparation process, and in doing so, I was able to take a much-needed break. To my surprise, I found myself really enjoying the process of documenting the journey.
Demistyfing Score Report #
Sometimes, it feels like a score report is an encoded message. It gives you a general idea of which areas need improvement, but it’s difficult to pinpoint exactly which technologies within those areas require the most attention.
After my second attempt, I started analyzing the score report in more detail. Section 1.0 stood out as needing improvement, so I turned back to the Learning Matrix and made a list of relevant books to go through again. Reflecting on my first attempt, I realized I hadn’t devoted enough time to reading, and perhaps I rushed through my preparation.
Unsure of which materials would best help me improve in Section 1.0, I decided to reach out to Stuart Clark, a key contributor to the DevNet exams and an author of Cisco Press books. I’d seen his contributions to the DevNet community and knew him to be both knowledgeable and approachable. Our conversation reassured me that my first impression was right - Stuart is not only an expert in the field but also someone who genuinely cares about helping others succeed.
In his response, Stuart provided me with a list of books and online resources tailored to help me strengthen my understanding of Section 1.0. His advice gave me the clarity I needed to move forward with my studies.
1.1 Cloud Deployment Design
Books:
Cloud Computing: Concepts, Technology & Architecture
Designing Distributed Systems
Kubernetes: Up and Running
1.2 Deployment Strategies
Books:
Continuous Delivery
The DevOps Handbook
Online Resources:
Martin Fowler's Blog on Deployment Strategies
1.3 Network Automation
Books:
Network Programmability and Automation
Mastering Python Networking
1.4 Git in CI/CD
Books:
Pro Git
Continuous Integration, Delivery, and Deployment with GitLab CI/CD
1.5 CI/CD Troubleshooting
Online Resources:
Troubleshooting CI/CD Pipelines
Specific Tool Documentation
Stuart, thank you for all advices I got from you! You are a rockstar, pal!
Countdown to the Third Attempt #
During the three weeks before the exam, I felt guilty because I should have worked harder on studying. But in truth, I spent most of my time doing anything but studying. My mind seemed to find a thousand more interesting things to focus on than going through the exam blueprint again.
Fortunately, many of the distractions I chose were still productive: I caught up on my blog, published new posts, and even learned a few new things, all while avoiding the social media rabbit hole. In fact, as I’m writing this, I realize that one unexpected benefit of the DevNet Expert journey has been my reduced time scrolling through pointless videos. Yay for small victories!
Coming back to the exam prep, the last three days were the hardest - mainly because of my mental state. I felt resigned, like I had done everything I could but didn’t know where to go next or what to focus on. That uncertainty chipped away at my confidence.
I kept asking myself:
Am I really ready this time?
The fear of never passing haunted me, and it’s a challenge I keep facing. The only way to push through was to stop overthinking and trust the process.
Even though it felt like I hadn’t improved much since my last attempt, I tried to let go of those doubts and remind myself that progress is often invisible in the moment. Daily steps can seem so small that they’re hard to notice, but I believed that those tiny changes would add up in the end.
The night before the exam, I decided to listen to the playlist that had been my soundtrack during my most intensive study sessions. It’s amazing how habits work - the moment the first song started playing, my mind clicked back into “battle mode.” A surge of energy washed over me, and I could feel my study habits kicking in. It reminded me of all the hard work I’d put in, and in that moment, I felt a sense of pride. I had stayed consistent, and that’s something to celebrate.
It’s important to celebrate your successes - recognize them, and don’t let your mind focus only on failures.
Same Travel, Same Sandwich, Same Anxiety #
I woke up at 3:30 to calmly prepare and make it to Warsaw Chopin Airport a few minutes before 5:00. Same old routine - again. Airport security, landing at Charleroi, catching the bus to Zaventem Airport in Brussels, then another bus to my hotel. It’s a pattern I’ve come to know all too well by now.
Once I arrived at the hotel, I checked in and immediately collapsed onto the bed. The travel had taken more out of me than I expected, and what I thought would be a quick nap turned into a three-hour sleep.
When I woke up, the familiar wave of anxiety hit me. I had to calm my nerves and double-check the route to Cisco’s office - just to make sure nothing had changed.
I headed to the office with Devvie to take a commemorative photo in front of the entrance.
No new constructions, nothing has changed. Everything feels exactly the same.
Here I am - again. This time, it cost me around $2300 (including flights and accommodation) to let Cisco drain me for 8 hours straight. My only guaranteed reward? A sandwich. Quite the expensive meal, if you ask me.
I’m not a rich guy who can keep coming back for these $2300 sandwiches. I’m here for the number - the certification that makes this all worthwhile… and to eat the sandwich, of course. ;-) If you read my impressions from the first attempt, you’ll understand by now - one sandwich isn’t nearly enough to be productive.
Returning to the Exam Room #
I woke up the next day, surprisingly calm. I packed my things, got ready, and headed to the Cisco Office. Even though I had eaten breakfast, the thought of the expensive sandwich kept creeping back into my head.
There were three of us this time. The proctor, who I had already met twice before, arrived in the lobby and invited us into a room I knew all too well. This was my third time meeting him.
With a smile, I joked that he must remember me by now. His grin confirmed it - yes, he definitely did.
He has likely seen thousands of engineers like me - people who keep coming back, trying again and again.
The procedures had changed slightly. While I’m not sure how much I can share, one piece of advice: don’t even think about sneaking in electronic devices or trying to cheat. I think the changes are positive - every certification number should have value. I don’t want this certification to be something that can be easily obtained by using dumps.
I’ve never understood why people cheat in exams like this. Sure, maybe you tricked the system and got your certification, but so what? You’ve cheated yourself. It’s easy enough to tell, after a quick conversation, whether someone truly earned that number. In the end, it will catch up with you.
Personally, I wouldn’t be able to look myself in the mirror if I passed by cheating. The certification wouldn’t mean anything. For me, this journey is about more than just a number - it’s about learning, challenging myself, and growing. I’ve spent nearly a year studying, and I’ve met incredible people along the way. Passing dishonestly would only ruin that.
Notes from the Exam Battlegrounds #
This time, during Module 1, I focused on keeping an open mind with each question. I carefully reviewed every detail from the supporting materials, hoping that all the studying would help me spot the important details faster. But unfortunately, the questions were still as difficult as in my previous attempts. The challenge wasn’t my lack of knowledge - it was the exam format itself.
I made sure not to forget about snacks. I snacked throughout the day, sipping water, and even took a painkiller when I felt a headache coming on (not that I’m advocating this approach - always use medication responsibly!).
Module 2, thankfully, was much easier. I felt like a fish in water. The tasks were straightforward, and nothing caught me off guard, which I owe to consistent practice. Still, I took my time and paid close attention to each task’s requirements and constraints.
Then, the inevitable question came:
“What sandwich would you like? We have a sandwich with ham, ham and cheese, cheese…”
“And to drink? We have Coca-Cola, Coca-Cola Zero, Fanta, Sprite…”
With a little more practice, I could probably recite the lunch menu by heart. I wish my memory for the exam notes were as sharp as it is for lunch options.
After lunch, I dove back into the tasks, feeling like I was working at lightning speed. My stress levels were at zero, and my confidence was high.
I finished all the tasks with about 1.5 hours to spare. I used the extra time to review everything from top to bottom, ensuring I had submitted all my work to the GitLab server. To make the process a bit more enjoyable, I grabbed a coffee.
After going over everything twice, I still had 45 minutes left. With nothing more to do, I finished the exam and said goodbye to the proctor. I told him, half-jokingly, that I hoped this would be our last meeting.
I headed back to the hotel, took a long stroll to the supermarket to refresh my mind.
Exam Results #
After leaving Cisco’s office, I felt extremely confident about Module 2, without a single doubt in my mind. However, I couldn’t say the same about Module 1. Although I knew I had performed better than my last attempt, uncertainty still lingered, clouding my thoughts.
I remembered a blog post by an engineer who had written about his own journey. He said he knew he had passed when he walked out of the exam room feeling 100% confident, with everything having gone as expected. On his previous attempt, even the smallest shred of self-doubt had resulted in a failing score. It reminded me of how much knowledge and preparation it takes to ace this exam - you have to be so sure of your answers that any doubt could be a sign of trouble. That’s exactly how I felt: completely secure about Module 2, but not quite with Module 1.
I hoped the score report would arrive sooner this time. After all, I knew I had performed better than my last attempt. The scoring tool should have been able to evaluate my work more quickly, right?
By 23:00, still nothing. I finally gave up and went to bed, convincing myself to stop obsessively refreshing my inbox.
The next morning, the first thing I did was check my phone - still no email. After breakfast, I headed to Zaventem Airport, then caught a bus to Charleroi, and finally took my flight home.
During the journey, my mind wouldn’t stop racing. My stress hit its peak as I began overthinking every detail, wondering what went wrong or if my gut feeling was right. I managed to calm myself, reminding myself that overthinking wouldn’t change the outcome. The exam was over and wasting my mental energy wouldn’t help.
Finally, as I was between airports, my phone buzzed. “Your score report is available.” The notification arrived later than last time.
I opened the email, bracing myself.
I failed.
When Support Makes the Difference #
Something inside me broke. It was an incredibly emotional moment, and I found myself overwhelmed by a mix of resignation, frustration, and uncertainty. I didn’t know what to do next.
The score report strengthened emotions even more. It was like a slap in my face.
I remember Andreas who said to me: “That was ’the best’ failing score I’ve ever seen”.
For a brief moment, I seriously considered giving up. But how could I, when so many people were standing behind me? When I had this blog, which might one day help someone going through a similar journey?
I know that I would have given up if it weren’t for the support of my family, friends, and the broader community.
So many people are following my journey. I’ve received messages - especially from CCIEs - telling me they understand my struggle, that they’ve been there too.
I realized I needed a proper break. At that point, it was impossible to make clear decisions because I was so emotionally drained. I knew I needed to step back and give myself time to calm down and recover mentally. I just wanted to let go of all the emotions that had built up.
The day after, I posted on LinkedIn about how I was feeling. The responses I received were a testament to the true power of support. It was essential in keeping me from giving up. I’m deeply thankful for every message - it meant more to me than you could know.
But I’m not sharing all of this to seek more encouragement. Rather, it’s a reminder that dealing with failure is tough, but it should never stop us from pursuing our goals.
A New Outlook on Failure #
I took a seat on the airplane heading back to Warsaw. There was a woman sitting next to me. I’ve noticed the scars on her arms. It was clear she was going through something far more serious than I could imagine, and the sight struck me deeply. Whatever had led her to this point, it was clear she was battling some heavy struggles.
In that moment, I realized my failed exam score wasn’t the end of the world. Sure, I had failed three times and lost thousands of dollars in the process, but was it really that important?
Imagine approaching her and saying, “Hey, I failed the exam that costs around $2,500 per attempt. This is my third failure, and it feels like the worst thing in the world.” The thought felt absurd, considering what she might be going through.
My “issue” was just a result of an ambitious goal I’d set for myself. Her struggles were much more significant. Recovering from pain like that could take months or even years.
I changed the narrative.
I didn’t fail - I just used a solution that didn’t work this time, and I was close to achieving my goal.
I didn’t lose thousands of dollars - I invested them in myself. Money comes and goes; it’s an asset that’s easy to recover. Recovering from psychological pain, though? That’s a far harder journey.
I realized I needed to appreciate more often what I have, what I’ve achieved, and, most importantly, the fact that I’m healthy.
As we were about to land in Warsaw, the girl beside me broke the silence.
“English? Polish?” she asked.
“Polish.” I replied.
She explained that she’d bought a book at the airport but couldn’t stand the author’s humor. “Having this book in my hands makes me so fucking angry. I hate this book full of bullshit. Maybe you’ll find some value in it. Do you want it?”
I was speechless. “Of course, thank you so much.” I said.
After that, she went quiet, and I found myself staring at the book, reading the summary on the back.
As the plane landed and we prepared to leave, I overcame my introverted nature for a moment and told her, “I had a really bad day, but your kind gesture made me feel better.”
“That’s the nicest thing I’ve heard in a long time,” she responded.
“I hope the good comes back to you,” I said as I headed toward the exit.
If you ever read this - I saw you suffering. I wish you all the best, and I believe you’ll recover. Thanks to you, I realized that my “issue” is not the end of the world.
I understand now that my mission to share knowledge must go on, and my DevNet Expert journey must be brought to completion.
Letting Go and Looking Ahead #
I let my emotions go and took some time to rest for the next few days. I stopped thinking about my previous attempts or what I would do next. Instead, I focused on things I enjoy that have nothing to do with the DevNet Expert Lab Exam.
After that break, I made the decision to return to Brussels on October 3rd for another attempt. This time, I had two months to not only rest but also prepare thoroughly. I’m looking forward to seeing the updated version of the exam - DevNet Expert Lab Exam v1.1.
My advice to anyone in a similar situation: Let your emotions go. Take a break, cool down, and revisit your thoughts when you’re in a clearer mental space. Trust me, it makes a huge difference.
See you in the next episode!