VCDX – Supporting Documentation

Berikut ini, saya mengutip resource yang sangat baik dari mengenai persiapan untuk mengambil sertifikasi VCDX. Sertifikasi tertinggi dari VMware Inc.

Once you have finished your design documents, you then have to prepare the supporting documentation.  The length of this task is very often underestimated by aspiring candidates, who either rush the job to make the submission and possibly have their application rejected due to incompleteness or miss their submission date.


List of articles in VCDX series:

  1. VCDX – Recipe for Success
  2. VCDX Study Plan – Networking
  3. VCDX Study Plan – Security
  4. VCDX Study Plan – Storage
  5. VCDX Study Plan – BC/DR
  6. VCDX Study Plan – Compute & vSphere
  7. VCDX – The Submission
  8. VCDX – The Presentation
  9. VCDX – D-Day
  10. VCDX – Think like a Panelist
  11. VCDX – I passed, now what?
  12. VCDX – Design Scenario Strategy
  13. VCDX – Troubleshooting Scenario Strategy
  14. VCDX – Mock Design Scenarios
  15. VCDX – Mock Troubleshooting Scenarios
  16. VCDX – Learn to speak “VCDXese”
  17. VCDX – How do I measure if my Customer Requirements are being met?
  18. VCDX – Logical & Physical Design Blueprints
  19. VCDX – Study Group Etiquette
  20. VCDX – Supporting Documentation

The term “Supporting Documentation” refers to the following documents/sections from the VCDX Blueprint:

  • Implementation Plan
  • Configuration Guide
  • Test Plan
  • Standard Operating Procedures

Assuming you have validated that your design meets your Customer’s Requirements, you now have to ensure that your supporting documentation will allow the design to be implemented, configured, tested and operated successfully.  This is where we separate the men from the boys, so much effort has gone into the design process, you then need to marshal your resources and push through the creation of the supporting documentation.

The strategy is very simple, create a linked list that maps from each physical design decision to the Implementation Plan, Configuration Guide, Test Plan and the SOPs.  This is summarised in the diagram below:


It is very important to maintain a unique numbering system throughout all of your documentation; this will allow you to quickly verify that all components and scenarios are covered and then collate them into a matrix to ensure that nothing is missed.  For example: supporting_documentation_template and supporting_documentation_matrix.



Be Sociable, Share Tweet about this on TwitterShare on LinkedInShare on FacebookEmail this to someone

Leave a Reply

Your email address will not be published.

%d bloggers like this: