CNPA Free Study Guide! with New Update 87 Exam Questions
Get up-to-date Real Exam Questions for CNPA UPDATED [2026]
Linux Foundation CNPA Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
NEW QUESTION # 44
A company is implementing a service mesh for secure service-to-service communication in their cloud native environment. What is the primary benefit of using mutual TLS (mTLS) within this context?
- A. Enables logging of all service communications for audit purposes.
- B. Allows services to authenticate each other and secure data in transit.
- C. Simplifies the deployment of microservices by automatically scaling them.
- D. Allows services to bypass security checks for better performance.
Answer: B
Explanation:
Mutual TLS (mTLS) is a core feature of service meshes, such as Istio or Linkerd, that enhances security in cloud native environments by ensuring that both communicating services authenticate each other and that the communication channel is encrypted. Option A is correct because mTLS delivers two critical benefits:
authentication (verifying the identity of both client and server services) and encryption (protecting data in transit from interception or tampering).
Option B is incorrect because mTLS does not bypass security-it enforces it. Option C is partly true in that service meshes often support observability and logging, but that is not the primary purpose of mTLS. Option D relates to scaling, which is outside the scope of mTLS.
In platform engineering, mTLS is a fundamental security mechanism that provides zero-trust networking between microservices, ensuring secure communication without requiring application-level changes. It strengthens compliance with security and data protection requirements, which are crucial in regulated industries.
References:- CNCF Service Mesh Whitepaper- CNCF Platforms Whitepaper- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 45
A platform engineering team is building an Internal Developer Platform (IDP). Which of the following enables application teams to manage infrastructure resources independently, without requiring direct platform team support?
- A. Manual infrastructure deployment services.
- B. Self-service resource provisioning APIs.
- C. A comprehensive platform knowledge center.
- D. Centralized logging and monitoring interfaces.
Answer: B
Explanation:
The defining capability of an IDP is enabling self-service so developers can independently access infrastructure and platform resources. Option D is correct because self-service resource provisioning APIs allow developers to provision resources such as namespaces, databases, or environments without relying on manual intervention from the platform team. These APIs embed governance, compliance, and organizational guardrails while giving autonomy to development teams.
Option A (manual deployment services) defeats the purpose of self-service. Option B (knowledge centers) improve documentation but do not provide automation. Option C (logging/monitoring interfaces) are observability tools, not resource provisioning mechanisms.
Self-service APIs empower developers, reduce cognitive load, and minimize bottlenecks. They also align with the platform engineering principle of "treating the platform as a product," where developers are customers, and the platform offers curated golden paths to simplify consumption of infrastructure and services.
References:- CNCF Platforms Whitepaper- CNCF Platform Engineering Maturity Model- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 46
As a platform engineer, how do you automate application deployments across multiple Kubernetes clusters using GitOps, Helm, and Crossplane, ensuring a consistent application state?
- A. Employ a GitOps controller to synchronize Git-stored Helm and Crossplane configurations.
- B. Use Helm and Crossplane, with manual GUI-based configuration updates.
- C. Leverage Git for configuration storage, with manual application of Helm and Crossplane.
- D. Integrate Helm and Crossplane into a GitOps-enabled CI/CD pipeline.
Answer: A
Explanation:
The most effective way to achieve consistent, automated deployments across multiple Kubernetes clusters is to combine GitOps controllers (e.g., Argo CD, Flux) with declarative configurations managed by Helm and Crossplane. Option A is correct because the GitOps controller continuously reconciles the desired state stored in Git-Helm charts for applications and Crossplane manifests for infrastructure-ensuring consistency across clusters.
Option B and D rely on manual updates, which are error-prone and not scalable. Option C mischaracterizes GitOps by suggesting push-based pipelines rather than the core GitOps model of pull-based reconciliation.
This combination leverages Helm for application packaging, Crossplane for cloud infrastructure provisioning, and GitOps for declarative, version-controlled delivery. It ensures applications remain in sync with Git, providing auditability, automation, and resilience in multi-cluster environments.
References:- CNCF GitOps Principles- CNCF Platforms Whitepaper- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 47
Which of the following best represents an effective golden path implementation in platform engineering?
- A. An API service catalog providing comprehensive details about available infrastructure components and their consumption patterns.
- B. A central documentation repository listing available database services with their configuration parameters.
- C. A monitoring dashboard system that displays the operational health metrics and alerting thresholds for all platform services.
- D. A templated workflow that guides developers through deploying a complete microservice with integrated testing and monitoring.
Answer: D
Explanation:
A golden path in platform engineering refers to a curated, opinionated workflow that makes the easiest way the right way for developers. Option C is correct because a templated workflow for deploying a microservice with integrated testing and monitoring embodies the golden path concept. It provides developers with a pre-validated, secure, and efficient approach that reduces cognitive load and accelerates delivery.
Option A (documentation) provides information but lacks automation and enforced best practices. Option B (monitoring dashboards) improves observability but does not guide developers in delivery workflows. Option D (API service catalog) is useful but more about service discovery than curated workflows.
Golden paths improve adoption by embedding guardrails, automation, and organizational standards directly into workflows, making compliance seamless. They ensure consistency while allowing developers to focus on innovation rather than platform complexity.
References:- CNCF Platforms Whitepaper- Team Topologies & Platform Engineering Practices- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 48
In a cloud native environment, which approach is effective for managing resources to ensure a balance between defined states and dynamic adjustments?
- A. Manual Resource Tracking
- B. Static Resource Allocation
- C. Declarative Resource Management
- D. Imperative Resource Management
Answer: C
Explanation:
Declarative resource management is a core principle in Kubernetes and cloud native platforms. Option C is correct because declarative systems define the desired state of resources (e.g., YAML manifests for Deployments, Services, or ConfigMaps), and controllers reconcile the actual state to match the desired state.
This provides consistency, automation, and resilience, while also allowing dynamic adjustments like scaling.
Option A (imperative management) requires step-by-step commands, which are error-prone and not scalable.
Option B (manual tracking) adds overhead and risk of drift. Option D (static allocation) wastes resources and does not adapt to changing workloads.
Declarative management enables GitOps workflows, automated scaling, and consistent application of policies.
This approach aligns with platform engineering principles by combining automation with governance, enabling efficiency and reliability at scale.
References:- CNCF GitOps Principles- Kubernetes Design Principles- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 49
Which CI/CD tool is specifically designed as a continuous delivery platform for Kubernetes that follows GitOps principles?
- A. Jenkins
- B. CircleCI
- C. TravisCI
- D. Argo CD
Answer: D
Explanation:
Argo CD is a GitOps-native continuous delivery tool specifically designed for Kubernetes. Option B is correct because Argo CD continuously monitors Git repositories for desired application state and reconciles Kubernetes clusters accordingly. It is declarative, Kubernetes-native, and aligned with GitOps principles, making it a key tool in platform engineering.
Option A (TravisCI) and Option C (CircleCI) are CI/CD systems but not Kubernetes-native or GitOps-driven.
Option D (Jenkins) is a widely used CI/CD tool but operates primarily in a push-based model unless extended with plugins, and is not purpose-built for GitOps.
Argo CD provides automated deployments, drift detection, rollback, and auditability-features central to GitOps workflows. It simplifies multi-cluster management, enforces compliance, and reduces manual intervention, making it a leading choice in Kubernetes-based platform engineering.
References:- CNCF GitOps Principles- Argo CD CNCF Project Documentation- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 50
In a GitOps workflow using Crossplane, how is infrastructure provisioned across multiple clusters?
- A. By provisioning infrastructure manually in cloud provider consoles and documenting the steps in Git for future reference.
- B. By manually applying Crossplane manifests to each cluster using kubectl to provision resources as needed for the infrastructure.
- C. By using CI/CD pipelines to execute imperative scripts that create cloud infrastructure outside of Kubernetes in any cloud provider
- D. By defining infrastructure resources declaratively in Git, where Crossplane controllers reconcile and provision them automatically in target environments.
Answer: D
Explanation:
Crossplane integrates tightly with GitOps workflows by extending Kubernetes with infrastructure APIs.
Option B is correct because infrastructure resources (databases, networks, S3 buckets, etc.) are defined declaratively in Git repositories. Git becomes the single source of truth, while Crossplane controllers automatically reconcile the desired state into real infrastructure across supported cloud providers.
Option A reflects imperative scripting, which contradicts GitOps principles. Option C (manual provisioning) lacks automation, governance, and repeatability. Option D involves manual application with kubectl, which bypasses GitOps reconciliation loops.
With Crossplane and GitOps, teams achieve consistent, reproducible, and auditable infrastructure provisioning at scale. This enables full alignment with cloud native platform engineering principles of declarative management, self-service, and extensibility.
References:- CNCF Crossplane Documentation- CNCF GitOps Principles- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 51
In a multi-cluster Kubernetes setup, which approach effectively manages the deployment of multiple interdependent applications together as a unit?
- A. Direct deployments from CI/CD with Git configuration.
- B. Creating separate Git repositories per application.
- C. Using Helm for application packaging with manual deployments.
- D. Employing a declarative application deployment definition.
Answer: D
Explanation:
In multi-cluster Kubernetes environments, the challenge lies in consistently deploying interdependent applications across clusters while ensuring reliability and repeatability. The Cloud Native Platform Engineering guidance stresses the importance of a declarative approach to define applications as code, which enables teams to describe the entire application system-including dependencies, configuration, and policies-in a single manifest. This ensures that applications are treated as a cohesive unit rather than isolated workloads.
Option A is correct because declarative application deployment definitions (often managed through GitOps practices) allow for consistent and automated reconciliation of desired state versus actual state across multiple clusters. This approach supports scalability, disaster recovery, and compliance by ensuring identical deployments across environments.
Option B (separate repos per application) increases fragmentation and does not inherently manage interdependencies. Option C (direct deployments from CI/CD) bypasses the GitOps model, which reduces auditability and consistency. Option D (Helm with manual deployments) partially addresses packaging but lacks the automation and governance needed in a multi-cluster setup.
References:- CNCF GitOps Principles for Platforms- CNCF Platforms Whitepaper- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 52
Which of the following is a primary benefit of adopting a platform approach for managing application environments with diverse needs?
- A. It enables self-service infrastructure provisioning while supporting app-specific requirements and organizational standards.
- B. It enforces one infrastructure setup for all applications to reduce management complexity.
- C. It centralizes all deployments in one environment to improve control and visibility.
- D. It isolates application environments completely to maximize security and avoid shared resources.
Answer: A
Explanation:
The main advantage of a platform engineering approach is balancing self-service for developers with organizational governance and standardization. Option A is correct because platforms enable developers to provision infrastructure and application environments independently while embedding security, compliance, and operational guardrails. This ensures that applications with diverse needs (e.g., different scaling patterns, compliance requirements, or environments) can still operate within a unified governance framework.
Option B (isolation only) is sometimes required for compliance but does not address the broader benefit of balancing flexibility and standardization. Option C forces uniformity, which reduces adaptability for varied workloads. Option D (centralized deployments) reduces developer autonomy and scalability.
The platform approach enables golden paths, curated abstractions, and reusable services, allowing diverse applications to thrive while maintaining control. This balance is central to platform engineering's goal of reducing cognitive load and improving developer productivity.
References:- CNCF Platforms Whitepaper- CNCF Platform Engineering Maturity Model- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 53
A Platform Team is adopting the HEART framework to measure user experience of their developer portal.
Which of the following aspects does the HEART framework primarily focus on to help improve developer experience and platform performance?
- A. HEART focuses on Happiness, Engagement, Adoption, Retention, and Task success, enabling teams to track both qualitative and quantitative metrics for user experience.
- B. HEART tracks Happiness, Engagement, Adoption, Reliability, and Throughput, helping teams optimize infrastructure performance.
- C. HEART evaluates Hardware, Efficiency, Availability, Response times, and Throughput to measure and ensure platform reliability and performance.
- D. HEART focuses on Happiness, Efficiency, Availability, Reliability, and Throughput, enabling teams to assess both qualitative and quantitative aspects of platform performance.
Answer: A
Explanation:
The HEART framework was developed by Google to measure user experience using both qualitative and quantitative indicators. Option C is correct because HEART stands for Happiness, Engagement, Adoption, Retention, and Task success. In platform engineering, this framework is applied to measure developer experience with internal developer portals (IDPs) and other platform components.
Option A and D misrepresent the acronym by replacing its original user-experience focus with infrastructure- oriented metrics. Option B substitutes Reliability for Retention, which is incorrect.
By applying HEART, platform teams can measure satisfaction (Happiness), frequency of use (Engagement), onboarding success (Adoption), long-term value (Retention), and ability to complete tasks effectively (Task success). This helps teams identify pain points, iterate on golden paths, and improve the usability of their platform.
References:- CNCF Platforms Whitepaper- Google HEART Framework for UX Measurement- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 54
What is a key cultural aspect that drives successful platform adoption in an organization?
- A. Keeping platform development separate from application teams.
- B. Encouraging platform feedback loops from developers to improve usability.
- C. Prioritizing platform security over usability.
- D. Mandating that all teams must use the platform without exceptions
Answer: B
Explanation:
Successful platform adoption depends heavily on cultural practices that foster collaboration and continuous improvement. Option D is correct because feedback loops between developers and platform teams ensure that the platform evolves to meet developer needs while balancing security and governance. This aligns with the principle of treating the platform as a product, where developer experience is central.
Option A (mandates) often lead to resistance and shadow IT. Option B isolates platform teams, creating silos and reducing alignment with developer workflows. Option C is misleading-security is important, but overemphasizing it at the expense of usability hinders adoption.
Feedback-driven iteration creates trust, improves usability, and drives organic adoption. It transforms the platform into a valuable product that developers want to use, rather than one they are forced to adopt.
References:- CNCF Platforms Whitepaper- Team Topologies (Platform as a Product model)- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 55
In a cloud native environment, which factor most critically influences the need for customized CI pipeline configurations across different application types?
- A. The technical differences in build tools, testing frameworks, and artifact formats across programming languages.
- B. The organizational practice of assigning unique pipeline configurations based on application priority levels.
- C. The requirement to visually distinguish between different application pipelines in monitoring dashboards.
- D. The need to accommodate varying team sizes and developer expertise levels within the organization.
Answer: A
Explanation:
The biggest driver for customizing CI pipeline configurations across application types is technical differences between programming languages, frameworks, and artifact formats. Option B is correct because applications written in Java, Python, Go, or Node.js require different build tools (e.g., Maven, pip, go build, npm), testing frameworks, and packaging mechanisms. These differences must be reflected in the CI pipeline to ensure successful builds, tests, and artifact generation.
Option A (priority-based pipelines) is more of an organizational practice, not a technical necessity. Option C (team sizes and expertise) may influence usability but does not drive pipeline configuration. Option D (visual distinction) relates to dashboards and observability, not pipeline functionality.
Platform engineers often provide pipeline templates or abstractions that encapsulate these differences while standardizing security and compliance checks. This balances customization with consistency, enabling developers to use pipelines suited to their technology stack without fragmenting governance.
References:- CNCF Platforms Whitepaper- Continuous Delivery Foundation Guidance- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 56
What is the primary goal of platform engineering?
- A. To create reusable, scalable platforms that improve developer productivity and experience.
- B. To focus exclusively on infrastructure automation without considering developer needs
- C. To limit developer access to infrastructure to enhance security and compliance.
- D. To replace all DevOps practices with automated tools and well-defined processes.
Answer: A
Explanation:
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.
References:- CNCF Platforms Whitepaper- CNCF Platform Engineering Maturity Model- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 57
Which of the following is a primary benefit of using Kubernetes Custom Resource Definitions (CRDs) in a self-service platform model?
- A. CRDs enable platform teams to define custom APIs without modifying the Kubernetes API server code.
- B. CRDs automatically manage the scaling and failover of platform services without additional configuration.
- C. CRDs provide built-in support for multi-cloud deployments without additional tooling.
- D. CRDs eliminate the need for Role-based access control (RBAC) configurations in Kubernetes clusters.
Answer: A
Explanation:
Kubernetes Custom Resource Definitions (CRDs) extend the Kubernetes API by allowing platform teams to create and expose custom APIs without modifying the core Kubernetes API server code. Option C is correct because this extensibility enables teams to define new abstractions (e.g., Database, Application, or Environment resources) tailored to organizational needs, which developers can consume through a self- service model.
Option A is incorrect because scaling and failover are handled by controllers or operators, not CRDs themselves. Option B is wrong because RBAC is still required for access control over custom resources.
Option D is misleading because multi-cloud support depends on how CRDs and their controllers are implemented, not a built-in CRD feature.
By leveraging CRDs, platform teams can standardize workflows, hide complexity, and implement guardrails, all while presenting developers with simplified abstractions. This is central to platform engineering, as it empowers developers with self-service APIs while maintaining operational control.
References:- CNCF Platforms Whitepaper- Kubernetes Extensibility Documentation- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 58
During a Kubernetes deployment, a Cloud Native Platform Associate needs to ensure that the desired state of a custom resource is achieved. Which component of Kubernetes is primarily responsible for this task?
- A. Kubernetes API Server
- B. Kubernetes Scheduler
- C. Kubernetes Etcd
- D. Kubernetes Controller
Answer: D
Explanation:
The Kubernetes Controller is responsible for continuously reconciling the desired state with the actual state of resources, including custom resources. Option D is correct because controllers watch resources (via the API Server), detect deviations, and take corrective actions to match the desired state defined in manifests. For example, a Deployment controller ensures that the number of Pods matches the replica count, while custom controllers manage CRDs.
Option A (Scheduler) assigns Pods to nodes but does not reconcile state. Option B (Etcd) is the key-value store holding cluster state but does not enforce it. Option C (API Server) exposes the Kubernetes API and validates requests but does not enforce reconciliation.
Controllers embody Kubernetes' declarative management principle and are essential for operators, CRDs, and GitOps workflows that rely on automated state enforcement.
References:- CNCF Kubernetes Documentation- CNCF GitOps Principles- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 59
Which metric measures a cloud native platform's impact on developer productivity and deployment speed?
- A. Track average time from code commits to successful production deployment.
- B. Evaluate total security vulnerabilities detected during platform usage.
- C. Monitor overall cloud infrastructure cost and resource consumption.
- D. Measure total cloud resource utilization across all development teams.
Answer: A
Explanation:
The Lead Time for Changes metric, one of the DORA (DevOps Research and Assessment) metrics, directly measures the impact of a platform on developer productivity and deployment speed. Option B is correct because it reflects the average time taken from when code is committed until it is successfully deployed into production. A shorter lead time indicates that the platform enables faster feedback loops, quicker delivery of features, and overall improved developer experience.
Option A (infrastructure cost) and Option D (resource utilization) are important for operations but do not measure productivity or speed. Option C (security vulnerabilities) relates to platform security posture, not productivity.
By tracking lead time, organizations can evaluate how effective their platform is in enabling self-service, automation, and streamlined CI/CD workflows. Improvements in this metric demonstrate that the platform is successfully reducing friction for developers and accelerating value delivery to end users.
References:- CNCF Platforms Whitepaper- State of DevOps Report (DORA Metrics)- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 60
In a cloud native environment, how do policy engines facilitate a unified approach for teams to consume platform services?
- A. Integrates with CI/CD pipelines to streamline service provisioning.
- B. Enforces service-level agreements (SLAs) across all teams.
- C. Enforces strict compliance policies with security standards.
- D. Provides centralized reusable policies to ensure security and compliance.
Answer: D
Explanation:
Policy engines (such as Open Policy Agent - OPA or Kyverno) play a critical role in enforcing governance, security, and compliance consistently across cloud native platforms. Option D is correct because policy engines provide centralized, reusable policies that can be applied across clusters, services, and environments. This ensures that developers consume platform services in a compliant and secure manner, without needing to manage these controls manually.
Option A is partially correct but too narrow, as policies extend beyond compliance to include operational, security, and cost-control measures. Option B is not the primary function of policy engines, though integration with CI/CD is possible. Option C is incorrect because SLAs are business agreements, not enforced by policy engines directly.
Policy engines enforce guardrails like image signing, RBAC rules, resource quotas, and network policies automatically, reducing cognitive load for developers while giving platform teams confidence in compliance.
This supports the platform engineering principle of combining self-service with governance.
References:- CNCF Platforms Whitepaper- CNCF Security TAG (OPA, Kyverno)- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 61
In the context of observability for cloud native platforms, which of the following best describes the role of OpenTelemetry?
- A. OpenTelemetry is a proprietary solution that limits its use to specific cloud providers.
- B. OpenTelemetry is solely focused on infrastructure monitoring.
- C. OpenTelemetry is primarily used for logging data only.
- D. OpenTelemetry provides a standardized way to collect and transmit observability data.
Answer: D
Explanation:
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.
References:- CNCF Observability Whitepaper- OpenTelemetry CNCF Project Documentation- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 62
As a Cloud Native Platform Associate, you are tasked with improving software delivery efficiency using DORA metrics. Which of the following metrics best indicates the effectiveness of your platform initiatives?
- A. Mean Time to Recover (MTTR)
- B. Service Level Agreements (SLAs)
- C. Lead Time for Changes
- D. Change Failure Rate
Answer: C
Explanation:
Lead Time for Changes is the DORA metric that best measures the efficiency and impact of platform initiatives. Option A is correct because it tracks the time from code commit to successful production deployment, directly reflecting how effectively a platform enables developers to deliver software.
Option B (MTTR) measures resilience and recovery speed, not efficiency. Option C (Change Failure Rate) measures deployment stability, while Option D (SLAs) are contractual agreements, not engineering performance metrics.
By reducing lead time, platform engineering demonstrates its ability to provide self-service, automation, and streamlined CI/CD workflows. This makes Lead Time for Changes a critical measurement of platform efficiency and developer experience improvements.
References:- CNCF Platforms Whitepaper- Accelerate (DORA Report)- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 63
Which IaC approach ensures Kubernetes infrastructure maintains its desired state automatically?
- A. Manual
- B. Imperative
- C. Declarative
- D. Hybrid
Answer: C
Explanation:
The declarative approach to Infrastructure as Code (IaC) is the foundation of Kubernetes and GitOps practices. Option A is correct because declarative IaC defines the desired state of the infrastructure (e.g., Kubernetes YAML manifests) and relies on controllers or reconciliation loops to ensure the actual state matches the declared one. This allows for automation, consistency, and drift correction without manual intervention.
Option B (imperative) requires explicit step-by-step instructions, which are not automatically enforced after execution. Option C (hybrid) can combine both methods but does not guarantee reconciliation. Option D (manual) is error-prone and eliminates the benefits of IaC entirely.
Declarative IaC reduces cognitive load, improves reproducibility, and ensures compliance through automated drift detection and reconciliation, which are essential in platform engineering for multi-cluster and multi-team environments.
References:- CNCF GitOps Principles- Kubernetes Declarative Model- Cloud Native Platform Engineering Study Guide
NEW QUESTION # 64
......
Pass Linux Foundation CNPA Exam in First Attempt Guaranteed: https://getfreedumps.passreview.com/CNPA-exam-questions.html