DevNet Expert Exam Tomorrow

•

It's the day before my #DevNet Expert. Time to reflect on prep and topics I am weak or strong on in the blueprint, as well as my testing strategy. - Prep: should've prepped more - Weak: NET/REST-CONF, YANG, NSO, pyATS - Strong: Docker, k8s, OWASP, design - Exam Strategy (!) 🧵

Prep Did not get nearly as much prep done as I would've liked. This is not unexpected. Life has a way of not considering your plans. That being said, given reduced prep time, it was important on key topics. I set my exam date as early as possible as a focusing strategy.

So, I focused using 3 strategies: - Skip what I felt confident in - Quick recap of things I've used a lot, but not recently - Spend the most time on weak topics

Weak area: NETCONF/RESTCONF/YANG If someone is strong in these areas, great job. I'm solid on the foundation, but it is always time-consuming due to the convoluted nature of the modeling, tooling, etc. This is something that ultimately just gets better with practice.

Weak area: NSO NSO is, at this point, pretty hyperspecific tech in terms of places using it. It is what it is. Tried to get better and build my hands on, but time only permitted so much. Getting more familiar with creating services was key, and I did my best.

Weak area: pyATS/Genie I've just rarely used this and it is another big weakness. I never got around to getting deeper on this.

Strengths We don't need to get too deep into strengths as these are just topics I've spent a lot of time on, hands on or otherwise, or are likely to just be question/concept oriented in the exam and can just brush up on concepts.

Docker I use Docker as a default for basically any webapp or complex script I write K8s I use k8s to deploy microservice applications and enjoy the tech so mess with it probably more than necessary

Strengths OWASP & Design I can thank the Secure Code Warrior challenge @CiscoDevNet put on during #DevNetCreate for this. Great hands-on to get familiar with the OWASP Top 10 and examples. Concepts I deal in this area daily, so most concept-topics are pretty easy.

On to strategy, which is the key for tomorrow. Fortunately, I've taken and passed a CCIE before and many of the strategies used there can apply here.

Exam Strategy - Time management - Momentum/easy wins - Don't ace it, just pass it - Take advantage of the exam format - Strategic documentation usage - Grade yourself - Personal brain dump

Time Mgmt Time mgmt is key in any exam like the CCIE. You can't spend too long on one task. If you are, move on and come back to it later. If you're feeling bad about multiple "failed" tasks, go work on a task you are confident of.

Momentum This means you should review all tasks in the config section quickly before beginning - making a list of the general topic area noting what your "easy wins" are likely to be. When you feel defeated, go to an "easy win" for you to rebuild confidence and momentum.

Momentum, cont'd You should use your list to check off tasks as you complete them, noting your confidence and if you performed needed verification. Sometimes you may not feel you have time to verify, so you can note to try and come back at the end to do so.

Bonus This list/chart can now also be used to self-grade your test. The exam may tell you point values. If so, you can get a general % idea of your grade to help you mark progress. E.g. if your stuck on a 2 task, but there's an easy win that is 6 points... do it!

Don't ace, just pass No one will know if you ace the exam (not even you), so there's no need to ace it. A pass is a pass!

Don't ace, just pass Don't worry about finishing tasks that you don't think you need. If I'm terrible at pyATS and that's 4 points, I probably don't need it if I can finish most of the other tasks. Skip it! Try it at the end if you have extra time.

Don't ace, just pass Fun fact - I straight up didn't even attempt 2 full sections in my CCIE security when I passed the exam! No one knew until now! Your objective is a pass, not a 100%!

Exam Format This can be a detriment if you let it. Don't. Take advantage! For the DevNet Exam, we know there is a 3-hour question-based section and 5-hour "config." The 5-hours are hard set, EVEN if you finish the questions early. So don't waste the time!

Exam Format Say you finish the questions in 2.5 hours. Take the remaining 30 minutes to open up or read through some documentation of things your weak on. Doc tabs may even stay open between different sections, what a bonus that would be! So, take the extra time.

Exam Format After doing so practice prep, give yourself some time to take a bio break or simply walk around for a few minutes. Get some coffee. Let your mind and eyes rest, they likely need it. Take some deep breaths.

Strategic doc usage As mentioned in exam format, prep documentation tabs at once. My expectation is to need them pretty heavily because the exam topics are break and syntax is hyper-specific in programming. Autocomplete is less of a thing, but at least you have IDE tips.

Strategic doc usage That being said, be strategic in using the docs. Sure, you could use it on every task to be 100% confident. But, don't be surprised when you don't finish half of the tasks. Choose your doc battles wisely.

Bonus At lunch about 60-90 minutes before the end of the day, review your task chart and do a quick self-grade. See where you stand and see if you need to adjust your strategy. If near the end you aren't going to have enough points, tackle some remaining high point tasks.

Brain dump As soon as you're done and get to your car, hotel, airport, bench outside, etc. you should do a brain dump into a notebook or document on everything you can remember on the exam to help you the next time. Don't share as it violates CCIE NDA - this is yours only

Remember! - KEEP MOMENTUM! Find your easy wins - You just need to PASS IT, NOT ACE IT - Leverage exam format for "extra" time - Don't overuse the docs, time is your enemy - Grade yourself periodically - Brain dump immediately!

Final tip: If you fail, don't worry - many came before you and many will come after. Look at your exam results grading rubric (albeit vague), strategize, plan, and circle back.

Hopefully, this has been helpful and not a useless rambling.