VCDX-NV – Defence Scenario

Due to the virus outbreak, my VCDX defence has been postponed until the next window, which is June. The VCDX board decided, understandably, to keep their panellists and applicants as safe as possible. That said, I thought I’d continue the blogging trend and discuss another area of preparation.

Still excited as 3 months will fly by! I’ve discussed the document and design defence. Now let’s look at the defence scenario.

What is the Defence Scenario?

The defence scenario is 1 of 2 defences I will have to complete to successfully become a VCDX. The first task is the design defence, which I’ve spoken about here. The second is the defence scenario. This is a 45-minute window where my 3 panellists will create a scenario, to test my architecture skills.

So how am I preparing?

Know your subject.

I am gunning for the VCDX-NV (Network Virtualization) and my submitted design is using NSX-v. Therefore the defence scenario will be focusing on NSX-v technologies. My design document and my design defence would have covered off a number of NSX-v areas, touching on multiple pillars in the blueprint. So, is it reasonable to assume, the lighter or untouched areas in my design will not be the focal point of the scenario… I think so. Know your subject in its entirety, not just the elements that are covered in your project.

Create a methodology.

There are numerous blogs out there which recommend different ways to tackle the defence scenario. The advice I have been given is; “Do what feels most natural to you”. While I like the advice, I wanted to meet in the middle, I wanted to use a methodology that spoke to me. So I have borrowed Abdullah’s (and Larus’) methodologies. Both are the same conceptually, however, Adbullah’s is written focusing on NV and Larus is focusing on DCV.

Abdullah Abdullah – https://notes.doodzzz.net/2018/06/08/vcdx-nv-design-scenario-youre-the-river-and-youre-the-raft/

Larus Hjartarson – https://vmice.net/2015/10/vcdx-design-scenario/

In short, these methodologies split the board up into 3 sections. 1 for the conceptual design, 1 for the logical design and (usually the centre) the design decisions/diagram(s). When I read both these blogs; it instantly clicked, their brain works like mine, so this is my methodology.

Mock, mock and mock some more.

Nothing beats good old fashion practice. The best shooter on the team is always the one that has the most repetitions. Mock design scenario’s with a number of audiences. I’ve mocked with DCV’s, NV’s and some dual VCDX’s. There have been some nightmare scenarios and some catastrophic showings, but I am improving. At the start, this knocked my confidence and I’ve had to pick myself up or have others pick me up. It’s important to keep working! A variety of audiences has helped, with each of them coming up with different scenarios and different questions. Even having different personalities and a few troublemakers as helped prepare me for “anything”.

My schedule.

I’ve started scenario mocking in mid-January and have done 1 a fortnight until the end of February. As my defence has been postponed, I’ll perform one scenario a fortnight until closer to the June date, where I’ll ramp up. I feel it’s important to keep my foot on the gas and while I won’t be flat out for 3 months, my VCDX preparation won’t stop.

As with the last 2 posts, remember, no VCDX number, so please don’t take this as gospel.

Wish me luck!