CNCFCNPAFree

Cloud Native Platform Engineering Associate Free Practice Questions

This practice bank tests foundational cloud native platform engineering knowledge. Questions cover container images, runtimes, Kubernetes basics (namespaces, Deployments, Services, Pods, scheduling, ConfigMaps, health checks), kubectl usage, immutable infrastructure, sidecar pattern, high availability, and infrastructure as code. Key decisions involve distinguishing container vs VM concepts, understanding declarative vs imperative approaches, and applying orchestration primitives for resilience. The practice questions build fluency in core Kubernetes constructs and platform engineering principles, preparing you for the CNPA certification.

15
practice questions
20
recall cards
15
explanations
0
sign-ups required
Exam-focused analysis

What this CNPA practice set measures

This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.

Core Container and Runtime Fundamentals

This section covers the foundational concepts of containerization. A container image is a lightweight, standalone package containing code and all dependencies. The container runtime manages the lifecycle and isolation of containers. Understanding these basics is critical for platform engineering because they underpin all orchestration and deployment decisions. The practice bank emphasizes the difference between containers and virtual machines and the role of the runtime in process isolation.

  • Container images package code and dependencies into a single executable artifact.
  • Container runtimes handle starting, stopping, and isolating containers.
  • Containers are not virtual machines; they share the host OS kernel.

Kubernetes Resource Organization and Workloads

Namespaces provide scope for resources, helping organize multi-tenant clusters. Deployments manage pod replicas and updates declaratively. The kube-scheduler assigns pods to nodes. Services provide stable endpoints for accessing pods. ConfigMaps inject configuration data. Pods are the smallest deployable units. The practice bank tests the ability to select the right resource for a given purpose and understand how they interact.

  • Namespaces partition cluster objects but don't provide hardware isolation.
  • Deployments ensure desired pod state; they don't manage storage or networking.
  • Services abstract pod IPs via stable DNS and IP endpoints.

Declarative Configuration and Immutable Infrastructure

Declarative configuration lets you define desired state, and the system reconciles to it. Immutable infrastructure replaces instances rather than modifying them in place. Infrastructure as code manages infrastructure via version-controlled config files. The practice bank tests these principles through questions on kubectl apply, ConfigMaps, and the sidecar pattern. These practices enable reproducibility, automation, and resilience in platform engineering.

  • Declarative configuration reduces drift and enables automation.
  • Immutable infrastructure improves reliability by avoiding in-place changes.
  • Infrastructure as code uses version control for reproducibility.

Resilience and Application Health

High availability is achieved by distributing replicas across nodes and zones. Health checks (liveness and readiness probes) determine if containers are operating correctly and ready to serve traffic. The sidecar pattern extends primary container functionality without modifying the application. The practice bank verifies understanding of these resilience patterns, which are essential for building robust cloud native systems.

  • Distribute replicas across failure domains for high availability.
  • Health checks enable automatic restart and traffic routing.
  • Sidecar containers augment the main container (e.g., for logging, monitoring).
Active recall deck

Practice Cloud Native Platform Engineering Associate with real flashcards

Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.

20 free cards

Card 1 of 20

1 reviewed this session

Static practice bank

Start the 15-question diagnostic

The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.

Question 1 of 15

Which of the following best describes a container image?

Show hint

Understand core container concepts and image fundamentals.

1 correct answers

Study workflow

Turn one CNPA attempt into a study plan

  1. 1

    Master Container Basics

    Review the definition of a container image and its distinction from a virtual machine. Understand the role of the container runtime. Practice identifying which component handles process isolation versus networking or storage.

  2. 2

    Learn Kubernetes Resource Hierarchy

    Familiarize yourself with Pod, Service, Deployment, Namespace, ConfigMap, and Secret. Use kubectl explain for each resource. Understand how they relate and when to use each. Focus on the purpose of each resource as per the practice bank.

  3. 3

    Practice Declarative Management

    Write YAML manifests for a typical application: Deployment with replicas and labels, Service with selector, and ConfigMap for environment variables. Apply with kubectl apply and observe desired state reconciliation. Compare with imperative commands to solidify the concept.

  4. 4

    Study Immutable Infrastructure Patterns

    Understand why rebuilding and replacing containers is preferred over patching. Explore the sidecar pattern by deploying a simple application alongside a logging sidecar. Test how to update applications by rolling out new versions via Deployment updates.

  5. 5

    Implement Health Checks and High Availability

    Add liveness and readiness probes to a Deployment manifest. Experiment with multi-node clusters to distribute replicas. Verify that Kubernetes restarts unhealthy pods and routes traffic only to ready pods. Relate these practices to high availability.

FAQ

Questions about this CNPA practice page

Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.

What is the primary difference between a container and a virtual machine?+

Containers share the host OS kernel and are lightweight, starting in seconds. Virtual machines include a full OS and hypervisor, making them heavier but offering stronger isolation. Container runtimes manage process isolation without hardware emulation.

When should I use a ConfigMap versus a Secret in Kubernetes?+

Use ConfigMap for non-sensitive configuration data like environment variables or config files. Use Secret for sensitive data such as passwords or API keys, as Secrets are base64-encoded and can be encrypted at rest. Both inject data into pods.

How does the kube-scheduler decide where to place a pod?+

The kube-scheduler considers resource requirements (CPU, memory), node constraints (taints, tolerations), affinity rules, and data locality. It selects a node that can satisfy the pod's resource needs and policies, then updates the API server with the binding.

What does it mean to practice immutable infrastructure?+

Immutable infrastructure treats servers and containers as disposable. Changes are made by replacing entire instances rather than modifying existing ones. This eliminates configuration drift, simplifies rollbacks, and improves consistency across environments.

Why are health checks important in container orchestration?+

Health checks allow the orchestrator to detect when a container is unresponsive or not ready to serve traffic. Liveness probes restart deadlocked containers; readiness probes control traffic routing. This ensures high availability and self-healing of applications.

Keep studying

Build the next review session

Browse another free bank or use the study strategy guide to turn your misses into spaced review.