Start with the retirement notice
Broadcom’s VCP-CMA page states that the certification and examination retired on December 15, 2025, with new registrations ending earlier. A 2023 badge ladder should therefore be read as historical context, not a current shopping list. Do not purchase an old examination package simply because its title matches a search result.
Existing achievement and current examination availability answer different questions. Keep the exact credential name and award date on your record, then check your transcript and the applicable issuer policy for its status. Retirement of an exam does not by itself explain every holder’s recognition or renewal position.
Choose a role before choosing a replacement
Cloud management covers visibility, capacity and operational control. Automation covers repeatable provisioning and change workflows. Start by deciding whether your daily responsibility is administering a platform, supporting failures, creating service catalogues or designing the private cloud. That decision is more useful than searching for a badge with similar initials.
Broadcom’s present certification catalogue is the starting point for current VCF routes. Compare the scope and product version in an official blueprint with your environment. Treat any mapping from the old CMA track as a learning recommendation unless the issuer explicitly publishes an equivalency.
Design a provisioning workflow rather than a script collection
A useful personal lab starts with a fictional development-server request. Define the requested image, approved network, resource limits, owner, expiry and required approval. Decide which values a requester can change and which values the platform enforces. This is an exercise in service design as much as command execution.
Create the workflow in small stages: validate inputs, obtain approval, provision resources, attach ownership metadata and report completion. Record which identity performs each action. Keep secrets out of source files, logs and screenshots, and give the automation account only the permissions needed for the exercise.
Make failure and cleanup part of the design
Now deliberately introduce a harmless lab failure, such as an unavailable image or an invalid network choice. Observe whether the workflow leaves partial resources behind. Document what should be retried, what must be rolled back and when a human must investigate. Repeated requests should have a defined outcome rather than creating unexplained duplicates.
Add a retirement path for the development server. Explain how the owner is notified before expiry, how retention requirements are checked and how deletion is recorded. A workflow that provisions successfully but never cleans up teaches only half of the operational problem.
Connect automation with operations
Use the same fictional service to practise monitoring. Choose indicators that answer operational questions: request success rate, provisioning duration, unused capacity and repeated failures. Distinguish an alert requiring action from information that belongs in a dashboard. Define ownership and escalation before adding more notifications.
Write a capacity recommendation with assumptions rather than a definitive prediction from a small dataset. For example, identify whether growth is driven by more requests or by larger allocations. This makes your analysis useful to both the platform team and the people paying for resources.
Turn the work into a study and career plan
Collect a workflow diagram, an access model, a failure log and a service retirement checklist. Map each output to a current exam objective where applicable. Study remaining gaps with official documentation and repeat the exercise without step-by-step notes to test whether the sequence makes sense.
An administrator moving toward automation should be able to explain the operational risk the workflow reduces, not just the tool used. Before enrolling, verify the credential’s live registration status and prerequisites. Keep your portfolio examples fictional or sanitised, and describe them honestly as lab work rather than a production deployment.
Official references
Certification requirements and programme terms can change. Use the issuer’s current page and your account to confirm details before applying or paying.