Recently (18th of April 2017) I covered Objective 2.7 from the VCAP6-DCV Design (VMware Certified Advanced Professional – Data Center Virtualization) certification blueprint on vBrownbag EMEA.
The objective had the ominous title of “Build Security Requirements into a vSphere 6.X Logical Design“. Among other things it covers the security aspects of a vSphere design and what needs to be kept in mind when addressing topics such as regulation compliance, Role Based Access Control and analyzing security requirements and how they can map to various design characteristics and IT processes.
Here is the slide deck:
I hope this helps someone on their path to achieving the VCAP-DCV Design exam (and than the VCDX of course).
Here is a link to all the other Objectives covered by vBrownbag
Here is the Youtube video as promised!
Recently I had the privilege to be selected as a contributor for the new vSphere Design Pocketbook v3, published by Pernixdata, where IOs are eaten for breakfast.
As the name implies this is the third edition of the book, each one with a different format.
First one had many tweet sized recommendations, the second on included longer posts on design and technical components while this third one is a mix of both.
The social edition, or the online edition only with more fancier name, can be downloaded right here. A physical copy will probably be available at various trade shows where Pernixdata has a presence.
Even as biased as I am I recommend picking up a copy for you and all your closest relatives, cause they will love you forever when you send them a copy. (results may vary).
And as a PernixPrime I also recommend you to check out Pernixdata based on their slogan: “Keep you CPU and memory close, but your IOs even closer”. (this is not their slogan and should be regarded as nonsense).
There isn’t really much I can tell about the defense itself without giving up way to much information so keep in mind this post is intentionally very vague.
As I mentioned in a previous post the defense itself has three distinct sessions.
The defense itself to defend the design and show the panelist you know everything there is to know about your design, including alternatives and expert level understanding of how different technologies/requirements/constraints can impact your design.
The design scenario to show the panelist that you fully understand the VMware design methodology and can use it during customer meetings. Its like a quality assurance test for the VCDX candidate design skill level for VMware.
The troubleshooting scenario is to show the panelist your technical skill level regarding the track you are going for and the method you use. The method is more about speeding the troubleshooting cause you have very limited time. There are very different technology stacks between the four VCDX tracks for the troubleshooting to focus on.
And just remember that the panelist is not there to make you fail, they are there to help you by asking questions that you can answer to increase the score (assumption on my part).
The time will fly away as soon as you start and before you know it the first section is done. Then you get a short break before the second section and before you know it that time has passed as well. Your brain will go into autopilot mode during the sections.
Then you are done. Expect to feel releaved and somewhat mentally tired. Don’t expect to run on full capacity the following days or week. It is quite normal to not remember exactly who was on your panelist.
Now only a “long” wait until the result email arrives.