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 13 Discussion

In a scenario where an Internal Developer Platform (IDP) is being used to enable developers to self-service provision products and capabilities such as Namespace-as-a-Service, which answer best describes who is responsible for resolving application-related incidents?
C) Platform teams are responsible for investigating and resolving underlying infrastructure problems whilst application teams are responsible for investigating and resolving application-related problems.
A) A separate team is created which includes people previously from the platform and application teams to solve all problems for the organization.
B) Platform teams delegate appropriate permissions to the application teams to allow them to self-manage and resolve any underlying infrastructure and application-related problems.
D) Platform teams are responsible for investigating and resolving all problems related to the platform, including application ones, before the app teams notice.

Linux Foundation CNPA Exam - Topic 3 Question 13 Discussion

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

In a scenario where an Internal Developer Platform (IDP) is being used to enable developers to self-service provision products and capabilities such as Namespace-as-a-Service, which answer best describes who is responsible for resolving application-related incidents?

Show Suggested Answer Hide Answer
Suggested Answer: C

Platform engineering clearly separates responsibilities between platform teams and application teams. Option C is correct because platform teams manage the platform and infrastructure layer, ensuring stability, compliance, and availability, while application teams own their applications, including troubleshooting application-specific issues.

Option A (creating a single merged team) introduces inefficiency and removes specialization. Option B incorrectly suggests application teams should also solve infrastructure issues, which conflicts with platform-as-a-product principles. Option D places all responsibilities on platform teams, which creates bottlenecks and undermines application team ownership.

By splitting responsibilities, IDPs empower developers with self-service provisioning while maintaining clear boundaries. This ensures both agility and accountability: platform teams focus on enabling and securing the platform, while application teams take ownership of their code and services.


--- CNCF Platforms Whitepaper

--- Team Topologies (Platform as a Product Model)

--- Cloud Native Platform Engineering Study Guide

Contribute your Thoughts:

0/2000 characters
Iluminada
11 days ago
I like A for collaboration, but it might complicate things.
upvoted 0 times
...
Rosalyn
17 days ago
D seems too centralized. It could slow down response times.
upvoted 0 times
...
Elroy
22 days ago
I feel C is safer. Platform teams should focus on infrastructure.
upvoted 0 times
...
Dan
27 days ago
Option C is more realistic. Clear roles help avoid confusion.
upvoted 0 times
...
Dudley
1 month ago
I agree, B is good. They need to manage their own issues.
upvoted 0 times
...
Gabriele
1 month ago
I think option B makes the most sense. Empowering app teams is key.
upvoted 0 times
...
My
1 month ago
B is the way to go! Let the teams manage their own incidents.
upvoted 0 times
...
Augustine
2 months ago
C is my pick. It separates concerns effectively.
upvoted 0 times
...
Cristy
2 months ago
I like A. Collaboration is important for problem-solving.
upvoted 0 times
...
Adell
2 months ago
Option D feels too centralized. App teams should handle their own issues.
upvoted 0 times
...
Carlee
2 months ago
I agree, but option C seems more balanced. Clear responsibilities!
upvoted 0 times
...
Justine
2 months ago
I think option B makes the most sense. Empowering app teams is key.
upvoted 0 times
...
Alesia
2 months ago
Wait, can app teams really manage their own incidents? Sounds risky!
upvoted 0 times
...
Salley
3 months ago
D seems unrealistic, how can platform teams catch everything?
upvoted 0 times
...
Tamekia
3 months ago
A sounds like overkill, why create a whole new team?
upvoted 0 times
...
Johnson
4 months ago
C is the way to go. App teams should handle their own issues.
upvoted 0 times
...
Laurel
5 months ago
I think B makes the most sense for self-service.
upvoted 0 times
...
Anabel
5 months ago
Option D seems too centralized; I feel like it could lead to bottlenecks if platform teams handle everything.
upvoted 0 times
...
Edda
5 months ago
I'm leaning towards option C as well, but I wonder if there are scenarios where platform teams might need to step in more often.
upvoted 0 times
...
Kenda
5 months ago
I remember practicing a question similar to this, and I think option B makes sense since it emphasizes self-management for app teams.
upvoted 0 times
...
Dan
6 months ago
I think option C sounds familiar, but I'm not entirely sure if application teams really have the authority to resolve their own issues.
upvoted 0 times
...

Save Cancel