Backgroound Image

CCDE Journey (Take 2)

Back in 2020 I was planning to take the CCDE exam, but those plans were derailed by a little thing called a global pandemic. With test centers closed for an unknown period, I decided to wait until things calmed down before I started to really dig into it. Then, in 2021 it was announced that the CCDE was moving to version 3.0. I didn’t want to get end up in a race against the sunset of the v2 exam, which meant waiting until the release of v3. Add in some travel, a new job, and a handful of other events that distracted from my CCDE plan, and here I am, ready to give this another go.

I’m planning to continually add content as I’m learning new things, both as a way to help me remember what I’m covering, and hopefully in a way that might help others that are either working towards the CCDE or just looking to pick up bits of information along the way.

Study Materials

I have a handful of material that I’ll be using for the CCDE prep.

Primary resources:

Additional resources:

The CCDE covers a massive range of topics. It will be a fun process working my way through all of it!

Cisco Live Las Vegas 2022 recap – The Good, the Bad, and the Tech

This was my first time attending Cisco Live in person, and it was a wild time. In addition to the normal Cisco Live event, I also had the opportunity to participate in a few extra events. I attended the CCDE Techtorial (detailed post on it coming soon), there were several Cisco Champion events, and I was a delegate at Tech Field Day Extra (TFDx) –

It was a jam-packed week with a ton of walking, countless conversations, and enough information to make my head hurt. I’ve attempted to distill down my thoughts on the event and provide recommendations from a first-timer to future first-timers.


If you aren’t familiar with Cisco Live, it’s a major IT industry event that Cisco puts on Every year (virtually in 2020 and 2021) and there are versions of it run globally. The US-based event is the largest, but there are also events in Europe and Australia. I attended the event in Las Vegas at the Mandalay Bay Convention Center from June 12th through 16th. Hundreds of breakout sessions are available, covering the entire Cisco solution portfolio. The sessions can be very high-level, explaining the basics of a technology, or very deep and technically focused. People from all over the world attend, and I believe the 2022 attendance was near 15,000.

The Good

1. The people

I can’t say enough about how much of a factor the social side of Cisco Live was. I spent countless hours talking to people outside of sessions. I had the opportunity to meet so many people, made even more special after two years of quarantine. Many of those people were from other countries, and I likely wouldn’t have had the opportunity to meet them otherwise.

Just to name-drop a bit, I had the chance to talk to Cisco giants Peter Jones, and fellow Champions Daren Fulwell, Mark Sibering, Sijbren Beukenkamp, David Peñaloza Seijas, Bill Burnam, Dustin Gabbett, Joe Houghes, Kenny Paula, Robb Boyd… this list could go on by a few dozen more people… plus the people that I was able to hang out with on the TFDx side (many are also Cisco Champions) – Ben Story, Micheline Murphy, Pieter-Jan Nefkens, Jody Lemoine… (huh, that list is all Champions)…  Again, the list could go on. I also had the chance to meet people I’d recorded Cisco Champions Radio episodes with, including Jason Gooley, JP Vasseur, Shai Silberman, and Carlos Pereira.  I’ve probably not even listed half of the people I should have.

There were definitely moments when I was in awe of the people I was talking to. I have books written by these people on my shelf. I’ve watched their training material. As a professional geek, it was awesome to just be in the same room, let alone actually talking to these people.

I had the chance to talk with a few people about ThousandEyes, and I could discuss how I’ve used it with peers and learn how they are using it. We discussed challenges and how we overcame them. I talked to people about some of the announcements Cisco made and learned from those different perspectives. I listened to questions people asked during sessions; sometimes, it was a question I was wondering myself but hadn’t thought to actually ask it.

The “live” aspect of Cisco Live was massively beneficial. The conversations were far more interesting and engaging than pre-recorded or virtual meetings. The opportunity to sit in one of the lounge areas and talk shop (or talk about anything else) with peers from many different backgrounds was truly awesome.

2. The people (yes, we just did this)

Told you I couldn’t say enough about the people! The Cisco Insider Champs team (Amilee San Jaun, Breana Jordan, Britney McDaniel, Danielle Carter, and Lauren Friedman) did an awesome job getting us access to special sessions and behind-the-scenes access. They truly made the experience better! Much of, if not all, of the above, was made possible because of the Cisco Insider Champions team. I can’t stress enough how much value came out of the community connections, and I am extremely thankful to be part of it.

