Question 1

In the context of observability for cloud native platforms, which of the following best describes the role of OpenTelemetry?

Accepted Answer

C

Explanation: OpenTelemetry is a Cloud Native Computing Foundation (CNCF) project designed to create a unified, vendor-neutral standard for observability data. It provides a collection of APIs, SDKs, and tools to instrument applications and infrastructure for generating, collecting, and exporting telemetry data—specifically traces, metrics, and logs. This standardization allows organizations to use a consistent approach for observability across different services and platforms, avoiding vendor lock-in and simplifying the process of data collection and transmission to various analysis backends. Its primary role is to provide this standardized framework, not to be a backend or analysis tool itself.

Question 2

Which of the following is a primary benefit of using Kubernetes Custom Resource Definitions (CRDs) in a self-service platform model?

Accepted Answer

C

Explanation: The primary benefit of Custom Resource Definitions (CRDs) is that they provide a native mechanism to extend the Kubernetes API. In a self-service platform model, this allows a platform team to define their own custom API objects (e.g., Database, MessageQueue, Tenant) that represent managed services. Application developers can then interact with these high-level abstractions using standard Kubernetes tools (kubectl, GitOps) and declarative manifests, without needing to understand the underlying implementation details. This is accomplished without modifying or forking the core Kubernetes API server code, ensuring the platform remains maintainable and aligned with the upstream Kubernetes project.

Question 3

Which key observability signal helps detect real-time performance bottlenecks in a Kubernetes cluster?

Accepted Answer

C

Explanation: Metrics are numerical, time-series data representing the state of a system, such as CPU utilization, memory consumption, or request latency. They are lightweight, easily aggregated, and ideal for real-time visualization on dashboards and for triggering alerts. This continuous, quantitative data stream allows operators to immediately observe trends, spikes, and saturation points that indicate performance bottlenecks across the Kubernetes cluster. Tools like Prometheus are designed specifically to collect and analyze these metrics for real-time performance monitoring.

Question 4

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

Accepted Answer

C

Explanation: Automated builds are a core component of Continuous Integration (CI) that ensures every build is executed in a standardized and repeatable manner. By using a version-controlled script, the process of compiling source code, linking dependencies, and packaging the application is performed identically every time it is triggered. This eliminates inconsistencies and errors that arise from manual builds, where different developers might use slightly different environments, tool versions, or procedures. The primary benefit is this consistency, which creates a reliable foundation for subsequent testing and deployment stages, ensuring that any detected failures are due to code changes, not variations in the build process itself.

Question 5

A developer is struggling to access the necessary services on a cloud native platform due to complex Kubernetes configurations. What approach can best simplify their access to platform capabilities?

Accepted Answer

B

Explanation: A web portal acts as an abstraction layer, simplifying the developer experience by hiding the underlying complexities of Kubernetes. Instead of writing complex YAML manifests or using kubectl commands, developers can interact with a user-friendly graphical interface to deploy applications, view logs, and manage services. This approach, central to the concept of an Internal Developer Platform (IDP), reduces the cognitive load on developers, enabling them to self-serve capabilities efficiently without needing to be Kubernetes experts. This directly addresses the problem of complex configurations hindering access to necessary services.

Question 6

During a CI/CD pipeline setup, at which stage should the Software Bill of Materials (SBOM) be generated to provide most valuable insights into dependencies?

Accepted Answer

C

Explanation: The build process is the most effective stage for generating a Software Bill of Materials (SBOM). During this phase, all source code, libraries, and third-party dependencies are definitively resolved and compiled into the final software artifact (e.g., a container image or executable). Generating the SBOM at this point ensures it is an exact, accurate inventory of every component and its specific version included in the deliverable. This provides the most valuable and actionable data for security scanning, license compliance, and vulnerability analysis before the artifact proceeds to testing and deployment, aligning with secure software development lifecycle principles.

Question 7

In a cloud native environment, which approach is effective for managing resources to ensure a balance between defined states and dynamic adjustments?

Accepted Answer

C

Explanation: Declarative resource management is a core principle of cloud-native systems. It involves defining the desired state of the system in configuration files (e.g., YAML manifests). A control plane, such as the Kubernetes controller manager, then continuously monitors the system's actual state and automatically takes action to reconcile any differences, ensuring it matches the declared state. This model effectively balances a predefined configuration with the need for dynamic, autonomous adjustments, such as self-healing by replacing failed pods or auto-scaling based on load. It provides a robust, predictable, and automated approach to managing complex, distributed environments.

Question 8

A software development team is struggling to adopt a new cloud native platform efficiently. How can a centralized developer portal, such as Backstage, help improve their adoption process?

Accepted Answer

A

Explanation: A centralized developer portal like Backstage acts as a "single pane of glass" for engineering teams. It unifies infrastructure tooling, service catalogs, software templates, and technical documentation into one consistent user interface. This centralization is critical for efficient cloud-native adoption as it reduces cognitive load on developers, who no longer need to hunt for disparate resources. By providing a single, discoverable access point for all platform services and knowledge, it streamlines onboarding, accelerates development workflows, and ensures that teams can easily find and use the tools and standards provided by the platform engineering team.

