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

- Free Preparation Discussions

Linux Foundation CNPA Exam - Topic 3 Question 8 Discussion

Actual exam question for Linux Foundation's CNPA exam
Question #: 8
Topic #: 3
[All CNPA Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

One of the primary objectives of internal developer platforms (IDPs) is to improve developer experience by reducing cognitive load. Complex Kubernetes configurations often overwhelm developers who simply want to consume services and deploy code without worrying about infrastructure intricacies.

Option B is correct because implementing a self-service web portal (or developer portal) abstracts away Kubernetes complexities, providing developers with easy access to platform services through standardized workflows, templates, and golden paths. This aligns with platform engineering principles: empowering developers with self-service capabilities while maintaining governance, security, and compliance.

Option A increases burden unnecessarily and negatively impacts productivity. Option C limits access to services, reducing flexibility and developer autonomy, which goes against the core goal of IDPs. Option D, while helpful for education, does not remove complexity---it only shifts the responsibility back to the developer. By leveraging portals, APIs, and automation, platform teams allow developers to focus on building business value instead of managing infrastructure details.


--- CNCF Platforms Whitepaper

--- Team Topologies and Platform Engineering Practices

--- Cloud Native Platform Engineering Study Guide

Contribute your Thoughts:

0/2000 characters
Abraham
11 hours ago
I think B is the best choice. A web portal would really help.
upvoted 0 times
...
Paz
5 days ago
Honestly, a web portal (B) sounds like the best solution here.
upvoted 0 times
...
Lorenza
24 days ago
Surprised that increasing configurations (A) is even an option!
upvoted 0 times
...
Eliseo
29 days ago
Documentation (D) is great, but it won't simplify access.
upvoted 0 times
...
Novella
1 month ago
Ah, the age-old struggle of developers vs. Kubernetes. Option B is the clear winner here.
upvoted 0 times
...
Toi
1 month ago
Option B sounds like the way to go. I don't have time to become a Kubernetes expert.
upvoted 0 times
...
Nobuko
1 month ago
B) all the way. Simplify my life, please!
upvoted 0 times
...
Lucy
2 months ago
Definitely option B. Who wants to deal with Kubernetes configurations when you can just use a nice web portal?
upvoted 0 times
...
Salena
2 months ago
B) Implement a web portal that abstracts the Kubernetes complexities.
upvoted 0 times
...
Pearlie
2 months ago
Increasing configurations for security sounds counterproductive. I feel like it would just make things more complicated for the developer.
upvoted 0 times
...
Bernardine
2 months ago
I think we had a similar practice question where documentation was emphasized, but I'm not convinced that's enough on its own.
upvoted 0 times
...
Louis
2 months ago
I'm pretty confident that option B is the best solution. Simplifying access through a web portal is the most logical way to address the issue the developer is facing. The other options don't seem as directly relevant to the problem at hand.
upvoted 0 times
...
Latricia
3 months ago
Option B is definitely the way to go here. Abstracting the Kubernetes complexity through a web portal is the most user-friendly approach and will make the developer's life a lot easier. I don't think the other options really solve the core problem.
upvoted 0 times
...
Gwen
3 months ago
Hmm, this is a tricky one. I can see the appeal of the web portal in option B, but I'm also wondering if detailed documentation (option D) could be a helpful complement to that. The developer might still need to understand some of the Kubernetes concepts, even with the portal.
upvoted 0 times
...
Nilsa
3 months ago
I'm not entirely sure, but limiting user access might just complicate things further. It feels like it could lead to more confusion.
upvoted 0 times
...
Nadine
3 months ago
I disagree, limiting access (C) could cause more issues.
upvoted 0 times
...
Aleta
4 months ago
B is the way to go! A web portal would really help.
upvoted 0 times
...
Nell
4 months ago
I remember discussing how a web portal could really help abstract the complexities of Kubernetes. It seems like a practical solution.
upvoted 0 times
...
Adolph
4 months ago
I'm a bit confused by this question. Increasing configurations for security (option A) seems counterintuitive if the goal is to simplify access. And limiting user access (option C) doesn't really address the core issue. I'm leaning towards the portal solution in option B.
upvoted 0 times
...
Una
4 months ago
I think option B is the best approach here. Implementing a web portal to abstract the Kubernetes complexities seems like the most straightforward way to simplify access for the developer.
upvoted 0 times
Kimbery
3 months ago
I totally agree, option B makes it so much easier!
upvoted 0 times
...
...

Save Cancel