Shameless plug: If you’re interested in joining the Cisco Insider Champions program (or the Cisco Insider programs -Advocates, User Group, and User Research), you can find more info here: The Champions applications are typically available in the October-December timeframe.

The Advocates program can be joined at any time here:

If you join either program, please let me know so I can follow you.

3. The techtorial session

The techtorial was a premium session held on Sunday, the day before Cisco Live officially kicked off. It was a 4-hour deep-dive session, and it was amazing! Having that much time really allowed the presenters to go into depth with the material, and there was enough time to have an interactive discussion. Those sessions are also very focused, which means there’s not really a level-setting/marketing part of the session. From a value-per-hour standpoint, I think I got a lot more out of the techtorial than I did the normal sessions.

4. Swag.

I have to mention the swag. Sure, I didn’t get sent home with the thousands of dollars of swag that are given out for the Oscars, but I was happy. A few shirts, socks, and a wide assortment of other random bits. I will say that I’m disappointed that the AMD booth wasn’t handing out Threadripper Pros to everyone that stopped by.

5. Did I mention the people?

Yup, back to the people. I had the opportunity to randomly belt out Metallica lyrics with Kenny Paula and the #metaldevops godfather, Jason Gooley. I ate many a stroopwafel that made the trip from the Netherlands. I watched a Dutch man hit the bell in one of those carnival strength games with the oversized mallet. I made solar battery charging kits with fellow Cisco Champions and the awesome Champs team. I got my selfie with Robb Boyd.

The Bad

1. Timing

I think Cisco Live could easily be three weeks long, and I still wouldn’t do everything I wanted to. There were a lot of sessions that I couldn’t make because they overlapped with other things. I only visited a few vendor booths. I didn’t do any labs, play capture the flag, or do activities in the DevNet zone. I would have loved to have had more time to engage with more people, attend more sessions, talk to different vendors, etc. Trying to fit everything in is a challenge, and as a first-timer, I found that overwhelming in many ways. I also found that I was spending time doing things that weren’t as valuable of a use of time, like the Cisco Live challenge game. I thought it would be cool to win a prize, so I did some of the activities and quizzes to get as many points as possible. Well, I didn’t win, and I probably wasted an hour or two on it. Looking at the leaderboard, I’d bet the people at the top spend a significant amount of time on it, and though the prizes were nice, I don’t think it would have been worth the time. Next time I’ll try to prioritize better what I want to do and limit time spent on anything else.

2. The walking

The walking itself wasn’t really the problem, but the time spent walking was. I stayed at the Luxor, about a 17-minute walk from the hotel lobby to the entrance of the conference center. I bought some stuff at the Cisco Store and wanted to drop it off in my hotel room before I went to my next session. It took 45 minutes to go from the store to my hotel room and back to the next session room. Next time I’ll try to get a room closer to the conference and better plan my trip to the store.

3. The on-site exam

When I registered for Cisco Live, I was really excited to get a free exam. There were a few problems, though. First, there wasn’t an exam I had been preparing for, so I just picked one I thought I’d have a chance to pass with minimal study. Second, when you think about it, an exam might be $400, but when you compare that to the cost of Cisco Live, you’re losing a few hours of the conference to take a test that you could take any time. If I could schedule my exam for a time that didn’t interfere with the conference, it might be a different story, but those spots go fast. Third, trying to get an exam done during the conference just adds extra stress that’s not needed. Next time I don’t plan to bother with the exam. I’ll probably take a look at the schedule, and if there’s a great spot open, I might go for it, but it would be quite low on my priority list.

4. The parties

I’ll admit, I’m not much of the party type. The appreciation event concert was Britany Howard and the Dave Matthews Band. Though both might be great acts, they aren’t my style. The food at the celebration wasn’t great either. The CCIE party (I was a +1, I’m a long way from an IE) wasn’t a big hit for me either. That said, I know there were plenty of people stoked to see DMB, and they had a blast at the parties. They were a great opportunity to hang out with people, and many great conversations were had. Next time I’ll approach the parties as more of a networking event than a concert or similar event. Unless they manage to get a concert lineup with Jonathan Coulton (check out Code Monkey) and Psychostick (check out Blue Screen, which also happens to be one of the best music videos ever made).

And The Tech

