CCAR-P Practice Question: Developer Productivity and Operational Enablement
A platform team maintains a shared Claude API integration used by multiple product squads. Squads frequently push prompt changes that break downstream features, and nobody can tell which prompt version produced a given output in production. The team wants every API call to be traceable to an exact prompt revision and wants to gate prompt changes behind review. Which approach best satisfies both requirements?
⚠ Common exam trap
The trap here is assuming that timestamps or deployment logs are sufficient to identify which prompt version produced a specific output, when only an immutable revision identifier tied to the prompt content itself can do that reliably.
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
✓
Store prompts in a Git repository, reference each revision by commit SHA when calling the Messages API, and require pull-request review before merging prompt changes.
Prompts are code and should be treated as such. Git provides immutable commit SHAs that can be logged with each Messages API call, giving exact traceability from a production output back to the prompt revision that generated it. Pull-request review adds a human gate so breaking changes are caught before they reach the shared integration, satisfying the change-control requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable extended thinking on every request and rely on the model's reasoning output to reconstruct which prompt was used.
Why it's wrong here
Extended thinking exposes internal reasoning tokens, not the prompt revision that produced them. It also increases latency and cost on every call and provides no immutable identifier for the prompt. This does not create traceability to a specific prompt version and adds no review process, so it misses both goals.
- ✓
Store prompts in a Git repository, reference each revision by commit SHA when calling the Messages API, and require pull-request review before merging prompt changes.
Why this is correct
Versioning prompts in Git gives every revision an immutable commit SHA that can be logged alongside each API call, making production outputs traceable to an exact prompt state. Requiring pull-request review enforces a gate before changes reach the shared integration. This combination directly addresses both the traceability and the change-control requirements without adding runtime infrastructure.
- ✗
Add a timestamp field to every API request and correlate logs with the deployment time of the calling service.
Why it's wrong here
Timestamps correlate an output with a deployment window, but they cannot identify which prompt revision was active if multiple prompt edits ship between deployments or if prompts are edited outside the deploy pipeline. This approach provides approximate correlation at best and gives no review gate, so it fails the traceability requirement.
- ✗
Have each squad maintain its own prompt copy in a shared wiki page and record the editor's name in the page history.
Why it's wrong here
A wiki records who edited a page but offers no immutable revision identifier that can be attached to an API call, and edits are not gated by review. Prompt copies drift across squads, so the same logical prompt can diverge silently. This fails the traceability requirement and provides weak change control.
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.