Post

CNPE: Building the Platform

CNPE: Building the Platform

This is the platform lab on The Road to Golden Kubestronaut. CNPA was the concept exam. CNPE asks you to build the platform.

The Certified Cloud Native Platform Engineer exam is performance-based. It has been required for Golden Kubestronaut since 1 March 2026. For two hours you work in a Linux remote desktop, in the terminal and in web interfaces, on architecture, GitOps, self-service APIs, observability, and policy.

By now this should feel like a review of the road behind you. Treat it that way, and still practice. A review you cannot type is not a pass.

Where this exam sits

CNPE reuses CKA, CGOA, CAPA, CBA, KCA, PCA, and OTCA. The new part is holding them in one system a developer can use. Linux is the last exam after this one. The platform still runs on an operating system, and LFCS is that exam. Finish the platform lab first, while the GitOps and policy work is fresh.

Exam snapshot

Domains match on the CNCF CNPE page and the Linux Foundation CNPE page.

ย ย 
ExamCertified Cloud Native Platform Engineer (CNPE)
FormatOnline, proctored, performance-based
Duration2 hours
Validity2 years
PrerequisiteNone. CNPA is the right preparation. It is not required.
Price$445 for the exam, including one retake
Time to schedule12 months from purchase
IncludedTwo Killer.sh simulator attempts. Each attempt stays open for 36 hours.

Syllabus

GitOps and Continuous Delivery, 25%

Tied for the largest domain.

  • GitOps for applications and for infrastructure.
  • CI/CD that lands on Kubernetes.
  • Progressive delivery. Blue/green and canary. You did the idea in CKAD, ICA, and CAPA. Here you wire it.

Platform APIs and Self-Service, 25%

The other large domain.

  • CRDs that represent a platform service.
  • A workflow a developer can start without filing a ticket.
  • Operators that reconcile those requests.
  • Automation around that self-service path.

Observability and Operations, 20%

  • Monitoring, alerting, logging, and tracing, in one place.
  • Metrics that say whether the platform is getting better.
  • An incident. Find it and fix it. CKA troubleshooting still applies.

Platform Architecture and Infrastructure, 15%

  • Networking, storage, and compute choices that a platform has to make on purpose.
  • Cost, right-sizing, and scaling.
  • Multi-tenancy. One cluster, many teams, and the limits that keep them apart.

Security and Policy Enforcement, 15%

  • Service-to-service communication that is authenticated.
  • RBAC across the platform.
  • Audit trails, SBOMs, and compliance reports.
  • Policy engines and admission controllers. Kyverno belongs here.
  • Scanning in the pipeline, before the deploy.

How to prepare

  1. Read the competencies on the Linux Foundation CNPE page.
  2. Build a small platform path on a cluster. A Git repository, Argo CD syncing it, a Kyverno policy rejecting privileged pods, and one dashboard that shows the app is up.
  3. Add a CRD that means โ€œplease create an environmentโ€ and a controller, even a tiny one, that acts on it.
  4. Use both Killer.sh attempts. The docs allowed during the exam are the Kubernetes docs and blog, plus task-specific links in the exam. The list is on the resources page.

Resources

  1. The official curriculum. CNCF CNPE page and the Linux Foundation CNPE page. The PDF is CNPE_Curriculum.pdf in cncf/curriculum.
  2. The docs for the lab. Kubernetes documentation for the tasks, and the project docs you already used for Argo, Kyverno, and Prometheus.
  3. The simulator. Two Killer.sh attempts, included with registration.

Before you book

One monitor, a private room, a matching photo ID, a clear desk, and a computer that can install the secure browser. Not a virtual machine. Plug the laptop in. You have two hours.

The next post is LFCS, the Linux Foundation Certified System Administrator exam. The operating system under every cluster you have touched on this road.

This post is licensed under CC BY 4.0 by the author.