Cisco Live is always buzzing with new product launches, announcements, and a massive amount of information. This year was no different. The biggest announcement was the ability to monitor Catalyst switches in the Meraki dashboard and even convert them to running Meraki code so they would be fully Meraki-managed. Plenty of other awesome stuff happened, but I want to focus on the event’s overall experience. I’ll save the tech details for another post.

Aside from product announcements and sessions, there’s also the World of Solutions. Essentially, that’s the show floor of the event. Cisco had huge spaces dedicated to different things like DevNet, Emerging Technologies and Incubation, WebEx, labs, etc. There were also dozens of other vendor booths, some even giving their own sessions on the show floor.

Recommendations for Future Attendees

  1. Wear good shoes. It’s a lot of walking! I think I calculated something like 30+ miles of walking during the week.
  2. Bring a water bottle and stay hydrated. With all the walking, the Vegas heat, and the overall dryness, it’s easy to get dehydrated. Add in air travel and perhaps some alcohol consumption, and that’s a recipe for disaster. There are plenty of water coolers, but sometimes it was challenging to find one that wasn’t empty. Bring a water bottle, fill it when you can, and make sure to drink enough water.

Now that the basic human needs are covered, on to the actual conference recommendations.

  1. Make time to talk to people. Sessions fill fast, making it feel like you need to register for as many as possible. Don’t fall into that trap. Sign up for the sessions you really want to attend, and then use the open time to talk to people. Most sessions are recorded, but the chance to talk to people isn’t.
  2. Don’t be afraid to talk to someone. See your favorite blogger, podcaster, and beard? Go ahead and say “hi” to me. And if I’m not your favorite, that’s fine. Say “hi” to me, and them too. Did you hear someone ask a question in a session, and it sounded like they might be in a similar position to you? Talk to them. Maybe they’ve solved a problem you’re working on. Maybe you have some advice you could give them.
  3. Don’t focus on the parties. Sure, they can be fun, but after an 8+ hour day of talking and tech sessions, if you need some downtime, take it. Maybe doing back-to-back-to-back 16-hour days for a week is something you can do, and if so, go for it. If not, that’s cool. The parties, swag, and all of that are great, but if you risk burning yourself out, make sure to pace yourself.
  4. Swag is great. Prizes are also great. Neither should be the focus of a trip to Cisco Live. The cost of the conference pass, hotel, and airfare far outweigh the value of the swag. There’s always joking about finding the vendors with the best swag, but really, look for the vendors that can help you. Talk to them. Talk to vendors you’ve never heard of. Maybe they have a product that can solve a problem you have, and you didn’t even know it existed. If it ends up not being a good fit, move on. There are plenty of vendors for a participant to talk to and plenty of participants for vendors to talk to, so if there’s no value, then it’s better for both of you to move on.
  5. If you need approval to make the trip, highlight how Cisco Live is a lot more than sales demos and swag. You have the opportunity to meet a lot of people and learn about what they are doing. The odds are pretty good that you can find people that have solved whatever challenge you might be facing or at least people that could provide useful information.

Final Thoughts

If you have the opportunity to go, do it! It was an awesome experience, and I can’t wait for my next chance to attend!

I can’t stress the value of the conversations enough. Speak up in sessions. Ask questions. Track down people if you need to. (Twitter can be a great way to find people), but talk to people. You can get much more focused answers and better insight with direct conversations. Plus you might find a friend.

Have questions? Have Cisco Live tips? Drop them in the comments, or reach out to me on Twitter @Ipswitch

I might have missed or misspelled some important names. If I did, I’m sorry. Let me know, and I’ll update this post. If you want me to add Twitter and/or LinkedIn links for you, send those over, and I’ll be sure to add them.

I Passed the Cisco DevNet Associate exam and Joined DevNet Class of 2020!

 I’m excited to announce that I passed the DevNet Associate (200-901) exam, and with that I’ve joined the DevNet Class of 2020!

 To start with, for those that don’t know, DevNet is the Cisco Developer Network, focused around developing solutions in the network space.  It focuses heavily on programability and automation of numerous Cisco products.  The DevNet Class of 2020 includes everyone that passes a DevNet exam during the inaugural year of the program.  Originally, the program was slated to end December 31st of 2020, but it was extended to February 24th, 2021.

I found this exam to be simultaneously one of the most challenging and fun certifications I’ve attempted.  With a near 20-year career in IT I’ve never really done much programming.  I’ve made a few HTML sites over the years, and the odd batch or PowerShells script, but never anything more than that.  In many ways this exam broke into a lot of new areas for me.  For network engineers looking to get into automation I thought this was a great way to start, and for people new to IT this is a great way to get into the automation and programmability mindset early on.

