CNPA Exam Dumps : Certified Cloud Native Platform Engineering Associate

The most efficient and scalable strategy is to use a declarative approach with Infrastructure as Code (IaC). Option B is correct because declarative definitions specify the desired state (e.g., resource requests, limits, autoscaling policies) in code, allowing Kubernetes controllers and autoscalers to reconcile and enforce them dynamically. This ensures that applications can scale efficiently based on actual demand.

Option A (fixed allocation) is inefficient, leading to wasted resources during low usage or insufficient capacity during high demand. Option C (manual provisioning) introduces delays, risk of error, and operational overhead. Option D (imperative scripting) is not sustainable for large-scale or dynamic workloads, as it requires constant manual intervention.

Declarative IaC aligns with GitOps workflows, enabling automated, version-controlled scaling decisions. Combined with Kubernetes’ Horizontal Pod Autoscaler (HPA) and Cluster Autoscaler, this approach allows platforms to balance cost efficiency with application reliability.

In GitOps workflows, the source of truth for environments is stored in Git. Promotion from staging to production is managed by merging changes into the production branch or repository. Option A is correct because once changes are merged, the GitOps operator (e.g., Argo CD, Flux) automatically detects the updated desired state in Git and reconciles it with the production environment.

Option B (creating new environments each time) is inefficient and unnecessary. Option C (manual updates) violates GitOps principles of automation and auditability. Option D (direct deployments) reverts to a push-based CI/CD model rather than GitOps’ pull-based reconciliation.

By relying on Git as the single source of truth, GitOps ensures version control, auditability, and rollback capabilities. This allows consistent, reproducible promotion between environments while reducing human error.

Agile and DevOps share the principle of continuous improvement through rapid feedback and iteration. Option B is correct because gathering feedback continuously and iterating aligns directly with DevOps practices such as CI/CD, observability-driven development, and platform engineering’s focus on developer experience. This ensures platforms and applications evolve quickly in response to real-world conditions.

Option A contradicts Agile, which emphasizes active customer collaboration. Option C reflects rigid waterfall methodologies, not Agile or DevOps. Option D enforces silos, which is the opposite of DevOps principles of cross-functional collaboration.

By embracing continuous feedback loops, both Agile and platform engineering accelerate delivery, improve resilience, and ensure that platforms deliver real value to developers and end users. This cultural alignment ensures both speed and quality in cloud native environments.