Linux Foundation CNPA Exam Questions Instant Access

Question 1

In a scenario where an Internal Developer Platform (IDP) is being used to enable developers to self-service provision products and capabilities such as Namespace-as-a-Service, which answer best describes who is responsible for resolving application-related incidents?

AA separate team is created which includes people previously from the platform and application teams to solve all problems for the organization.

BPlatform teams delegate appropriate permissions to the application teams to allow them to self-manage and resolve any underlying infrastructure and application-related problems.

CPlatform teams are responsible for investigating and resolving underlying infrastructure problems whilst application teams are responsible for investigating and resolving application-related problems.

DPlatform teams are responsible for investigating and resolving all problems related to the platform, including application ones, before the app teams notice.

Answer : C

Platform engineering clearly separates responsibilities between platform teams and application teams. Option C is correct because platform teams manage the platform and infrastructure layer, ensuring stability, compliance, and availability, while application teams own their applications, including troubleshooting application-specific issues.

Option A (creating a single merged team) introduces inefficiency and removes specialization. Option B incorrectly suggests application teams should also solve infrastructure issues, which conflicts with platform-as-a-product principles. Option D places all responsibilities on platform teams, which creates bottlenecks and undermines application team ownership.

By splitting responsibilities, IDPs empower developers with self-service provisioning while maintaining clear boundaries. This ensures both agility and accountability: platform teams focus on enabling and securing the platform, while application teams take ownership of their code and services.

--- CNCF Platforms Whitepaper

--- Team Topologies (Platform as a Product Model)

--- Cloud Native Platform Engineering Study Guide

Question 2

A Cloud Native Platform Engineer is tasked with improving the integration between teams through effective API management. Which aspect of API-driven initiatives is most crucial for fostering collaboration in platform engineering?

AAPIs must be documented properly to ensure all teams understand how to use them.

BAPIs should be released without versioning to simplify maintenance.

CAPIs should be tightly coupled to specific teams to enforce accountability.

DAPIs should be designed to be as complex as possible to accommodate all potential use cases.

Answer : A

Proper documentation is critical for fostering collaboration through APIs. Option A is correct because well-documented APIs ensure that all teams---platform engineers, developers, and operations---understand how to consume and integrate services effectively. Clear documentation reduces friction, accelerates adoption, and minimizes support overhead.

Option B (no versioning) is poor practice, as versioning ensures backward compatibility and safe upgrades. Option C (tight coupling) restricts collaboration and creates silos, which goes against platform engineering principles. Option D (complex design) reduces usability and increases cognitive load, the opposite of platform goals.

APIs serve as the contracts between teams and systems. In platform engineering, well-documented, versioned, and abstracted APIs provide a consistent and predictable way to interact with platform services, improving collaboration and developer experience.

--- CNCF Platforms Whitepaper

--- Team Topologies Guidance

--- Cloud Native Platform Engineering Study Guide

Question 3

In assessing the effectiveness of platform engineering initiatives, which DORA metric most directly correlates to the time it takes for code from its initial commit to be deployed into production?

ALead Time for Changes

BDeployment Frequency

CMean Time to Recovery

DChange Failure Rate

Answer : A

Lead Time for Changes is a DORA (DevOps Research and Assessment) metric that measures the time from code commit to successful deployment in production. Option A is correct because it directly reflects how quickly the platform enables developers to turn ideas into delivered software. Shorter lead times indicate an efficient delivery pipeline, streamlined workflows, and effective automation.

Option B (Deployment Frequency) measures how often code is deployed, not how long it takes to reach production. Option C (Mean Time to Recovery) measures operational resilience after failures. Option D (Change Failure Rate) indicates stability by measuring the percentage of deployments causing incidents. While all DORA metrics are valuable, only Lead Time for Changes measures end-to-end speed of delivery.

In platform engineering, improving lead time often involves automating CI/CD pipelines, implementing GitOps, and reducing manual approvals. It is a core measurement of developer experience and platform efficiency.

--- CNCF Platforms Whitepaper

--- Accelerate: State of DevOps Report (DORA Metrics)

--- Cloud Native Platform Engineering Study Guide

Question 4

In a Continuous Integration (CI) pipeline, what is a key benefit of using automated builds?

AMinimizes server costs.

BEliminates coding errors.

CEnsures consistent builds.

DReduces code redundancy.

Answer : C

The key benefit of automated builds in a CI pipeline is ensuring consistent and reproducible builds. Option C is correct because automation eliminates the variability introduced by manual processes, guaranteeing that each build follows the same steps, uses the same dependencies, and produces artifacts that are predictable and testable.

