1: description

The VCAP exams, and the VCAP Deploy exam in particular, are totally different from VCPs (which you also need to pass in the same track to obtain the certification). While VCPs focus on facts and technical knowledge about products - or, in other words, what an administrator should know - VCAPs focus on two more advanced areas of expertise: the design of a solution and its deployment.

In the case of a VCAP Deploy exam, there is one more, far more impactful difference, the exam is a closed book, practical test. What that means is that instead of a quiz system, you are given access to a lab environment where you are asked to perform a set of tasks ranging from day 2 configuration/operations, troubleshooting/debugging to initial product deployment. The environment itself is very similar to what you would expect in HoL (hands on labs): you get a Windows Server jumpbox with a preconfigured set of applications and browser bookmarks and a side panel listing all the different exam objectives.

Despite what I initially understood from the blueprint, this exam doesn’t give you access to documentation. This is one big grudge I have against it since similar exams in the industry allow you to access their documentation (Red Hat, Kubernetes). On the plus side, the exam is very straightforward for anyone with hands-on experience with the product. With minimal preparation, I’d be willing to bet that anyone with 6+ months of experience can pass first time as long as they keep their head cool and think quickly on their feet.

2: review

The exam is admittedly very enjoyable if you know what you’re doing. The set objectives are not super difficult. You don’t have to be an ex-GSS member to know how to do the majority of the stuff needed to pass. As long as you pay attention to subtle details given in the questions or input data and make the most of the product GUI (embedded manuals, tip prompts etc), you can successfully complete given tasks without ever doing them before at work or in a lab. For example, I never touched SaltStack before attempting the exam and I figured what I need to do on the spot.

Two important things to keep in mind are the time limit and the lack of documentation:

  1. Time - despite the exam being quite low on question number (12), the allocated time is not super comfortable. You can easily assume that you will need 10-15min at least per question which leaves little time to review etc. My advice here is to skip questions you’re not 100% on as quickly as possible and move on to the next one. Once you go through all 12 you can then estimate how much time you’re left with and how much you can “spare” to re-attempt the skipped tasks.
  2. Documentation - as I said before, this is a closed book exam. You cannot access any whitepapers, websites or read offline PDFs. What you do have however is all the embedded help sections within the product(s). I would suggest to review what sort of info will be available on the spot and focus on everything else in your prep time. A good example of this would be code samples: quite common in vRA documentation but rare/non-existent in help prompts.

3: experience

I think it took me about a week to prepare for this exam (3V0-31.22). During this time, I was mostly playing around in the ICM lab trying to familiarize myself with as many product features as possible. I ended up scoring 420/500 (300 to pass) on my first attempt. One annoying thing was that I had to wait for these results nearly two weeks. Unfortunately, it seems that VCAP Deploy exams are still manually verified or the automation behind it is quite lacking.

In terms of time, I was quite fast with knocking out 8 out of the 12 questions/objectives. I ended up having a bit over an hour left to tackle the 4 remaining. I ended up completing all objectives in time however I’m pretty sure I blew at least one of them completely (vRO…).

4: tips

  1. While the exam blueprint makes it look like the only product you need to know/focus on is vRealize Automation, I highly suggest you study Orchestrator and SaltStack as well.
  2. As I mentioned above, when studying for this exam, pay close attention to the code samples in the official documentation. Some of it will definitely come handy during the exam however you need to remember it by heart as there will be no way to look it up in the exam center. This is especially true for anything related to SaltStack.
  3. Troubleshooting is very important. For one thing, you might need to fix some stuff in the lab to complete the objective. Additionally, since the lab has no “oh shit I f*cked up” button, knowing how to troubleshoot and fix issues with the product might prove to be essential when you accidentally break part of the exam environment, This is 100% possible and 100% will happen in the worst possible time