Below are the notes I have taken during the NJ/NY VCDX workshop at @iamAntonZ ‘s place. We had a great opportunity to have 2 VCDX panelists giving the VCDX workshop, Niran Even-Chen ( @) and Agustin Malanco (@). You could find more info on this at http://nycvmug.blogspot.com/2016/06/re-cap-of-njnyv-vcdx-workshop.html
These notes are by no means to be used or relied on as primary source for your VCDX preparation.
Your design must include all the VCDX blueprint points.
Don’t use any kind of blogs as an official source for your references . Official VMWARE docs are the only sources that you can quote or reference to in your VCDX design.
One of the main changes to VCDX is removal of the “Troubleshooting” scenarios from the defense.
One design can be submitted 2 more times, if it did not get accepted the 1st time around. This means that you will need to make some modifications to your design, before resubmitting it again. You won’t get any detailed information on why it failed the submission, but you might get a generic response such as ” Storage or Networking needs more info”.
Same design could potentially be submitted by 3 different people, and they must submit it at the same time for the same VCDX track. Also, each and every applicant must know the design inside out, not just the portion he or she design.
It takes an average of 4-7 month to prepare the design and validate it. Once you got accepted for defense, get yourself an official VCDX mentor. The mentor will not be fixing your design for you, but rather guide you and advise you on proper documentation. Lookup the directory, and work with him to help you out on this. Just keep in mind that they are ( VCDX mentors) are not being paid for it and do it rather on their own time.