KCNA vs Terraform Associate: which portable certification?

These are the two certifications here that are not tied to a single cloud, which makes them unusually durable: both keep their value if you change platform or employer. They cover different halves of modern infrastructure work, though. KCNA is about running things — containers, orchestration, and the cloud-native ecosystem around Kubernetes. Terraform Associate is about provisioning things — describing infrastructure as code and changing it safely. Pick by which half your job actually involves; if it involves both, KCNA is the gentler starting point.

The two exams at a glance

KCNA is multiple choice, and that matters

The Kubernetes certifications people usually hear about — the administrator and developer ones — are hands-on lab exams where you solve problems in a live cluster under time pressure. KCNA is not one of those. It is a multiple-choice exam covering concepts, architecture and the ecosystem, which makes it a far gentler first step into Kubernetes.

That is its purpose rather than a shortcoming: it exists to give people a credible entry point before they commit to the lab exams. If you want proof you can operate a cluster under pressure, KCNA is not that proof, and the hands-on exams are what you are looking for.

Provisioning versus operating

Terraform answers "how does this infrastructure come to exist, and how do I change it without breaking things". Kubernetes answers "how do the workloads on that infrastructure get scheduled, scaled, connected and observed". In most organisations both questions are live, often for the same person.

In practice, teams frequently use Terraform to provision the cluster and Kubernetes tooling to run what is inside it. That is why holding both is a coherent combination rather than a redundant one — they meet at the boundary rather than overlapping.

How much hands-on each assumes

Terraform Associate assumes you have used the tool: managed state, written modules, read a plan carefully before applying it. The questions reward that experience and expose its absence quickly.

KCNA assumes considerably less, which is the point of a foundational exam. You should understand what a pod, a deployment and a service are and how they relate, but you are not asked to configure a cluster from a prompt. It is approachable for someone whose Kubernetes exposure so far is mostly reading about it — though a few afternoons with a local cluster still make it much easier.

Both renew on a shorter cycle than cloud certifications

These two have shorter validity periods than the major cloud certifications, and both are renewed by retaking the current exam rather than through a free assessment. Worth factoring in if you are planning several credentials.

One practical difference: CNCF exam fees typically include a free retake if you do not pass first time, which meaningfully lowers the risk of booking before you feel completely ready. Check the current terms on the vendor’s page — the facts table above shows each certification’s published validity.

Questions, answered