Learn the vocabulary of self-service infrastructure provisioning through a standardized platform.
0 / 5 completed
1 / 5
At standup, a dev mentions a self-service platform that lets an application team provision a new service, database, and pipeline through one standardized interface, instead of filing a ticket with the infrastructure team for each piece. What is this platform called?
An internal developer platform, or IDP, is a self-service platform that lets an application team provision a new service, database, and pipeline through one standardized interface, rather than filing a separate ticket with the infrastructure team for each individual piece. A ticket-based process creates a bottleneck as the infrastructure team can't scale their manual provisioning work as fast as the number of requesting teams grows. An IDP shifts that provisioning work to self-service while still enforcing organizational standards underneath.
2 / 5
During a design review, the team wants a pre-built, standardized template that provisions a new service with sane defaults for logging, monitoring, and security already wired in. Which capability supports this?
A golden path template scaffolds a new service with sane, pre-wired defaults for logging, monitoring, and security already included, so a team building something new doesn't have to reconstruct those concerns independently every time. Requiring every team to configure these from scratch invites inconsistency and wastes time re-solving an already-solved problem. This golden path is what makes an internal developer platform genuinely accelerate delivery rather than just relocating the same manual work.
3 / 5
In a code review, a dev notices the platform's self-service catalog only offers a curated, pre-approved set of infrastructure building blocks rather than letting a team provision any arbitrary cloud resource directly. What does this represent?
A curated service catalog offers only a pre-approved set of infrastructure building blocks, enforcing organizational standards like cost controls and security baselines through what's available to choose from, rather than letting a team provision any arbitrary cloud resource directly. Allowing unrestricted direct provisioning reintroduces the same inconsistency and risk the platform was built to prevent. This curation is what balances self-service speed with organizational guardrails.
4 / 5
An incident report shows a team provisioned a service through the platform's self-service catalog, but the underlying golden path template hadn't been updated in over a year and still shipped a known-vulnerable default dependency. What practice would prevent this?
Treating golden path templates as actively maintained, versioned artifacts that get regularly updated and security-patched prevents a stale template from quietly shipping a known-vulnerable default into every new service built from it. Treating a template as a one-time creation ignores that its dependencies and best practices inevitably age. This ongoing template maintenance is essential, since a platform's whole value depends on its golden paths staying genuinely safe and current.
5 / 5
During a PR review, a teammate asks why the team invested in an internal developer platform instead of just letting each application team continue filing infrastructure tickets as needed. What is the reasoning?
A ticket-based process requires the infrastructure team's manual involvement in every single request, which can't scale as fast as the number of application teams and requests grows. A self-service platform lets a team provision what they need directly, through a curated, standardized catalog that still keeps organizational guardrails in place. The tradeoff is the significant upfront investment needed to actually build and maintain that platform and its golden path templates.