Courseiva

CCAR-P Practice Question: Developer Productivity and Operational Enablement

A platform team is standardizing how internal teams integrate Claude. Leadership wants faster onboarding, fewer production incidents, and clear accountability for cost. Which TWO practices best support these goals? (Choose two.)

⚠ Common exam trap

The trap here is treating a single shared API key as a billing simplification, when it actually removes the per-team attribution that cost accountability depends on.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Publish a golden-path reference implementation with sample prompts, error handling, and a checklist for going to production.

A golden-path reference implementation accelerates onboarding and reduces incidents by giving teams proven patterns, while per-service tagging with a shared usage dashboard makes cost attributable and accountable. Freezing model versions, allowing full tooling autonomy, and centralizing one shared key each work against at least one of the stated goals, so they are not the right practices here.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Publish a golden-path reference implementation with sample prompts, error handling, and a checklist for going to production.

    Why this is correct

    A golden-path reference gives new teams a working starting point with proven error handling and prompt patterns, which speeds onboarding and reduces incidents caused by common mistakes. The checklist makes production readiness explicit. It also spreads a consistent approach without forcing a heavy migration. This directly supports faster onboarding and fewer incidents.

  • ✗

    Route all Claude traffic through a single shared API key managed by the platform team to simplify billing.

    Why it's wrong here

    A single shared key simplifies billing but destroys per-team cost attribution, which is the opposite of the accountability goal. It also creates a high-value credential that is hard to rotate and a single point of failure. Incident blast radius grows because one team's runaway usage affects everyone. This practice undermines clear cost accountability.

  • ✓

    Require every team to tag requests with a service identifier and workspace, and surface per-team token usage in a shared dashboard.

    Why this is correct

    Tagging requests with a service identifier and workspace makes token usage attributable, which is the foundation of cost accountability. A shared dashboard lets teams see their own consumption and compare against peers. Without attribution, cost discussions become guesswork. This practice directly supports clear accountability for cost across many teams.

  • ✗

    Let each team choose its own SDK, logging format, and retry strategy to maximize autonomy.

    Why it's wrong here

    Full autonomy recreates the fragmentation the platform team is trying to eliminate. Divergent SDKs, logs, and retry strategies make incidents harder to diagnose and prevent shared tooling from working. Onboarding slows because there is no common path. Autonomy is valuable, but unconstrained variation conflicts with the goals of faster onboarding and fewer incidents.

  • ✗

    Mandate that all teams use the same model version and freeze upgrades for a year to reduce variability.

    Why it's wrong here

    A year-long freeze reduces short-term variability but blocks access to improved models and security fixes, and it does not address onboarding speed or cost accountability. It also forces teams with different latency and quality needs into one tradeoff. Eventually the freeze creates a risky big-bang upgrade. This practice does not support the stated goals.

About these practice questions

Courseiva writes every CCAR-P question from scratch — 262 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Anthropic exam blueprint

This CCAR-P practice question is part of Courseiva's free Anthropic certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCAR-P exam.