I think the OP is over complicating things. The VCP exams are pretty much a cakewalk if you have 3-4 years experience in vmware (and it's ancillary products). You don't need to memorize every gui option. The test is multiple choice and if you are familiar with the product you will narrow down the choice down to two in a instant.
I have over 25 IT certifications. Multiple cisco, vmware, All the AWS certs, multiple Microsoft, Linux, multiple hardware vendors, etc. My advice is always the same.
- Learn the foundations
- You are not going to get a CCNA if you can't do basic binary math
- You are not going to have a shot at modern MCSA exams without understanding powershell, etc.
- Learn how to use the product for real
- This means you to need to lab it up.
- Books are guides but they are not teachers - Come up with your own scenarios and test them.
- Seek a mentor - You will have questions, they will have answers. This is especially important for policy based exams (security).
- Know how to do it both in the GUI and the terminal. I failed my CCNA:Security the first time out because I knew how to configure ASA's on the terminal, but not with ASDM (The gui).
- Learn the terminology
- Every technology has special terms. You can be a amazon network engineer, but if you can't recite the OSI model (even if you understand it) you are lost.
- Flashcards!
- Learn the administrative information
- This is big on Microsoft and vmware, you are going to be asked licensing, upgrade paths, etc.
- Learn the material/company way.
- There might be five ways to do something that are all correct, but there is only one "right" way.
- This is where you need a study guide for the test.
- Note that in some cases you might need to know multiple "right ways".
- Read the white papers - This is huge for AWS you can get 60% of the answers right from white papers.
Once you have that, it's time to test prep/test
- Pre-Test
- Never ever braindump a test. This is cheating and you are only hurting yourself.
- Find example questions - All test makers have sample questions that will help you understand the format and the style of the questions.
- Read the exam guide - All test makers post a document letting you know what areas the test will cover and points associated with each section.
- Are there labs? If there are labs, see if you can track down some sample labs or build your own labs.
- Take a approved practice quiz - Note that sometimes these are harder than the real quiz.
- Make flashcards, drill them.
- Join a group of like minded individuals, talk shop.
- It's easier than you think - Most of these tests are way easier and you are just working yourself up. They sound hard on paper, but 90% of them are cakewalks if you prepared at all.
- Testing tips
- Read the last line of a question - Most of the time this is the question.
- The the answers next, try to exclude obvious bad answers.
- If you are still in doubt, read the question.
- If the quiz allows you to go back to previous questions, write down or flag questions you are unsure on. Future questions may provide the answer.
- If paper is provided, don't be afraid to 'dump' to the paper before starting the exam. Unless the rules prohibit it, many timers do not start until you accept the EULA. This is a great time to jot down those last minute things you memorized or to write down a grid or anything else that might be useful to you.
- Do not second guess yourself. When you reach the end of the test only review questions you did not answer. If you answered and even thought you had a clue go with that. Your first choice is more often than not the right choice.
- After the test
- Pass or fail, if the test results tell you the areas you are weak on, go study again. Use this as a chance to learn and grow.
- Try not to renew certifications, but to grow beyond them. If you have a a+, don't take it again, take a net+ or security+. It renews the previous certification and forces you to grow.
A lot of people discourage certifications. They will point to that paper tiger they met or how they are unrealistic etc. Ignore them. You never hear anyone complain about the uncertified guy who can't do anything simply because that guy was unlikely to get the job at all! Certifications don't make masters, they make baselines. At a minimum it means you understand the terminology and have exposure to the material. It can also breed confidence. Many certifications will expose you to material, patterns, or concepts that your job may not. I worked with VMware for a decade and I never used their replication or backup products. I had to learn them for my VCP. When I took my Office 365 MCSA exam I also had to learn to use sharepoint, a product I don't think should even exist, but I got more exposure to it and learned something I never would otherwise. And yes, many of the tests will require you to learn something that is "not real world", but you would be suprised how often I find things in the real world that are not "real world". For example I had to learn to use elastic beanstalk for my AWS devops pro exam. Nobody would recommend using that in the real world, but I've ran into it more times than I can count now and knowing it has allowed me to help people get off of it.
I'm obviously not an expert in everything I have a certification in. I can however claim to be much more well rounded and speak to exactly why I got each one. I use certifications as a target for continuing my education. Like a boss fight in a video game. If I don't have a end game I can't bring myself to study. I'd like to encourage everyone to go take a exam. It's good for you and you just might learn something.