How I prepared

First things first.  Learning Python.  Coming from the network background this took some work, but it really wasn’t too bad.  I started with some YouTube videos and books.  One site specifically that I used a lot was, as well as the YouTube videos from the same author.

I found the repetition of the labs got boring after a while, so I started to look for beginner projects.  One project that I worked with was a Python clone of the classic Pong game.  However, instead of just duplicating the code I worked on adding additional functionality.  Players could enter their names, and select their paddle colors, as well as set the game speed and score limit.  I added some input validation to make sure the entries didn’t cause the game to crash.  For me, it was important to actually work with the code and play with the options instead of simply copying what someone else said.

Once I felt I had a decent handle on Python I started reading the DEVASC 200-901 Official Cert Guide, which of course hit a lot of the same Python info I was working with already, but added depth.  The book goes into a lot of other things like Git and API configs.  Which, of course, meant getting Git set up and testing committing, branching, and merging code.

The Cisco DevNet site has access to sandboxes that can be used to test out API calls.  Since I don’t have DNA Center, ACI, Meraki, Webex, FMC, etc. all running in my basement it was really good to have access to the sandbox.  I worked through learning the API methods via curl, Postman, Python, and SDK.  This meant a lot of repetition.  The authorization methods between the Cisco platforms changes, and that means the way you interact with the API needs to change.

Looking back, I wish that I had merged the Git exercises more with the API work.  I could have built out a repository of all the tests I was working with.  So, as a recommendation, use Git early, and get in the habit of using it.

I also watched the Pluralsight videos by Nick Russo.  Personally, I found those difficult to follow.  Coming in to programming fresh, there was a lot that I felt was skimmed.  This meant I spent a lot of time pausing videos to duplicate scripts.  There’s a bunch of files attached to the courses, but I felt it was important to actually write the code.

In addition to Python, Git, and APIs, you also need to know the different data formats.  The main ones would be YAML, JSON, and XML.  Again, not coming from a programming background this was another stumbling block for me.  The different sources I used all covered this, but it took some work to really understand it.  It came down to just going over the formatting and syntax a few times until it really made sense.

If that wasn’t enough to learn, there’s also the automation frameworks.  Things like NETCONF, RESTCONF, YANG, Ansible, Puppet, Chef, NSO, etc.  More to learn.  More terms.  More syntax.

But wait, there’s more! Docker and VIRL/CML.  Learning about the tools to build environments programmatically, and how to make them work.  Yet more terms and syntax.

The exam also covers the software design methodologies.  Things like Agile, Lean, Waterfall, etc.  The DevOps ideas.  Testing methods.  Luckily, no syntax, but more terms.

The final topics were (for me) the easiest.  Basic network security and network operations.  Things like attack types and remediation mechanisms, subnetting, and other layer 2/3 functionality.  Since this is stuff I’ve spend years working with these topics were a breeze.  However, for someone new to network operations the process of learning the layer 2 and layer 3 configuration can be a bit more complicated.  Luckily, this isn’t the CCNA.  You don’t need to configure STP or OSPF.  You just need to know what the terms mean.  If you can articulate what a switch and router do, what the OSI model is, and you understand how subnets work then you should be OK.

Thoughts on the exam

As I’d mentioned at the beginning, I found this exam to be both fun and challenging.  There were questions where I stared at the screen slack-jawed trying to understand what was being asked.  Often, those questions were ones I was overthinking, and after a brief befuddlement I figured it out.  This isn’t because the questions were poorly worded.  In fact, it was the opposite.  I thought the questions were well written, but since some of the concepts are still new to me it took a moment to really wrap my head around it.
I think the exam was fair, and it asked good questions.  I didn’t feel like there were any trick questions, or things that were intentionally misleading.  There were definitely some challenging questions, but they seemed fair and I felt like I should have known the answers.  Without giving anything away, I’ll just say that since this is a technical exam knowing the terms, acronyms, and syntax for all of the topics is important.

Final notes

I want to reiterate that I thought this was a great exam, with really good content.  Whether we network engineers want it or not, network programmability is going to be a thing.  Think back to the people that wanted to maintain a PBX instead of moving to VoIP, or the adoption of virtualization.  These shifts take time, but they are happening.  As difficult as some of this was for me to learn, I’m glad I did.  Comparing this to many of my other certifications, this one really feels like there’s a ton of value and I gained some useful skills preparing for it.

