Archive

Posts Tagged ‘VCAP’

VCDX Journey

August 31st, 2010

 

Some of you may be aware that I have been working hard through the VCDX journey over the past year / 18 months. I’m not usually a VMware blogger as I think that space is more than filled, so I usually concentrate on the storage side. However the VCDX is still fairly exclusive, so I wanted to share this journey with everyone. It’s been a really good time, and I have learnt a hell of a lot! It’s helped me better understand the solutions and help my company as a whole put together better VMware solutions, so it’s been hugely beneficial. I’d recommend anyone that is focused on VMware for their company to go down the VCDX route. Even if you don’t get onto the final Defense, it’s a fantastic journey and you will learn a lot.

I won’t go into too much detail about my experience of the Enterprise Admin or Design exams as these have been replaced by the VCAP ones. They are obviously pre-req’s anyway, but I’d say after going through the rest of the journey that they are essential training to get you ready anyway. I’ll probably be sitting both the VCAP exams in the next few months just to make sure my skills are kept up to date.

The Defense Application

Make sure you free your diary for at least a week of solid work. People have said be prepared to do 30-40 hours of work on this, but I think I spent closer to 70 or 80! I had a full week off work, and used both weekends too. I had a lot of work to do as I haven’t really done many fully structured deployments as expected in the Defense application before, so I had to make one up. This is definitely a lot harder as you have to visual everything, including limitations and obstacles. If you make something up, you don’t usually make up challenges for yourself. To compensate, I think I ended up making my scenario a little more complex and I had to do a lot of checking through support docs which added to my work load.

General , , ,



This site is not affiliated or sponsored in anyway by NetApp or any other company mentioned within.