What is the primary purpose of using multiple environments (e.g., development, staging, production) in a cloud native platform?
Answer(s): A
The primary reason for implementing multiple environments in cloud native platforms is to isolate the different phases of the software development lifecycle. Option A is correct because environments such as development, staging, and production enable testing and validation at each stage without impacting end users. Development environments allow rapid iteration, staging environments simulate production for integration and performance testing, and production environments serve real users.Option B (reducing costs) may be a side effect but is not the main purpose. Option C (distributing traffic) relates more to load balancing and high availability, not environment separation. Option D is the opposite of the goal--different environments often require tailored infrastructure to meet their distinct purposes.Isolation through multiple environments is fundamental to reducing risk, supporting continuous delivery, and ensuring stability. This practice also allows for compliance checks, automated testing, and user acceptance validation before changes reach production.
-- CNCF Platforms Whitepaper-- Team Topologies & Platform Engineering Guidance-- Cloud Native Platform Engineering Study Guide
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?
Answer(s): D
Prometheus is the de facto standard for collecting and monitoring metrics in Kubernetes and other cloud native environments. Option D is correct because Prometheus is a CNCF graduated project designed for multi-dimensional data collection, time-series storage, and powerful querying using PromQL. It integrates seamlessly with Kubernetes, automatically discovering targets such as Pods and Services through service discovery.Option A (Grafana) is widely used for visualization but relies on Prometheus or other data sources to collect metrics. Option B (ELK Stack) is better suited for log aggregation rather than real-time metrics. Option C (OpenTelemetry) provides standardized instrumentation but is focused on generating and exporting metrics, logs, and traces rather than storage, querying, and alerting.Prometheus plays a central role in platform observability strategies, often paired with Alertmanager for notifications and Grafana for dashboards. Together, they enable proactive monitoring, SLO/SLI measurement, and incident detection, making Prometheus indispensable in cloud native platform engineering.
-- CNCF Observability Whitepaper-- Prometheus CNCF Project Documentation-- Cloud Native Platform Engineering Study Guide
Which platform component enables one-click provisioning of sandbox environments, including both infrastructure and application code?
A CI/CD pipeline is the platform component that enables automated provisioning of sandbox environments with both infrastructure and application code. Option A is correct because modern pipelines integrate Infrastructure as Code (IaC) with application deployment, enabling "one-click" or self-service provisioning of complete environments. This capability is central to platform engineering because it empowers developers to spin up temporary or permanent sandbox environments quickly for testing, experimentation, or demos.Option B (service mesh) focuses on secure, observable service-to-service communication but does not provision environments. Option C (service bus) is used for asynchronous communication between services, not environment provisioning. Option D (observability pipeline) deals with collecting telemetry data, not provisioning.By leveraging CI/CD pipelines integrated with GitOps and IaC tools (such as Terraform, Crossplane, or Kubernetes manifests), platform teams ensure consistency, compliance, and automation. Developers benefit from reduced friction, faster feedback cycles, and a better overall developer experience.
-- CNCF Platforms Whitepaper-- CNCF GitOps Principles-- Cloud Native Platform Engineering Study Guide
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?
The most sustainable solution for managing developer access while balancing governance and self- service is to adopt GitOps-based RBAC management. Option A is correct because it leverages Git as the source of truth for access permissions, allowing developers to request access through pull requests. For non-sensitive environments such as staging, approvals can be automated, ensuring efficiency while still maintaining auditability. This approach aligns with platform engineering principles of self-service, automation, and compliance.Option B places the burden entirely on one engineer, which does not scale. Option C introduces bottlenecks, delays, and reduces developer experience. Option D bypasses governance and auditability, potentially creating security risks.GitOps for RBAC not only improves developer experience but also ensures all changes are versioned, reviewed, and auditable. This model supports compliance while reducing manual intervention from the platform team, thus enhancing efficiency.
-- CNCF GitOps Principles-- CNCF Platforms Whitepaper-- Cloud Native Platform Engineering Study Guide
In a GitOps approach, how should the desired state of a system be managed and integrated?
The GitOps model is built on the principle that the desired state of infrastructure and applications must be stored in Git as the single source of truth. Option D is correct because Git provides versioning, immutability, and auditability, while reconciliation controllers (e.g., Argo CD or Flux) pull the desired state into the system continuously. This ensures that actual cluster state always matches the declared Git state.Option A is partially correct but fails because GitOps eliminates manual push workflows-- automation ensures changes are pulled and reconciled. Option B describes Kubernetes CRDs, which may be part of the system but do not embody GitOps on their own. Option C contradicts GitOps principles, which rely on pull-based reconciliation, not centralized push.Storing desired state in Git provides full traceability, automated rollbacks, and continuous reconciliation, improving reliability and compliance. This makes GitOps a core practice for cloud native platform engineering.
Post your Comments and Discuss Linux Foundation CNPA exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CNPA content, but please register or login to continue.