Question 9

In a GitOps workflow, how should application environments be managed when promoting an application from staging to production?

Accepted Answer

A

Explanation: The core principle of GitOps is using a Git repository as the single source of truth for the desired state of an application. The promotion of an application from a staging to a production environment is managed through Git operations. Typically, a pull request is created to merge the validated configuration from a staging branch into the production branch. Once this merge is approved and completed, a GitOps operator (e.g., Argo CD, Flux) automatically detects the change in the production branch. It then pulls the new declarative configuration and applies it to the production cluster, reconciling its live state with the newly defined desired state in Git.

Question 10

As a Cloud Native Platform Associate, you need to implement an observability strategy for your
Kubernetes clusters. Which of the following tools is most commonly used for collecting and
monitoring metrics in cloud native environments?

Accepted Answer

D

Explanation: Prometheus is a Cloud Native Computing Foundation (CNCF) graduated project specifically designed for monitoring and alerting in dynamic, microservices-based environments like Kubernetes. It operates on a pull-based model, actively scraping (collecting) time-series metrics from configured endpoints. Its powerful query language (PromQL) and integration with the Kubernetes service discovery mechanism make it the de facto standard for collecting and monitoring metrics within the cloud native ecosystem. It serves as the core data source for metrics-based observability.

Question 11

Development teams frequently raise support tickets for short-term access to staging clusters,
creating a growing burden on the platform team. What's the best long-term solution to balance
control, efficiency, and developer experience?

Accepted Answer

A

Explanation: Using GitOps to manage Kubernetes RBAC (Role-Based Access Control) provides the best long-term balance. This approach treats access control configurations as code, stored in a Git repository. Developers request access via pull requests (PRs), creating a transparent and auditable trail. Automating the PR approval and merge process for non-sensitive environments, like staging, eliminates the manual burden on the platform team. This empowers developers with a self-service workflow they are already familiar with, improving efficiency and experience while maintaining strict, version-controlled governance over cluster access.

Question 12

In a GitOps workflow using Crossplane, how is infrastructure provisioned across multiple clusters?

Accepted Answer

B

Explanation: The core principle of a GitOps workflow is using Git as the single source of truth for declarative infrastructure and applications. Crossplane extends Kubernetes with Custom Resource Definitions (CRDs) that represent external infrastructure (e.g., S3 buckets, RDS instances). In this model, the desired state of the infrastructure for one or more clusters is defined as YAML manifests and committed to a Git repository. Crossplane's controllers, running in a management cluster, continuously watch these resources and reconcile the actual state of the infrastructure in the cloud provider with the desired state declared in Git, creating, updating, or deleting resources automatically.

Question 13

Which IaC approach ensures Kubernetes infrastructure maintains its desired state automatically?

Accepted Answer

A

Explanation: The declarative approach is fundamental to Kubernetes' design for Infrastructure as Code (IaC). In this model, a user defines the desired state of the system in a manifest file (e.g., a YAML file describing a Deployment with three replicas). The Kubernetes control plane then continuously works to match the cluster's actual state to this desired state. This is achieved through a reconciliation loop, where controllers monitor resources and automatically take corrective action—such as restarting a failed pod or scaling a service—to enforce the declared configuration. This ensures the infrastructure self-heals and maintains its intended state without direct, step-by-step commands.

Question 14

What is a key cultural aspect that drives successful platform adoption in an organization?

Accepted Answer

D

Explanation: Successful platform adoption is fundamentally a socio-technical challenge that hinges on treating the internal platform as a product and its users (developers) as customers. A key cultural aspect is establishing continuous feedback loops where developers can easily provide input on the platform's functionality and usability. This collaborative approach ensures the platform evolves to meet the actual needs of its users, which increases its value and encourages voluntary adoption. This product-centric mindset fosters trust, improves the developer experience, and ultimately drives the platform's success more effectively than mandates or technical purity alone.

Question 15

A developer is tasked with securing a Kubernetes cluster and needs to implement Role-Based Access
Control (RBAC) to manage user permissions. Which of the following statements about RBAC in
Kubernetes is correct?

Accepted Answer

D

Explanation: Role-Based Access Control (RBAC) is a fundamental security mechanism in Kubernetes for regulating access to API resources. It operates on four key API objects: Role, ClusterRole, RoleBinding, and ClusterRoleBinding. A Role or ClusterRole contains rules that represent a set of permissions, defining which actions (verbs like get, list, create) are allowed on specific resources (like pods, deployments). A RoleBinding or ClusterRoleBinding then grants these defined permissions to a set of subjects (users, groups, or ServiceAccounts), effectively connecting a role to a user.

Free Linux Foundation CNPA Actual Exam Questions