How to Plan a Certification Path When Everything Keeps Changing
Count what has changed in 2026. Microsoft retired fifteen-plus exams. CompTIA launched SecAI+ and AutoOps+, refreshed Security+ objectives, moved Data+ and Linux+ to new versions. Cisco rewrote CCNP and CCIE blueprints. AWS rebuilt its programme. Fortinet renamed everything. PMI overhauled the PMP. ISACA changes CISM in November.
If you are trying to plan a certification path against that, you are not imagining the difficulty.
The trap this creates
Constant change encourages two bad responses.
Paralysis. Waiting for things to settle before committing. They will not settle. There is no year coming where the catalogue stands still, and a year spent waiting is a year without a credential.
Chasing. Adding every new credential as it launches, on the theory that being current is the point. This produces a CV listing eight certifications and demonstrating no depth in any of them.
What actually protects you
Certify against your job, not against the news. The single best filter is whether the credential appears in listings for the role you want. Vendor announcements are marketing. Job postings are demand.
Prefer credentials with long lineages. Security+, CISSP, CCNA and AZ-104 have all changed versions repeatedly, but the credential itself has been continuously recognised for years. Version changes are survivable. Credential discontinuation is not, and the older names rarely disappear.
Finish things. A passed exam on a slightly dated blueprint beats a half-studied current one every time. Retirement does not revoke what you hold.
Check the code before you buy. The cheapest mistake to avoid in this whole business. Two minutes on the vendor's own exam page.
Where the churn is genuinely signal
Not all of it is noise. When a vendor adds content to an existing exam, that reflects the job changing. SC-500 adding AI workload security to AZ-500 is not marketing, it is an accurate description of what security engineers now have to secure.
The distinction worth holding: changes to existing credentials usually reflect reality. Entirely new credentials usually reflect a market opportunity. Both can be worth pursuing, but only the first is likely to be asked for by name in the next two years.
A workable rule
Hold one foundational credential in your discipline, one that is current for your specific stack, and nothing else unless a role demands it.
For a security person that might be Security+ plus a vendor credential for whatever firewall sits in the rack. For a cloud person, an associate-level provider certification plus depth in the services you actually run. Two well-chosen credentials, kept current, beat six collected and left to lapse.
The industry will keep changing the catalogue. Your job is not to keep up with it. It is to hold the credentials that describe what you can actually do.
Whatever you decide to take, we probably cover it. Browse all 150+ exam question sets, all on current blueprints, with lifetime updates and a refund if you fail.