I’ve been putting off doing VCAP level exams for a long time, probably longer than I should have in hind-sight. But a month ago I took my brave pills and booked what would be my first VCAP level exam: VCIX6-NV ↗. So the date was set and I have been studying in pretty much all the free time I have over the last month - repeating HOLs over and over, standing up, breaking, fixing my home lab’s NSX environment, setting all kinds of stuff with API instead of the UI to try and get a grasp of everything this exam is supposed to encompass.

I’ll start with studying, follow the blueprint - it is absolutely essential and will prepare you for (almost) everything this exam throws at you, follow one of the blueprint guides, I used Martijn Smit’s excellent one ↗ - be aware it was written in 2014 and is not fully up to date with VCIX6-NV, but it very close - I used this guide step by step and went and implemented everything that was described in my lab.

This leads me on to step two - if you don’t have a home lab or a dedicated environment ↗ for testing in, I believe it will be very hard to pass this exam, even rent one from baremetal cloud I linked to before. It also helps to have a use case: mine is the services for my apartment and parent’s home runs inside this lab which gave me the perfect use case for NSX, multi-tenancy and some live workloads to experiment with, a snippet of my DLRs, Edges and Logical Switches can be seen below.

Home lab NSX Edges

It helps that above, each of the ESGs and DLRs has a different config, some run OSPF, some static, some BGP between each other, the Kharms-DLR for example has some bridging interfaces there to transmit client data onto a shared subnet with servers (the kit is actually hosted in that premises).

NSX Logical Switches

If you don’t have use cases, make some up, build a few workload you sort-of care about so you are motivated to fix rather than just blow away and start again, it will also help you experience edge cases (I had a few load-balancer WTF moments the night before the exam!).

I’m assuming you have a VCP6-NV and followed some online courses like Jason Nash ↗’s PluralSight course ↗ for that - but this exam being 100% live lab based, the best experience you can get is to actually use the product.

That nicely leads me on to my third piece of advise for studying, do the HOLs lots.

Ones I’d particularly recommend:

and if they’re still available:

I covered the above labs between 5-10 times each. They are invaluable and are very close to the exam experience of which you can get a look at here ↗.

Moving on to taking the exam itself, if you want more info on the environment, take a look at the blogs by Joshua Andrews ↗ and Dave Davis ↗ - take note in particular the keys that are disabled and that you have no right click so don’t click on a VM console session :)

The exam time is 190 minutes, which sounds like a lot - it’s not. This exam is grim and a god damn time vortex, I got hung up on Q2 after the browser cache didn’t clear and ended up rebooting an NSX manager to try and alleviate the problem - which worked, but it was time wasted. I also encountered a problem where two questions seemed to contradict each other, but it was me being panicked, I didn’t see it - don’t get lost in the beginning, note down questions you aren’t 100% confident with and come back to them.

Set yourself a pace per question, like you would with any exam, 190 minutes and 23 questions = 8.2 minutes per question. I did find myself at the end with 30 minutes left and 8 questions to go, rushing through trying to make up for lost time and didn’t end up answering everything, but that appears to be the grim truth of VCAP level exams - I later found out on the vExpert Slack team this is the rule rather than the exception.

But the stress, leaving out questions at the end because of lack of time and overall dread felt during the exam resulted in this:

However, less than an hour later and a very hasty + angry drive home, I found this in my inbox…

That I did not expect, I almost didn’t want to open the attachment for fear of it driving home the truth that I had failed, however, my pessimism appeared to be redundant and I can now proudly call myself a VCIX ↗! :)

If you want a few more resources on exam experiences, Anthony Spiteri ↗ and Ross Wynne ↗ have both written about the VCIX-NV in a similar manner.

“VCIX NV”

Why not follow @mylesagray on Twitter ↗ for more like this!