Golden Paths
Also: Paved roads · Paved paths · Opinionated defaults
Opinionated, well-supported default workflows that make the safe, productive way the easy way for developers.
Why CCAR-P tests this
Developer enablement is about reducing friction on the correct path, so the exam checks whether you steer teams onto supported defaults instead of leaving every choice open.
A golden path (or paved road) is a pre-built, opinionated workflow that a platform team offers so most developers can accomplish a task the right way without assembling it from scratch. In an AI-enablement context, that might be a templated agent scaffold, a standard CLAUDE.md, a vetted set of Skills, a sanctioned CI integration, and default guardrails — all wired together so the recommended way is also the lowest-friction way.
The philosophy is enablement over enforcement: rather than blocking every non-standard choice, you make the supported path so convenient and well-documented that teams choose it voluntarily, while leaving an escape hatch for genuine edge cases. This concentrates support, security review, and cost controls onto a small number of blessed workflows instead of an unbounded sprawl of one-off setups.
Golden paths pay off operationally: fewer configurations to secure, a single place to push a fix or a new guardrail, and faster onboarding because new developers inherit least-privilege defaults, sandboxing, and verification steps for free. The trap is confusing a golden path with a hard mandate — a paved road guides by making the right thing easy, it does not wall off every alternative.
Exam trap
A golden path is a well-supported default that makes the safe choice easy, not a hard-coded restriction that forbids every alternative — answers framing it as mandatory lockdown miss the enablement intent.
Commonly confused with
Related concepts
Independent, unofficial study material from Claude Cert Prep. Not affiliated with Anthropic.