VCDX Presentation

The journey to VCDX presentation is definitely a long and arduous one, I went through the experience once and did not pass my first attempt at VCDX. It was one of those moments where you look back on what you could have done better.

For me I knew my design was not at the level I hoped it would be and not only my VCDX presentation but the way I presented was not helping me.

Getting to the presentation

I worked with my VCDX mentor (Josh Odgers VCDX #90), if you know Josh he is a straight shooter, and an excellent coach and assisted me in going through my feedback from my first attempt. I definitely would not have achieved my successful attempt without his assistance. He also spends a vast amount of his own time helping out other hopeful VCDX’s, taking part in mock panels and providing constructive feedback.

For the second attempt, I made substantial changes to my design document, particularly in the storage area. I also made sure that there was clear linkage between my requirements and my design decisions, this is particularly important to provide the reviewer with an easy way of understanding why certain decisions were made.

I submitted my design and was received my acceptance to defend in Singapore on July 9th 2014. This time I knew what to expect and I knuckled down reviewed my design and how to present it.

Preparing the Presentation Itself

So your tired you have entered your design, and all you want to do is take a break, that is probably a good idea, but I recommend not making it more than a day or two. If you are like me your brain will go “I have four weeks and I can’t stop thinking about this anyway!” Its time to dive into writing that presentation, assume that you are going to be accepted and use the time wisely, even if you are not, you have not wasted your time, all thinking towards the defence is useful thinking.

Make sure that you get your design reviewed thoroughly with feedback, but multiple people if possible. Ideally that person should review it against the VMware VCDX blueprint rubric, encompassing AMPRS (remember I am not a panelist and I do not have any insight into how the defence is scored).

Also review your design again also against the rubric. I created a spreadsheet which had a column split across AMPRS and the top row across each vSphere (all outlined in the blueprint PDF). In this spreadsheet I plotted my design against the break down of each area, this gave me 127 different items that I knew I needed to touch to have a chance of being successful.

This spreadsheet then guided my build out of the presentation. In PowerPoint I made a point of choosing a clean template to use, with consistent formatting (this is important) and created my 12 slide presentation. This has been documented before, but this is when you need to find a system that works for you in your presentations, one piece of advice given to me is that you should be able to give your presentation without your deck, calmly and comfortably, all diagrams should be able to be produced on the whiteboard. Remember, you must know all aspects of the design, including Network & Storage!

I also took part in a couple of mock defence panels, the feedback for me was around my confidence, I was not confident in what I was saying even though I knew it inside and out. That was a tricky one to solve, but it is all about mental attitude.

The Actual Defence

I have blogged about my experience, and the main thing for me was overcoming my lack of confidence, I just remember sitting outside the room waiting to go in and repeating in my head, be calm and confident and just relax and enjoy. Its funny because that worked for me. I will not go into the details of what happened in the room, other than to say the whole thing felt really good, I felt prepared and confident.

After the VCDX

I had a holiday with my family, we took a trip up to Northern Queensland, to get away from the Melbourne winter and relax. Its now nearly 6 weeks later and I am thinking that I am really interested in the VCDX-NV (I work for a Telco and networking is massively important piece of what we do). Next year I have signed up to start my Masters, so studying seems to be in my blood. When you think about it in IT, it is always about continuous improvement. Gaining the VCDX has been part of that journey for knowledge.

I really want to help anyone else who is thinking of going through this journey, please contact me at twitter if you would like any assistance at @sidbrydon.

Thanks and good luck!




Progress through IT exams and certifications can sometimes be a challenging time. I feel a lot of the time they do not reflect the real world skills required to actually work in that area. For example a multiple choice question exam does not always suit everyone and can at times be a difficult thing to study for, what you really need is something that test day to day skills.

The VMware VCAP exams definitely do that. The DCA exam was like nothing I had ever experienced before. I remember looking through the blue print online and thinking it will be incredibly challenging. So that is where you should start here:

To prepare for the exam I did the following:

1) Attended the Optimize & Scale course. This was a really detailed course and challenged my knowledge in vSphere 5 (at this point I was still predominantly working with vSphere 4.1).

2) I had access to a high end lab environment and I also built out a smaller scale environment at home, so I could test settings, break things and see the repercussions, and most importantly remind myself of all the command line activities.

3) I reviewed the vBrownbag podcasts, these are an excellent source of information. Access here:

4) I started working with vSphere 5 more and more in my day to day role (we were implementing an enterprise scale VDI platform on vSphere 5 at the time).

5) I read as many PDF’s and kb articles I could find time to read.

6) I read as many blogs as I could around the exam itself, specifically:

(Just to name 3, there is a lot of material out there)

For those of you who have completed the DCA4 exam, there is of course one fundamental difference, no ESX classic.

The NDA around the exam prevents me from being specific about the content. But I wanted to reiterate what I have read and experienced. Read the blue print, understand everything, not everything will be tested though.

Book the exam if you have plenty of hands on experience with vSphere 5 and are comfortable with the command line, both shell and ideally powercli.

The exam itself is a bit of a monster, at 4 hours long. Depending on where you take it will depend on what you can take into the exam. With the DCA exam it is important to work through everything in order as it builds on work previously done and trying to go back in the exam later can be painful, due to the equipment lag.

The most important things are:

  1. When booking work out the best time of day for you to sit a 4 hour long exam, I tend to do better in the morning so I went with 9am.
  2. Get a good nights sleep before the exam.
  3. Eat something before you go in and take a snack and water in with you if you can. Because if you are like me if you need to eat something you lose focus.
  4. Stay calm and work through the problems, remembering that there is not specifically one way of doing things, you use your own preferred method.

I will leave you with one last thing. If the exam lab does not look right (ie you have a host not responding for example, this probably is not part of the exam and you have a problem). One of my friends sat the DCA4 and had a host in a not responding state, he spent 45 minutes trying to troubleshoot it, before doing a host reboot (something you are told not to do), he passed but could have done without the stress!

Have fun and good luck.