CCAR-P Practice Question: Developer Productivity and Operational Enablement
A platform team is building a shared Claude integration library used by 40 internal microservices. Each service currently hard-codes its own model ID, max_tokens, and retry logic. The team wants a single place to roll out model upgrades and enforce consistent retry behaviour without redeploying every service. What is the most effective architecture for this requirement?
⚠ Common exam trap
The trap here is assuming that centralizing retries through a proxy also solves configuration management, when it actually hides model changes and removes the typed contract developers need.
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 versioned internal SDK that reads model configuration from a central configuration service at startup and exposes typed client wrappers with built-in retry and backoff.
A versioned SDK reading from a central configuration service gives the platform team one lever for model IDs, token limits, and retry policy while preserving per-service autonomy. It enforces consistent behaviour through typed wrappers, supports staged rollouts, and avoids the fragility of repository-level environment files or an opaque rewriting proxy. This is the standard pattern for operational enablement at scale.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Place an HTTP proxy in front of the Anthropic API that rewrites the model field on every request and centralizes retries.
Why it's wrong here
A rewriting proxy centralizes retries but silently changes the model behind each service's back, which breaks per-service prompt tuning and cost attribution. It also adds a single point of failure and cannot enforce typed request shapes. Most critically, it does not give developers a supported SDK surface, so service code still hard-codes parameters that the proxy must guess how to patch.
- ✗
Move all Claude calls into a single shared monolith service and have the 40 microservices call it over gRPC.
Why it's wrong here
Consolidating into one service solves configuration drift but destroys the autonomy the microservices were built for, creating a bottleneck for every team and a blast radius for every change. It also requires a large migration and adds network hops that increase latency. The requirement can be met with far less disruption through a shared library plus centralized configuration rather than a new monolith.
- ✓
Publish a versioned internal SDK that reads model configuration from a central configuration service at startup and exposes typed client wrappers with built-in retry and backoff.
Why this is correct
A versioned SDK backed by a central configuration service lets the platform team change model IDs, token limits, and retry policy for all 40 services without touching each codebase. Typed wrappers enforce consistent behaviour and can be regression-tested once. Because configuration is fetched at startup, upgrades roll out on the next service restart, balancing safety and speed.
- ✗
Add a shared environment variable file to each repository and require every service owner to pull the latest values before each deployment.
Why it's wrong here
Environment files still live inside each repository, so the platform team has no single control point. Service owners can forget to pull updates, and drift between repositories is inevitable. This approach also offers no typed wrappers or built-in retry logic, so each service must reimplement behaviour. It fails the requirement to roll out model upgrades without redeploying every service.
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 →
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.