Exaforge

Cloud, DevOps, Evangelism

VCP Recertification

VMware announced recently that they would start requiring re-certification of VCPs.  I'm not sure I feel like this is a good call.

Their reasoning is two fold (as far as I can tell):

  1. Ensuring that VCP holder's knowledge is current.  "But staying up to date in the expertise gained and proven by your certification is equally vital. If your skills are not current, your certification loses value."
  2. Most other industry certifications require this as well. "...and is on par with other technical certifications like ones offered by HP, Cisco and CompTia (A+)" -- Christian Mohn

I think both of these arguments are specious.

  1. VCPs are tied to a specific version of vSphere...they aren't 'version agnostic'.  Check out my transcript below:Screen Shot 2014-03-10 at 10.38.33 AMEvery certification I've received is version specific.  Meaning there's nothing to 'keep up to date'.  vSphere 3.5 hasn't changed.  Therefore my VCP3 shouldn't need to be updated.  Clearly, if I don't hold VCP4 or VCP5 (or some other, higher certification), I can't show that I've been keeping up with the technology, and that my knowledge of the current product line is outdated, but that doesn't impact the understanding in my VCP3.  There's no reason to remove my ability to use the VCP3 logo...and perhaps VMware should drop the use of unversioned logos:
    VCP_Logoin favor of versioned logos like this:</p>

    vcp5_image_400X300So that its more clear how current a given person's certification is.</li>

  2. Other vendors do expire certifications, but the majority of vendors also don't specify a version number on the certification itself.  The CCNA, CCIE, from everything I understand are non-version specific, and therefore having to 'recertify' is entirely reasonable, because the technology they refer to has changed.
  3. </ol>

    So there you have it - I think the re-certification requirement is silly.