TOGAF 9.2 Certified

I recently finished the TOGAF 9 Part 2 exam.  Believe it or not, this exam is the follow-up to the TOGAF 9 Part 1 exam.  Having completed the Part 1 exam and certification process already, completing this exam upgrades my certification from TOGAF 9 Foundation to TOGAF 9 Certified.

If you don’t know what TOGAF is, or are unfimilar with the Foundation certification see my post on the Part 1 exam.

About the Exam

There are a couple things to be aware of with Part 2.  First off, it is an upgrade to Part 1.  This means that all the concepts are the same.  The big difference is that Part 1 focuses on knowing the TOGAF Standard, and its components.  Part 2 focuses on how it is used.  It’s also worth noting that the TOGAF 9 Certified certification replaces the TOGAF 9 Foundation certification.

The exam, on paper, looks deceivingly easy.  It is all of eight questions long.  No, these aren’t 8 questions with 14 sub-parts.  Nor are they simulations or other types of questions.  Just eight questions, with four answer choices each.  To pass you need to score at least 60%.  Also, each answer is weighted with the most correct answer being worth 5 points, the second best is 3 points, the next is only 1 point, and the worst answer will get you 0 points.  If you do the math, you can pass by getting the best answer five times, and completely missing the rest.  You could also get the second best answer for all eight questions and still pass.  The test is also open book.

Sounds easy, right?  Well, here’s where that takes a bit of a turn.  The questions are scenario based, which means there’s a lot of reading during the exam.  Also, because the answers are weighted it means it can be difficult to pick which of the four choices really is the best.

How I prepared

I took the Part 2 exam a week after I did the Part 1, so all of that studying was still fresh.

I picked up the Official  TOGAF ® 9 Certified Study Guide

For this exam I decided to try one of the practice tests in the back of the book first, and use that to guide my studies.  I found that with the knowledge I had after my Part 1 training, combined with some critical thinking and I was able to pass the practice test with flying colors.

I then went through the questions a second time and I ranked the answers from what I thought was best to worst.  I had about 85% accuracy with that, so I felt confident enough in my understanding that I went ahead and scheduled the test.

The Exam

As usual, this is a proctored exam from a Pearson VUE test site.  The exam experience was uneventful.  I’ve taken plenty of tests at this site, so getting in and out was a breeze.

The one thing about the exam that I will say is that critical thinking is important.  You need to be able to evaluate four different answers to a scenario, and at times it can be difficult to really decide which one is best.

TOGAF 9.2 Foundation Certification

About the Exam

I recently passed the TOGAF 9.2 Part 1 exam.  This is an Enterprise Architecture exam from The Open Group.  The Open Group is an open group (who would have guessed?) that includes a number of big names.  You can read more about them at their site:

The TOGAF certification actually contains two parts, Foundation and Certified.  You can earn the Foundation certification, and then upgrade to the full Certified status by completing an additional exam.  You can also sit both exams back to back and go directly to the Certified status.  More info on the certification can be found here:

For me, since I’m new to the TOGAF standard, I decided to do the Foundation exam first, and once I’ve finished that then move on to the Certified upgrade.

How I Prepared

For my study materials I bought the TOGAF® 9 Foundation Study Guide – 4th Edition

After reading through the book I think it’s a decent read.  It can be repetitive at times, but since some of the concepts are new to me I actually think it’s helpful.  There are practice tests included in the book, and they are almost identical to the separate practice tests sold by The Open Group.  If you get the book then I wouldn’t bother getting the practice tests.

I also watched Pluralsight video series on TOGAF. The thing I liked about the video series was the use of a fictional enterprise that was going through an Enterprise Architecture process.  In the Study Guide I had some trouble really understanding what some parts would look like in practice, so this material helped fill in some gaps.

There’s also the TOGAF library which contains a lot of useful information about the TOGAF standard.  However, for this exam that material really isn’t needed.

Taking the Exam

The TOGAF exam was similar to most other Pearson VUE exams.  The registration is done through The Open Group’s site, which redirects you to the Pearson VUE site for scheduling.  I was able to take the test at the same site I’ve used for Cisco and VMware exams, so the test environment was quite familiar.

