«

»

Feb 24

VCDX CXXVIII (#128)

On Monday, February 10, 2014 at 2:00 PM I defended the design I submitted before a panel of VCDXs. Just a few short (short in days, but the wait was in no way short) days later on Thursday, February 13, 2014 I received the results of my defense:

vcdx-128

I made it! My VCDX number is 128!

The preparation and the defense process were time consuming, very stressful, extremely educational, and ultimately enjoyable experiences. I learned a tremendous amount about my abilities as an Architect/Engineer and about the VMware design process.

When I was managing an IT department I had a mentor who would often say “there is value in the process.” I feel this is definitely true of the VCDX certification process. The process of documenting, submitting, and defending the design was an extremely valuable learning experience.

My Journey
Up until the VCDX defense the VCAP-DCA is one of the best certification exams I have ever taken. I took the DCA on both vSphere 4 and vSphere 5 when I was working for a VMware customer. In late 2012 I joined a VMware Partner, ABS Technology Architects, and the completion of the VCAP-DCD was on my professional development road map. A short time after joining ABS I sat and passed the VCAP5-DCD. I thought that was as far as I wanted to take it.

Not sure why I decided that I wanted to pursue the VCDX. I was just thinking I had already invested a huge amount in learning the different VMware Technologies. I guess I just wanted to get some validation of the path I had chosen. I attended the VCDX Boot Camp at PEX in 2013 and thought “yeah I can do this.” Beyond that I also recognized how working through the VCDX certification process would ultimately make me a better Architect. I set a goal for myself to attempt the VCDX defense at PEX 2014.

So I started looking for a design. This was probably the hardest part. I wanted the design to be real and I wanted it to be interesting.

I had only been with ABS a few months and had only done a handful of small implementations. Mostly 3-4 hosts clusters for small customers. These were all fairly simple and pretty straight forward. Good stuff but nothing to really get excited about.

In October of 2013 I had the chance to create a design for an Emergency (911) Call Center located in Harrisonburg, VA. This was a small design (5 hosts, about 50 VMs) but as I worked on designing the solution I thought this was very interesting, especially the availability and manageability requirements. I really enjoyed working with the customer, learning about their processes, developing the design, and implementing the solution. The implementation would be finished before the end of the year. Not only was I the Lead Architect for the design but I would also be the Implementation Engineer.

Even though the timing was tight to get the design submitted for a potential PEX 2014 defense I decided to use this solution for my submission. The solution was not an overly complex solution nor was it a very large solution. The reason I chose it was that it seemed to hit all the requirements of the VCDX Blue Print. The primary requirements of the design were focused on availability, manageability, and security.

Submitting the Design
So far the most common question I have had since successfully defending has been “How long did it take you to prepare?”

I have tried to break it down and best I can figure is between 120 to 180 or so hours total. This includes preparing the design documentation, completing the VCDX application, and preparing for the defense. I had approximately 60 hours that I devoted to preparing the design documentation for submission. These hours are pretty well documented since ABS gave me this time to prepare and I accounted for it. There was probably an additional 10 or so hours in proofing and finalizing the design documentation.

I submitted my design documentation and application on December 19, 2013. I found out on January 10, 2014 that my design had been accepted for defense.

Defense Preparation
The rest of the time was spent preparing for the defense, studying my design, questioning my decisions, and participating in mocks. This time is more of a guess as I did not document the amount of time I spent here.

I did Mock Defenses every Friday from the time I submitted up until I left for my defense. The Mocks were with ABS management and other ABS engineers. These mocks were “friendly” mocks, I knew and regularly worked with the folks that participated. Network engineers, storage engineers, BC/DR engineers, and data center engineers all participated in these mocks. Even though these mocks were “friendly” they were still a huge benefit. They helped me build confidence in my presentation and my design. These mocks also focused on the design at a high level which helped me validate the design factors.

The only “unfriendly” mock I did was the day before my defense. “Unfriendly” should not be taken negatively here, I wish I had participated in more of these earlier in the preparation process. This single mock was extremely valuable. I ended up doing some last minute tweaks to my presentation based on things that were brought up in this mock. It was only an hour, but I am not sure I would have been successful with out having gone through this.

VCDX Prep and Defense Tips
Here are a few of my tips for preparing for the VCDX defense:

  • Know your design! I mean it, really know your design. The important thing is to understand every decision you made and why you made it. Ask yourself the following questions about EVERYTHING in your design. Why did you I do that? Could I have done it another way? Why did I do it the way I did it and not some other way? How does what I did map back to the requirements?
  • Participate in Mock Defenses <- THIS!!! I should have done more of these, especially “unfriendly” ones. In mocks make sure that you also do mock design and troubleshooting scenarios.
  • Attend a VCDX Boot Camp. If you are preparing for the VCDX and able to attend one of these live then DO IT! If you are not able to attend one of the VCDX Boot Camp sessions check out the ProfessionalVMware.com VCDX Boot Camp podcast recordings at http://feeds.feedburner.com/Professionalvmware-Brownbags (just search the page for VCDX Bootcamp).
  • Get the book VCDX Boot Camp: Preparing for the VCDX Panel Defense (VMware Press Technology) Great information on preparing for the defense, including sample design and troubleshooting scenarios. Also some great information on how to set up Mock Defenses.
  • Watch the VCDX Prep Videos. They provide a lot of insight into what happens during the defense.
  • If you are not comfortable speaking in front of folks check out Toastmaster. Definitely helped me a lot. They have this exercise called Table Topics that helps you practice thinking on your feet.
  • Prepare your family. Pursuing the VCDX will take up a lot of your time.

If you are interested in pursuing the VCDX Certification more information on the VCDX program, including the VCDX Certification Blueprint and the VCDX Defense Schedule, can be found here http://www.vmware.com/go/vcdx.

Thanks
A lot of time was put into preparing and ultimately achieving the VCDX certifications and I could not have done it alone. I think it is important to recognize the people that helped me through the process.

Thanks to Brad Christian for setting up the mock defenses and allowing me to participate. Also a big thanks to the other VCDX candidates that participated and ripped my design to shreds the day before my defense. Knocked me down a level, for sure, but this did better prepare me for my defense. I really think this final mock is what helped me the most.

A huge thanks to Mark Gabryjelski and Tim Antonowicz for their support, encouragement, and guidance.

Thanks to my company, ABS Technology Architects, for giving me time to pursue this. Thanks to my supervisor, Rob, for putting together and participating in the mock defenses to help me prepare. Thanks to Javier, Rick, and Andrew for participating in the mock defenses and asking great questions about the design to help me through the process.

Finally, a special thanks to my family (especially my wife Sandy and my kids Mary Shannon and Johnathan) for putting up with the time and expense it took. A lot of early weekend mornings were spent working on the design and preparing for the defense, a lot of things were missed or put off because of this. You guys are (and always have been) my everything. Thank you so much for everything you do and put up with. I love you guys.

#128
The weekend after I returned from SFO I was not sure what to do with myself. For the past 3 months or so I had spent most of my Saturday and Sunday mornings studying my design and preparing for my defense. I suddenly had a lot of available free time. A tweet from @millardjk had me doing some research (and doodling) on the #128.

Now to figure out what’s next…..

About the author

vHersey

Hersey Cartwright is an IT professional with extensive experience designing, implementing, managing, and supporting technologies that improve business processes. Hersey is Solutions Architect for SimpliVity covering Virginia, Washington DC, and Maryland. He holds the VMware Certified Design Expert (VCDX-DV #128) certification. Hersey actively participates in the VMware community and was awarded the VMware vExpert title in 2016, 2015, 2014, 2013, and 2012. He enjoys working with, teaching, and writing about virtualization and other data center technologies. Follow Hersey on Twitter @herseyc

3 comments

  1. @virtualsnook

    Congratulations again Hersey and great write up!

  2. Nick

    Congrats again Hersey. Great post and very helpful for others who are interested in pursuing VCDX. Also very interesting to see that a design does not have to be of huge-scale to be considered. It’s all about the design and business requirements. Again, good stuff and thanks for sharing.

    1. vHersey

      Thanks Nick. Sorry I missed you at PEX (guessing you were there). Hope to make VMWorld but we will see.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>