CNPA Exam Dumps and Practice Questions

The Kubernetes reconciliation loop ensures that the actual state of a resource matches the desired state defined in its manifest. If the replica count of a Deployment is changed from 3 to 5, option B is correct: Kubernetes will automatically create two new Pods to satisfy the new desired replica count.

Option A is incorrect because Deployments are not deleted; they are updated in place. Option C contradicts Kubernetes' declarative model---no manual intervention is required. Option D is wrong because Kubernetes does not restart existing Pods unless necessary; it simply adds additional Pods.

This reconciliation process is core to Kubernetes' declarative infrastructure approach, where desired states are continuously monitored and enforced. It reduces human toil and ensures consistency, making it fundamental for platform engineering practices like GitOps.

--- CNCF Kubernetes Documentation

--- CNCF GitOps Principles

--- Cloud Native Platform Engineering Study Guide

OpenCost is the CNCF-supported open-source project designed specifically for Kubernetes cost visibility and optimization. Option B is correct because OpenCost provides granular, real-time allocation of Kubernetes costs across namespaces, workloads, and teams. This allows organizations to understand true cost drivers and optimize resource utilization effectively.

Option A (APM tools) may track performance but usually lack deep integration with Kubernetes cost allocation. Option C provides partial visibility but requires complex manual correlation of resource usage with billing data. Option D (cloud provider estimators) typically offer limited or high-level insights and do not map costs down to Kubernetes workloads.

By adopting OpenCost, platform teams can align financial accountability with engineering usage, a practice known as FinOps. This supports sustainable scaling, cost efficiency, and transparency---critical aspects of measuring platform success.

--- CNCF OpenCost Project

--- CNCF Platforms Whitepaper

--- Cloud Native Platform Engineering Study Guide

Mutual TLS (mTLS) is the core mechanism for securing service-to-service communication in cloud native environments. Option B is correct because mTLS provides encryption in transit and mutual authentication, ensuring both the client and server verify each other's identity. This prevents unauthorized access, man-in-the-middle attacks, and data leakage.

Option A (API Gateway) manages ingress traffic from external clients but does not secure internal service-to-service communication. Option C (Service Mesh) is a broader infrastructure layer (e.g., Istio, Linkerd) that implements mTLS, but mTLS itself is the mechanism that enforces secure communications. Option D (Load Balancer) distributes traffic but does not handle encryption or authentication.

mTLS is foundational to zero-trust networking inside Kubernetes clusters. Service meshes typically provide automated certificate management and policy enforcement, ensuring seamless adoption of mTLS without requiring developers to modify application code.

--- CNCF Service Mesh Whitepaper

--- CNCF Platforms Whitepaper

--- Cloud Native Platform Engineering Study Guide

OpenTelemetry is an open-source CNCF project that provides vendor-neutral, standardized APIs, SDKs, and agents for collecting and exporting observability data such as metrics, logs, and traces. Option C is correct because OpenTelemetry's purpose is to unify how telemetry data is generated, transmitted, and consumed, regardless of which backend (e.g., Prometheus, Jaeger, Elastic, commercial APM tools) is used.

Option A is incorrect because OpenTelemetry supports all three signal types (metrics, logs, traces), not just logs. Option B is incorrect because it is an open, community-driven standard and not tied to a single vendor or cloud provider. Option D is misleading because OpenTelemetry covers distributed applications, services, and infrastructure---far beyond just infrastructure monitoring.

OpenTelemetry reduces vendor lock-in and promotes interoperability, making it a cornerstone of cloud native observability strategies. Platform engineering teams rely on it to ensure consistent data collection, enabling better insights, faster debugging, and improved reliability of cloud native platforms.

--- CNCF Observability Whitepaper

--- OpenTelemetry CNCF Project Documentation

--- Cloud Native Platform Engineering Study Guide

One of the primary objectives of internal developer platforms (IDPs) is to improve developer experience by reducing cognitive load. Complex Kubernetes configurations often overwhelm developers who simply want to consume services and deploy code without worrying about infrastructure intricacies.

Option B is correct because implementing a self-service web portal (or developer portal) abstracts away Kubernetes complexities, providing developers with easy access to platform services through standardized workflows, templates, and golden paths. This aligns with platform engineering principles: empowering developers with self-service capabilities while maintaining governance, security, and compliance.

Option A increases burden unnecessarily and negatively impacts productivity. Option C limits access to services, reducing flexibility and developer autonomy, which goes against the core goal of IDPs. Option D, while helpful for education, does not remove complexity---it only shifts the responsibility back to the developer. By leveraging portals, APIs, and automation, platform teams allow developers to focus on building business value instead of managing infrastructure details.

--- CNCF Platforms Whitepaper

--- Team Topologies and Platform Engineering Practices

--- Cloud Native Platform Engineering Study Guide