The test itself is pretty straightforward.  It’s 40 questions, all multiple choice.  The passing score is 55% with each question equally weighted.  That means if you get at least 22 correct you’ll pass.  Since it’s not an adaptive test you are able to go back and review questions prior to completing the exam.

I really didn’t find the exam to be too terribly difficult.  There were a few questions that I had to guess on, but I was confident on about 70% of my answers.  Since the passing score is 55% I didn’t worry too much about the ones I was unsure of, and I ended up passing.

What’s next

It can take up to 6 business days for the score report to become official.  I am planning to start studying for the TOGAF Certified exam, and I hope to sit the exam in 2-3 weeks.

Update: I took the exam after, and wrote another post about it.

CISSP Certification

I recently received a provisional passing score on the (ISC)² CISSP exam, and I thought I’d share what I learned.

About the exam

First off, the CISSP is a certification centered around IT security, and in touches on both management and engineering aspects of IT security.  You can read more about what the CISSP entails here:

One of the requirements of the CISSP certification is that you have at least five years experience in at least two of the eight domains.

  • Security and Risk Management
  • Asset Security
  • Security Architecture and Engineering
  • Communication and Network Security
  • Identity and Access Management
  • Security Assessment and Testing
  • Security Operations
  • Software Development Security

You can also get a 1-year waiver if you have a 4-year degree, or an approved certification.

When I decided to go for the CISSP I already had 15 years experience, though most of it was on the network engineering side of things.  Due to the breadth of material covered in the exam I easily spent more time preparing for this test than any other certification test I’ve taken.

How I prepared

As I mentioned, I’ve had 15 years experience, so I’m familiar with most network security concepts from an engineering standpoint.  However, this exam goes into a lot more than just the technical side of cyber security.  A lot of the legal frameworks were new to me, as well as the software development side.

I started off by reading the CISSP Exam Cram (4th Edition).  That book is based on a previous CISSP exam, but the content is still relevant to the 2018 version of the test.  I read this cover-to-cover, making a number of highlights along the way.  I then went back through and went over those highlights again to really solidify what I read.

I also had the Sybex Official Study Guide and Practice Tests.  This book is much bigger, and I thought it went into more detail than the Exam Cram.  I mainly used to book as a reference for areas that I found I was weak in after taking the practice tests or concepts that I wasn’t confident in after finishing the Exam Cram.

To break up the monotony of reading I also watched the CISSP video series through Pluralsight.  I found the videos informative, but after having done so much reading it was a bit difficult to stay focused when reviewing content I was already familiar with.  I actually think the video series provides a great foundational level, and I would have been better off if I’d started with it before I did the reading. 

Lastly, I also read the Eleventh Hour CISSP Study Guide. I got the Kindle version, and I read through it a couple times in the days before the test.  This is a really condensed version of the material, but I thought it was a great refresher. 

Personally, I’m a big fan of practice tests.  I find that they often help highlight where my weaknesses are, so I can focus my studies more in those areas.  For the CISSP exam I must have done over 800 practice questions.  The exam covers a wide range of material, so I wanted to make sure I didn’t have any gaps.

The exam itself

Having taken exams for PearsonVue and Prometric in the past this exam really wasn’t much different.  The testing center did palm scans, and they were a lot more controlled than other exams, but nothing to significant.

Not that this is unusual for certification exams, but the CISSP exam seems to take pleasure in using some tricky questions.  Without getting into NDA space I’ll just use a very loose example-

Q: Which of these BEST describes what is needed for a sandwich

A: Peanut Butter

B: Mayo

C: Bread

D: Meat

Well, a sandwich could made with all of them (at the same time if your brave enough).  The correct answer is C because a sandwich is (at least by definition) made with bread.

In the US the exam is adaptive, meaning there’s no Back button, so when you submit an answer you’d better be happy with what you selected.  Read twice, click once.  It also doesn’t tell you how many questions there are.  It just stops abruptly somewhere between 100 and 150 questions.  The screen doesn’t display a result either.  You don’t find out if you passed or not until you get the score report.  The score report should indicated if you passed or failed, and if you failed it should list the domains you were weak in.  There’s also situations where a score isn’t immediately available.

After the exam

If you passed the exam you should get an email confirmation a couple days later with information on submitting an endorsement application.  The process is pretty straightforward, but it can take upwards of eight weeks for everything to be approved before the certification is official.

 Right now I’m still waiting for the official approval, so any addition details will come along when that’s complete.