Shane White and I gave a presentation to the Melbourne VMware User group this past Thursday evening.
For those who are interested, here is a copy of the presentation.
Shane White and I gave a presentation to the Melbourne VMware User group this past Thursday evening.
For those who are interested, here is a copy of the presentation.
I was asked by a person interested in attempting the VCDX if I could share my VCDX application / design, unfortunately as my application was based on an internal IBM project, it is strictly commercial in confidence.
However, I don’t think this is a huge problem as I can share my experience to assist potential candidates with their applications.
In the VCDX Certification Handbook and Application there are several sections, this post focuses on section 4.5 “Design Deliverable Documentation” and specifically the “A. Architectural design”.
Below is a screen shot of this section.
A piece of advise I shared in my post “The VCDX Journey” was that everything in your design is fair game for the VCDX panel to question you about. So for example if your design includes Site Recovery Manager OR vCloud Director , expect to answer questions about how your design caters for these products.
With that in mind, here are my tips.
Tip # 1 – Your design does not have to be perfect!
Don’t make the mistake of thinking you need to submit a design which follows every single “Best practice”, as this is very rare in reality. “Best Practice” is really a concept for VCP’s and to a lesser extent VCAP’s, a VCDX should be at a level of expertise too develop best practices, rather than follow.
Keep in mind, regardless of the architectural decision/s themselves, You need to be able to justify them and align them to your “Requirements” , “Constraints” & “Assumptions” in both your documentation and the VCDX defense panel itself.
So you may have been forced to do something which is not best practice and that you wouldn’t recommend due to a “Constraint”. This is not a problem for the VCDX application, but be sure to fully understand the constraint and document in detail why the decision you made was the best opinion.
My design did not follow all best practices, nor was it the fastest or most highly available solution I could have designed. Ensure your aware of things which you could have done better, or could have changed if you did not have certain constraints, and document the alternatives.
I would suggest a design which complied with all best practices could be harder to defend, than one which had a lot of constraints preventing using best practices. As a candidate attempting to demonstrate your “Expert” level knowledge, working around constraints too meet your customer/s requirements would give you a better ability to show your thinking outside the square, so this goes for your documentation as well as the panel itself.
Tip # 2 – Don’t just fill out the VMware Solution Enablement Toolkit (SETs) template!
If your a VMware Partner, you will likely have access to VMware SETs. These a great resources which make doing designs easier (especially for people new to VMware architecture) however they are templates and anyone can fill out a template. As a VCDX applicant, you should be showing your “Expert” level knowledge / experience and innovation.
I personally have created my own template, which is a collaboration of numerous resources, including the SETs, but also has a lot of work I have created myself.
In my template I have a lot more detail than what can be found in the “SET” templates, and this I felt really assisted me in demonstrating my expert level knowledge.
For example I have a dedicated section for Architectural decisions where I had around 25 ADs for the design I submitted for VCDX, which covered not just specific VMware options, but Storage, Backup , network etc as these are all critical parts of a VMware solution. I could have have documented a lot more, but I ran out of time.
Tip # 3 – Document all your Requirements / Constraints / Assumptions and reference them.
Throughout your design, and especially your Architectural decisions, you should refer back to your Requirements, Constraints and Assumptions.
Doing this properly will assist the VCDX panel members who review your design to understand the solution. If the design document doesn’t give the reader a clear understanding of the solution then I would be surprised if you will be invited to defend.
During the VCDX defense, you should talk to how you designed too meet the Requirements and how the constraints impacted your design. You also should call out any assumptions, and discuss what risks or impacts these assumptions may have, this will be a huge help in your VCDX defense. so ensuring you have documented the ADs well for your application, is a big step towards your application being accepted.
Tip # 4 – Have your design peer reviewed
Where possible I always have my work reviewed by colleagues. Even VCAPs & VCDX’s make mistakes, so ensure you have your work reviewed. This is an excellent way to make sure your design makes sense, and is complete.
I touched on this in Tip # 3, but make sure a person with zero knowledge of the solution, can read your design, and understand the solution. So get a review completed by somebody not involved with the project where possible.
Tip # 5 – Include information about Storage/Networking etc in your design
We all know, no VMware solution is complete without some form of Network & Storage, so ensure that your design has at least some high level details of the network & storage. This should assist you in other sections of your design document explaining your Architectural decisions, and give the reader a clearer picture of the whole environment.
Include diagrams of the end to end solution in an appendix so the reader can refer to them if any clarification is required.
Tip # 6 – Read the VCDX handbook and address each criteria.
As per the requirement document screen shot (above), the handbook actually tells you what VMware are looking for in your Architecture design.
It states “Including but not limited to: logical design, physical design, diagrams, requirements, constraints, assumptions and risks.”
In my design, Originally it didn’t in my opinion strictly meet all of the criteria, so I went back and added details to ensure I exceeded the criteria.
So in choosing what design to use for your application, my recommendation would be too not pick a small/simple design, but choose one which allows you to show your in depth knowledge and some innovation. This will make the application process a little more time consuming from a documentation point of view, but should increase your chance of success at the VCDX defense.
I hope this helps, and best of luck to anyone attempting the VCDX @ VMworld this year!
After deciding mid 2011 to take on the challenge of VCDX4 with a good friend of mine (James Wirth,VCDX#83), I went and sat the VCP5 exam when it was released. I passed VCP5 and assumed that would qualify me for the VCAP4 exams., WRONG! Therefore I had to go back and sit the VCP4 exam which i did two weeks later.
The VCP4 exam was surprising difficult as I had all the latest vSphere 5 configuration maximums and features etc fresh in my mind, so it made answering the “simple” questions much harder than it would have been if I had done VCP4 before doing VCP5.
None the less I passed VCP4 and submitted my authorization for both the VCAP4-DCD and VCAP4-DCA exams in November.
“#83” and I regularly got together to study in our labs as well as reviewing various material in preparation for DCD which we both agreed we should take first.
“#83” sneakily went ahead and booked his DCD without telling me, and I received a call one day from a very happy man advising me he was a VCAP4-DCD.
Not wanting to be left behind I booked my exam for Dec 3rd, and without to much more study, sat and passed the exam with the below score of 403, which I was reasonably happy with. I’m not sure how the grading works, but I felt comfortable during the exam, and was confident pressing “Finish” before the score shows up, so 400+ is pretty good i think.
I found the DCD exam to be by far the best exam I had ever sat, as I feel it actually tests your knowledge and experience as an Architect rather than your ability to remember large amounts of information which in reality everyone just googles. I found the visio style questions to be excellent, although the UI is a little clunky.
I called “#83” and had a similar conversation to when he called me after his result, but as I scored higher than him, I made sure he knew it. lol
#83 and I had a few more study sessions in our labs and I was looking on the Pearson Vue website to schedule my DCA in mid-late January. For some reason I was only authorized to sit the exam until Dec 31st, and there was only one (1) spot available. What the?!?
I therefore booked the exam for Dec 13th (Tuesday) which I was less than impressed about, but hey.
At this point I should point out, #83 and I both agreed the VCAP-DCA was likely the most difficult part of the VCDX process for us, as neither of us have ever been “VMware Administrators”, although we both have years of hands on experience.
I took annual leave for the Friday and Monday before the exam, and went through the DCA blueprint with a fine tooth comb, and did all tasks in my lab several times.
Exam day comes and I left home around 7am (for a 9am exam) and the commute normally takes 45mins, and I planned to review my notes prior to the exam.
However, wonderful Melbourne traffic hits! There was a accident on the main freeway into the city, and it was closed. So I was stuck in a huge traffic jam going off the first off-ramp. Long story short, I arrived at the exam center stressed to the back teeth 5mins after 9. Not happy!
As this was the last spot for the year I couldn’t afford to miss it, but the exam center we’re fine and set me up in the room after taking my ID and a photo etc.
The Exam UI is not bad, but for whatever reason (probably due to me being in Australia and the Lab being in the USA?) there was latency issues at times.
The exam format is a live lab, so
Tip#1 Think before you do something, as you could (and I have heard of people) essentially locking themselves out of a host. If you do this, you will almost certainly fail.
Tip#2 Manage your time effectively, as you don’t have a lot of time.
The tasks your asked to perform range from simple, to more advanced where some design experience will assist greatly.
Tip#3 Be aware not completing some questions prevents you from completing future tasks, so avoid skipping questions unless your totally stuck, in which case, don’t waste time and move on.
Tip#4 Know the DCA Blueprint! The exam isn’t impossible, if you are comfortable with the content of the Blueprint, without following documentation every step of the way, you should be able to pass the exam.
At the end of the exam, I was very nervous as I couldn’t properly concentrate due to the events of the morning commute. But, i felt I had done enough to pass (just!).
I called #83 and let him know I sat the exam, and felt I would only just scrape through, but the next 10 days wait for the exam result was a killer.
I received an exam from firstname.lastname@example.org on the 11th business day (by this time im stressing), and opened the email to find a PDF attachment with my exam score report.
I opened the PDF and it went to full screen (about 150%), and I couldn’t see the score, I had to scroll down to view it. I stopped for a moment, and had serious butterflies in my stomach, I scrolled down and saw the below.
Well, a Pass is a pass right?!?!
I must say, I didn’t really care about the score, I was stoked that I passed after a less than ideal preparation and getting the to exam stressed out.
I called #83 and boasted that I had passed, as he had been giving me a hard time over the pass two weeks while I was waiting for the exam result. He congratulated me, and asked what score I got, and I advised him, as expected, I just scraped through… and after a few seconds I told him I got 308… and we both laughed.
My mid quickly turned to the VCDX application / handbook, and my first tip for VCDX applications is
VCDX TIP # 1 – Ensure you documentation fully meets/exceeds the requirements set out in the handbook
The design I submitted is of a IaaS offering I designed for IBM, and it’s based on vSphere 5, vCloud 1.5 , vC OPS 5.0
The Architecture document I felt was of a high standard, but the supporting documents had not yet been completed for the project, So I had to create these in my own time, to submit the application by the due date. I would say I was 90% happy with my architectural document, but only 50% happy with the other documents.
VCDX TIP #2 – Submit a design for a solution which has been implemented, and all documentation is already completed to reduce the personal time you spend on your application.
I submitted my application (as did #83 & #93) and eagerly awaited a reply from the VCDX team.
I was very pleased to receive the below from Mark Brunstad (@MarkBrunstad on Twitter)
Again I have no idea how the applications are scored, and I was not provided a score, so who knows if my application was just good enough, or passed the bar with flying colors. I guess it doesn’t matter either way as I was accepted.
I got together with #83 (James Wirth) and #93 (Frank Fan) who were both accepted, and organized several mock panels which we did over the next few weeks.
VCDX TIP #3 – Do as many mock panels as possible, with a number of different panelists of different expertise.
The experience of presenting and defending your design is invaluable. The better you know your exam, and the more comfortable you are answering questions relating to your design, the better chance you have of successfully defending.
At this stage I started thinking about travel arrangements, as I am a single dad, I needed to bring my 20 month old daughter with me., I called a good friend of mine and asked if she wanted an all expenses paid trip to Canada to care for my 20 month old daughter while i studied prior to the defense, and during the defense itself. She accepted, and I booked the flights / accommodation etc.
On arrival, I caught up with #83 & #93, and we each did a final presentation to each other. I also did a mock panel (over WebEx and Skype) with #83 and #93 for #88 Ramses (@rsmeyers on Twitter) and he presented well.
#83 did his defense on Wednesday Morning, and #93 was scheduled for Friday afternoon. My defense was Thursday afternoon.
The morning of the defense, I booked a meeting room and did a brief rehearsal (in front of the mirror, lol) and came to the realization that if i didn’t know my design by now, it was too late, so I called it quits and went and spent time with my friend and daughter. (Which i think was a great idea as it took my mind off the defense).
My defense was scheduled for 2PM, so I jumped in the car around 1:30 and drove to VMware’s office which was only a few KM’s away.
I arrived and met up with #89 Eiad (@VirtualizationT on Twitter) & #91 Brian (@bsmith9999 on Twitter) in reception. We had a brief chat and all went for the essential pre defense toilet stop.
After a few mins, Mark Brunstad came and introduced himself, and after checking IDs and taking photos, led me into my defense room.
Mark was my Moderator, Andrew Mitchell (@amitchell01 on Twitter) was my Observer, and my three (3) panelists were Ben Lin (@blin23 on Twitter), Mike Brown (@vMikeBrown on Twitter) & Andrew Hald (@vmxl on Twitter).
I found my Panelists to be very good, they asked clear, concise questions. They are also all very good at not giving anything away during the defense, so dont play poker with these guys. 😉
The first part was the 75min Design Defense. I plugged my USB stick into the laptop provided, and setup my power point presentation. The VCDX documentation advises you create a 15 min presentation, I did this, but also had a lot of support slides, including diagrams and my documented architectural decisions.
VCDX TIP #4 – Have support slide at the end of your 15 min presentation
As I had done numerous presentations of my design both for work, and during my mock panels, I felt that I knew my design pretty much back to front. I was comfortable with all my architectural decisions, and could speak to all of them without referring to the slides.
I was surprised my panel asked very few questions in the first hour, im not sure if this was a good sign or not, but I felt that I had explained my solution fairly well, so I guess I answered some of their questions, hence they didn’t need to ask.
About the 60min mark, I got a few questions from the panel relating to vCloud and vC OPS which are technically not part of the criteria, but as my design needed to support these components, It is expected you can explain how the solution supports those products.
VCDX TIP #5 – Anything in your design is fair game for the panel to ask you about. Know all components of your design.
After answering a few questions (not as many as i expected) , the iPad 75min timer flashed red, “00:00” and time was up.
I was escorted back to reception for a short break, before go back in the room and starting the Design Scenario.
The 30min design scenario starts by the Moderator presenting a PowerPoint, of a fictional scenario.
For me, as I do this on regular basis, I didn’t find it difficult, although, in 30mins, you need to ensure you demonstrate your expert level abilities, so ensuring key aspects of a design are covered, albeit at a high level, isn’t easy.
I used the whiteboard extensively, and talked the panel through my thought process. I believe this is key to the panel being able to assess your abilities.
VCDX TIP #6 Talk the panel through your thought process, and use the whiteboard during the design scenario.
The 30mins went past very quickly for me, and before i knew it, the iPAD timer was blinking red “00:00” again.
We then went into the “Troubleshooting” session which is only 15 mins.
I was given a scenario in a power point presentation, and then the session started.
By now im sure you have read other blogs, where a lot of people who have passed VCDX don’t get to the solution within the 15mins. I would say, the solution is not important, its what you eliminate which is important. The scenario I was given was complex, and have numerous factors not directory VMware related which needed to be addressed.
VCDX TIP # 7 – Whiteboard what you have investigated and eliminated.
Doing this will ensure you don’t repeat yourself and waste the little time you have.
VCDX TIP #8 – Ask questions of the panel (this goes for the Design Scenario too)
The more questions you ask, the more opportunity the panel has to see your expert knowledge.
Right at the end of the 15mins, in the dying seconds, I believe I was at the solution, but more importantly, I had eliminated probably a dozen or more potential issues.
At the end of the Troubleshooting session, Mark (The Moderator) asked if I had anything I wanted to say, which i basically said it was a great experience, pass or fail, and that I believe having to defend in person add a lot of value and credibility to the certification.
Mark escorted me back to reception where I met up with #89 & #91 at reception. We had a good chat about our experience and after 15 mins or so, left the office.
After returning home after the defense, I eagerly awaited the result.
I was woken up Thursday morning around 5am by my phone blinking away, I checked to see if i had a missed call and noticed it was Twitter, since I was now awake, I checked twitter and saw several tweets congratulating the new VCDXs.
I immediately opened my email (on the Phone) and sure enough, there was an email from Mark Brunstad with a subject of “Your VCDX Design Defense Results”.
I opened the email, and saw the PDF attachment, without reading the file name (VCDX4 Congratulations Letter – Josh Odgers.pdf) I opened the attachment and saw the below.
I was over the moon! (and still am).
I am now a VCDX4, and because I sat and passed the VCAP5-DCD BETA, I am also VCDX5!
I found the VCDX experience start to finish to be a fantastic learning experience, and even now, as a VCDX, I still feel there is a hell of a lot of learn. I intend to continue learning from various sources including my VCDX colleagues as well as giving back to the VMware community by blogging, tweeting, and presenting at VMUGs and VMworld (hopefully 2013 as I have missed submissions for 2012).
VCDX # 90 out.