> ## Documentation Index > Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt > Use this file to discover all available pages before exploring further. # CNPA Exam Blueprint > Summary of the CNPA exam blueprint covering domains, question distribution, formats, timing, scoring, study priorities and strategies for platform engineering certification preparation. Welcome back, CNPA students. This guide summarizes the CNPA exam blueprint: domains tested, question distribution, question types, timing strategies, and how to prioritize study time based on domain weight. Exam overview | Item | Details | | - | - | | Format | Proctored (in-person or online) | | Question type | Multiple choice (4–5 options) | | Total questions | 60 | | Time | 120 minutes (2 hours) | | Passing score | 75% (45 correct answers required) | Plan for roughly 2 minutes per question on average. Allocate extra time to higher-weighted domains and skip or flag harder items to revisit later for efficient time management. Domain 1 — Platform Engineering Core Fundamentals (approx. 22 questions, \~36%) This is the largest and highest-weighted domain — focus most of your study time here. Expect conceptual and scenario-based questions that test platform architecture, core principles, and the declarative approach to platform operations. * Platform goals and approaches: developer velocity, standardization, self‑service, reliability, and trade-offs. * Platform architecture: scalable patterns, responsibilities split between platform and application teams. * DevOps and CI/CD concepts: cultural and technical foundations that enable platform engineering. * Declarative vs. imperative workflows: role of Infrastructure as Code and GitOps for versioned, auditable control. A presentation slide titled "Domain 1: Platform Engineering Core Fundamentals" with two labeled panels: 01 "Platform Goals and Approaches" and 02 "Platform Architecture." Each panel shows brief bullet points and a small icon (a target for goals and a blueprint/layout for architecture). A presentation slide titled "Domain 1: Platform Engineering Core Fundamentals" showing two boxed sections: "03 DevOps and CI/CD" with bullets about building on DevOps and improving developer speed, and "04 Declarative Resource" mentioning Infrastructure as Code and GitOps. The slide includes small icons for each section and a copyright note for KodeKloud. Expect mostly conceptual items and practical scenarios that require reasoning about architecture, trade-offs, and declarative control models. A slide titled "Domain 1: Platform Engineering Core Fundamentals" showing an illustration of a student at a desk with exam papers, a clock and a globe. A panel labeled "Exam Insights" notes about 22 questions expected and that questions will cover both concepts and practical application. Domain 2 — Observability, Security, and Conformance (approx. 12 questions, 20%) Covers observability primitives, platform and pipeline security, and governance/compliance practices. * Observability: traces, metrics, logs, and events—how to interpret signals for troubleshooting and performance tuning. * Security: service-to-service security, authentication/authorization, secrets management, and CI/CD pipeline security. * Governance and conformance: policy engines, compliance checks, and integrating governance into platform workflows. A presentation slide titled "Domain 2: Observability, Security, and Conformance" showing four circular icons labeled Observability, Security, Governance, and CI/CD Security. Each icon has a short descriptor underneath (e.g., traces/metrics/logs; service communication/Kubernetes; policy engines/compliance; pipeline protection). Expect scenario-based questions that require selecting observability strategies, security controls, or governance approaches appropriate to the platform context. Domain 3 — Continuous Delivery and Platform Engineering (approx. 10 questions, \~16%) Focuses on CI/CD pipelines and platform support for reliable delivery. * CI pipelines and best practices: build, test, artifact storage, promotion strategies. * GitOps: treating Git as the source of truth, reconciliation loops, and how GitOps contrasts with imperative automation. * Environments and promotion: dev, QA, staging, UAT, production workflows. * Incident response and operations: runbooks, alert design, and post‑mortem processes. A presentation slide titled "Domain 3: Continuous Delivery and Platform Engineering" showing four colored cards. The cards are labeled "CI Pipelines," "GitOps," "Application Environments," and "Incident Response" with brief subtitles about integration, workflows, deployment, and operational practices. The goal is to understand safe, repeatable flows to move code from repository to production and how platform patterns support that flow. Domain 4 — Platform APIs and Provisioning Infrastructure (approx. 7 questions, \~12%) Examines mechanisms that enable self‑service and automation for provisioning and lifecycle management. * Kubernetes reconciliation loops and controller fundamentals. * Custom Resource Definitions (CRDs) and operator patterns. * Infrastructure provisioning tools and integrations (e.g., Crossplane, Terraform, operators). * Self‑service APIs and lifecycle automation for platform consumers. A slide titled "Domain 4: Platform APIs and Provisioning Infrastructure" showing four circular icons and labels: Kubernetes Reconciliation Loop, APIs for Self‑Service (CRDs), Infrastructure Provisioning, and Operator Pattern. Each item includes a short subtitle describing concepts like core controller concepts, custom resource definitions, Kubernetes‑based automation, and integration techniques. Expect conceptual and scenario-based questions about extending Kubernetes, controller behavior, and enabling automated provisioning via platform APIs. Domain 5 — IDPs and Developer Experience (approx. 5 questions, \~8%) Covers integrated developer platforms (IDPs), service catalogs, developer portals, and designing low-friction self‑service experiences. * Platform capabilities: simplified access methods, common services, and abstractions to reduce cognitive load. * Service catalogs: API-driven discovery, consumption patterns, and lifecycle. * Developer portals and onboarding: adoption tooling, documentation, and workflows. * AI/ML integration: high-level roles for AI in platform automation and developer workflows. A slide titled "Domain 5: IDPs and Developer Experience" that lists four items: Platform Capabilities (simplified access methods), Service Catalogs (API-driven discovery), Developer Portals (platform adoption tools), and AI/ML Integration (platform automation). The items are numbered 01–04 and shown in colored boxes. Domain 6 — Measuring Your Platform (approx. 5 questions, \~8%) Measures how you evaluate platform success and quantify business value. * DORA metrics: deployment frequency, lead time for changes, change failure rate, time to restore service. * Adoption and efficiency: tracking platform adoption, cost-effectiveness, and developer productivity. * Business indicators: developer satisfaction, SLAs/SLIs, and measurable business impact. A presentation slide titled "Domain 6: Measuring Your Platform." It shows three numbered sections: "4 DORA Metrics — Key performance indicators," "2 Focus Areas — Platform efficiency, team productivity," and "5 Questions — Approximate exam coverage." Question counts are approximate and rounded; the summed total may differ from 60 by ±1. Use percentage weights to allocate study time proportionally across domains. Summary of domain focus areas | Domain | Primary focus | | - | - | | Domain 1 | Declarative concepts, platform architecture, platform goals (developer velocity, standardization) | | Domain 2 | Observability signals, security controls, governance and compliance | | Domain 3 | CI/CD/GitOps, promotion strategies, operational response | | Domain 4 | Extending Kubernetes: controllers, CRDs, provisioning integrations | | Domain 5 | IDPs, developer portals, service catalogs, adoption-focused UX | | Domain 6 | Platform success metrics: DORA metrics, adoption, efficiency | About the exam questions * Format: multiple choice (typically four or five options). * Style: scenario-based and largely conceptual; questions emphasize reasoning and trade-off decisions. * Common pitfalls when answering: 1. Insufficient domain knowledge or context. 2. Making incorrect assumptions not supported by the scenario. 3. Misreading qualifiers (e.g., "not", "least", or scope restrictions). 4. Confusing tool-specific details with platform-agnostic principles. Final tips * Time management: aim for \~2 minutes per question, but spend more time on higher-weight domains (Domain 1 > Domains 2 & 3). * Study strategy: focus on concepts and scenario reasoning rather than memorizing tool-specific commands. * Practice: work through scenario questions about architecture trade-offs, GitOps workflows, observability choices, and governance decisions. * Prioritize: use the percentage weights in this blueprint to allocate study time effectively. The exam is proctored. Ensure you meet proctor requirements (valid ID, environment rules) and understand the testing platform before your exam appointment. You are now ready to use this blueprint as a study guide: 60 questions, 120 minutes, 75% to pass—focus on fundamentals, practice scenario reasoning, and manage your time. Links and references * [Kubernetes Concepts — Official Docs](https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/) * [OpenTelemetry — Observability tooling and standards](https://opentelemetry.io/) * [GitOps Principles (gitops.tech)](https://www.gitops.tech/) * [DORA Four Key Metrics (overview)](https://cloud.google.com/blog/products/devops-sre/dora-four-key-metrics) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.