Certified Cloud Native Platform Engineer (CNPE)

Platform engineering spent five years as a job title with no exam behind it. The CNPE is the first hands-on attempt to fix that, and the blueprint is unusually honest about what it thinks the job is.

Where the marks actually are

Half the exam — 50% — is two domains: GitOps and Continuous Delivery at 25%, and Platform APIs and Self-Service Capabilities at 25%. Everything else splits the remainder: observability and operations at 20%, architecture and infrastructure at 15%, security and policy at 15%.

That weighting is an argument. It says a platform is a set of APIs other engineers consume without asking you, delivered by a pipeline that reconciles itself. The domain that would have dominated a DevOps exam — build the infrastructure — is the smallest one here at 15%, and it is mostly about cost and multi-tenancy rather than provisioning.

The practical consequence: if your platform work has been Terraform modules and Helm charts, you have prepared for the smallest domain. Writing a CustomResourceDefinition that models a service, and putting an operator behind it, is where a quarter of the marks live and where most candidates have the least practice.

The unfamiliar-tool clause

The curriculum lists fifteen tools it may draw on, then adds something no other CNCF exam says so plainly: candidates are expected to complete tasks using unfamiliar tools by relying on the help and documentation available in the exam, and will not be tested on deep tool-specific knowledge unless a competency names it.

Read that as an instruction rather than a reassurance. It means memorising Argo CD's flags is the wrong preparation, and knowing what a GitOps reconciler must do — so you can find it in any tool's docs within a two-hour clock — is the right one. It also means the exam is partly testing whether you read documentation quickly under pressure, which is a fair description of the job.

Against the CNPA

These are not two difficulties of one exam, they are two different claims. The CNPA is multiple-choice, $250, and spends 36% of its marks on core fundamentals — it establishes that you know what an internal developer platform is. The CNPE has no fundamentals domain, costs $445, and puts you in a terminal.

The blueprints barely overlap. Someone who passed the CNPA has not half-prepared for the CNPE; they have learned the vocabulary the CNPE assumes you already had.

Before you book

Build one self-service path end to end. A CRD, an operator or Crossplane composition behind it, a GitOps reconciler deploying it, a policy engine admitting it and a dashboard showing it. That single exercise touches four of the five domains, and it is closer to the exam than any course.

Use both simulator attempts. They are included in the price and are traditionally harder than the exam. Sitting the first one early — before you feel ready — is what turns them into a study plan rather than a verdict.

The cut score is not published. The Linux Foundation discloses 75% for its multiple-choice exams and 67% for the LFCS, and says nothing about this one. Specific numbers in study guides are inferred from score reports, not stated by the vendor.