Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

Linux Foundation CNPA Exam - Topic 4 Question 5 Discussion

Actual exam question for Linux Foundation's CNPA exam

Question #: 5
Topic #: 4

[All CNPA Questions]

Which approach is effective for scalable Kubernetes infrastructure provisioning?

AHelm charts with the environment values.yaml

BImperative scripts using Kubernetes API

CStatic YAML with kubectl apply

DCrossplane compositions defining custom CRDs

Show Suggested Answer

Suggested Answer: D

The most effective approach for scalable Kubernetes infrastructure provisioning is Crossplane compositions. Option D is correct because compositions let platform teams define custom CRDs (Composite Resources) that abstract infrastructure details while embedding organizational policies and guardrails. Developers then consume these abstractions through simple Kubernetes-native APIs, enabling self-service at scale.

Option A (Helm with values.yaml) is useful for application deployment but not for scalable infrastructure provisioning across multiple clouds. Option B (imperative scripts) lacks scalability, repeatability, and governance. Option C (static YAML with kubectl apply) is manual and not suited for dynamic, multi-team environments.

Crossplane compositions allow platform teams to curate golden paths while giving developers autonomy. This reduces complexity, ensures compliance, and supports multi-cloud provisioning---all key aspects of platform engineering.

--- CNCF Crossplane Project Documentation

--- CNCF Platforms Whitepaper

--- Cloud Native Platform Engineering Study Guide

by Laurene at Oct 04, 2025, 01:33 PM

Limited Time Offer

25%

Off

Get Premium CNPA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Carman

7 months ago

D allows for better integration with existing systems.

upvoted 0 times

...

Keneth

7 months ago

C is too static for large-scale setups.

upvoted 0 times

...

Adelaide

7 months ago

B can be useful, but it's not as scalable as A or D.

upvoted 0 times

...

Moon

8 months ago

A is effective for managing different environments easily.

upvoted 0 times

...

Albert

8 months ago

I prefer D. Crossplane is great for custom resources.

upvoted 0 times

...

Nina

8 months ago

Wait, can Crossplane really handle that much complexity?

upvoted 0 times

...

Madonna

8 months ago

C) Static YAML? Really? Seems outdated.

upvoted 0 times

...

Charlie

8 months ago

I have a feeling that imperative scripts could be useful, but they seem less maintainable compared to the other options.

upvoted 0 times

...

Wilda

8 months ago

Crossplane compositions sound familiar, but I can't recall if they were specifically for scalable provisioning or just for managing resources.

upvoted 0 times

...

Selma

9 months ago

I remember practicing with static YAML files and kubectl apply, but I feel like that might not be the best for scalability.

upvoted 0 times

...

Carylon

9 months ago

I think Helm charts might be the way to go since they allow for templating and managing configurations easily, but I'm not entirely sure.

upvoted 0 times

...

Wilda

9 months ago

I think A is the best choice. Helm charts are so flexible!

upvoted 0 times

...

Wilford

9 months ago

I think B) is too messy for scaling.

upvoted 0 times

...

Clay

9 months ago

A) Helm charts are super handy for managing configs!

upvoted 0 times

...

Eleni

10 months ago

D) Crossplane is the future, no doubt!

upvoted 0 times

...

Marleen

10 months ago

Helm charts and Crossplane, the dynamic duo of Kubernetes infrastructure provisioning!

upvoted 0 times

...

Destiny

10 months ago

C) Static YAML with kubectl apply? What is this, the stone age?

upvoted 0 times

...

Hershel

10 months ago

B) Imperative scripts using Kubernetes API? That's so 2019, let's move with the times!

upvoted 0 times

...

Cristal

11 months ago

D) Crossplane compositions defining custom CRDs sounds like the future of Kubernetes infrastructure provisioning.

upvoted 0 times

...

Therese

11 months ago

A) Helm charts with the environment values.yaml is the way to go! Scalable and maintainable.

upvoted 0 times

...

Julianna

11 months ago

Imperative scripts using the Kubernetes API could be powerful, but they might be harder to maintain long-term. I'd have to weigh the pros and cons carefully.

upvoted 0 times

...

Shalon

11 months ago

Static YAML with kubectl apply seems like the most straightforward approach. It's simple and reliable, but maybe not as scalable as the other choices.

upvoted 0 times

...

Allene

11 months ago

Hmm, I'm not sure. Crossplane looks interesting, but I'm not super familiar with it. I might need to read up on that option a bit more.

upvoted 0 times

...

Osvaldo

11 months ago

I think I'd go with Helm charts for this one. The values.yaml file makes it easy to manage environment-specific config.

upvoted 0 times

Cecilia

6 months ago

I've had success with Crossplane too, but Helm is solid.

upvoted 0 times

...

Barrett

6 months ago

Definitely, the values.yaml simplifies things.

upvoted 0 times

...

Celestina

7 months ago

I agree, Helm charts are super flexible!

upvoted 0 times

...

Margot

10 months ago

Helm charts really streamline the process for different environments.

upvoted 0 times

...

...