Option A (minimizing server costs) may be a side effect but is not the primary advantage. Option B (eliminates coding errors) is inaccurate---automated builds do not prevent developers from writing faulty code; instead, they surface errors earlier. Option D (reduces code redundancy) relates more to code design than CI pipelines.

Automated builds are fundamental to DevOps and platform engineering because they establish reliability in the software supply chain, integrate seamlessly with automated testing, and enable continuous delivery. This practice ensures that code changes are validated quickly, improving developer productivity and reducing integration risks.

--- CNCF Platforms Whitepaper

--- Continuous Delivery Foundation Best Practices

--- Cloud Native Platform Engineering Study Guide

Question 5

For a cloud native platform handling sensitive customer data, which approach ensures compliance with data privacy regulations like GDPR and PCI DSS within a Kubernetes environment?

ARelying on default cloud provider IAM policies with minimal Kubernetes customizations.

BUtilizing standard Kubernetes Secrets with encrypted storage and manual access reviews.

CDeploying a policy engine like Open Policy Agent (OPA) with real-time data masking and audit logging.

DImplementing Kubernetes Role-based access control (RBAC) with basic network policies and periodic manual audits.

Answer : C

Compliance with regulations like GDPR and PCI DSS requires fine-grained control, auditing, and data protection. Option C is correct because deploying a policy engine like Open Policy Agent (OPA) enables dynamic enforcement of policies, real-time data masking, and comprehensive audit logging. This ensures sensitive data is protected while providing traceability and compliance reporting.

Option A is insufficient, as default IAM policies without Kubernetes-level governance do not provide the granularity required for compliance. Option B (Kubernetes Secrets) adds encryption but lacks auditability and runtime enforcement. Option D (RBAC and network policies) improves security posture but does not provide comprehensive compliance coverage or data privacy features like masking and logging.

OPA and similar tools integrate with Kubernetes admission control to enforce compliance policies consistently, providing the flexibility and auditability needed in regulated industries.

--- CNCF Security TAG Best Practices

--- CNCF Platforms Whitepaper

--- Cloud Native Platform Engineering Study Guide

Question 6

Which of the following would be considered an advantage of using abstract APIs when offering cloud service provisioning and management as platform services?

AAbstractions enforce explicit platform team approval before any cloud resource is deployed.

BAbstractions curate cloud services with built-in guardrails for development teams.

CAbstractions allow customization of cloud services and resources without guardrails.

DDevelopment teams can arbitrarily deploy cloud services via abstractions.

Answer : B

Abstract APIs are an essential component of platform engineering, providing a simplified interface for developers to consume infrastructure and cloud services without deep knowledge of provider-specific details. Option B is correct because abstractions allow platform teams to curate services with built-in guardrails, ensuring compliance, security, and operational standards are enforced automatically. Developers get the benefit of self-service and flexibility while the platform team ensures governance.

Option A would slow down the process, defeating the purpose of abstraction. Option C removes guardrails, which risks security and compliance violations. Option D allows uncontrolled deployments, which can create chaos and undermine platform governance.

Abstract APIs strike the balance between developer experience and organizational control. They provide golden paths and opinionated defaults while maintaining the flexibility needed for developer productivity. This approach ensures efficient service provisioning at scale with reduced cognitive load on developers.

--- CNCF Platforms Whitepaper

--- CNCF Platform Engineering Maturity Model

--- Cloud Native Platform Engineering Study Guide

Question 7

What is the primary goal of platform engineering?

ATo focus exclusively on infrastructure automation without considering developer needs

BTo limit developer access to infrastructure to enhance security and compliance.

CTo replace all DevOps practices with automated tools and well-defined processes.

DTo create reusable, scalable platforms that improve developer productivity and experience.

Answer : D

The primary goal of platform engineering is to create reusable, scalable platforms that improve both developer productivity and developer experience. Option D is correct because platform engineering treats the platform as a product, providing self-service capabilities, abstractions, and golden paths that reduce cognitive load for developers while embedding organizational guardrails.

Option A is too narrow---platform engineering is not limited to infrastructure automation but extends to developer usability, observability, and governance. Option B is incorrect because limiting access contradicts the principle of empowering developers through self-service. Option C is misleading; platform engineering complements DevOps practices but does not replace them.

By enabling developers to consume infrastructure and platform services through self-service APIs and portals, platform teams accelerate delivery cycles while maintaining compliance and security. This approach results in improved efficiency, reduced toil, and better alignment between business and engineering outcomes.

--- CNCF Platforms Whitepaper

--- CNCF Platform Engineering Maturity Model

--- Cloud Native Platform Engineering Study Guide

Linux Foundation Certified Cloud Native Platform Engineering Associate CNPA Exam Questions