CCAR-P Practice Question: Developer Productivity and Operational Enablement
A new engineer joins a team building a Claude-powered support triage tool. She wants to iterate quickly on prompt wording without redeploying the service, but the team also needs every prompt change to be auditable and reversible. Which practice best supports both goals?
⚠ Common exam trap
The trap here is equating fast iteration with ungoverned editing, when the real need is speed plus a versioned, reversible record of every change.
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 an external configuration store with version history, and have the application load the active prompt version at runtime with a rollback control.
Externalizing prompts into a versioned configuration store decouples prompt iteration from code deployment while preserving an auditable history and a fast rollback path. The engineer can experiment and promote versions without a build pipeline, and the team can always trace or revert a change, which satisfies both stated goals.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Keep prompts in a shared document that the engineer edits freely, and copy the current text into the service configuration manually before each release.
Why it's wrong here
A shared document lacks version control semantics tied to the running service, and manual copying invites transcription errors and drift between the document and production. Iteration may feel fast, but auditability and rollback are effectively absent because there is no reliable link between a document revision and a deployed behavior.
- ✗
Hard-code the prompt as a string literal in the application source and require a full deployment for every wording change.
Why it's wrong here
Hard-coding makes iteration slow because every wording tweak requires a build and deploy cycle. It does provide auditability through version control, but it fails the primary goal of rapid iteration, and rolling back a bad prompt means reverting and redeploying the entire service, which is unnecessarily heavy for a text change.
- ✗
Allow the engineer to edit prompts directly in the production database with a direct SQL client, keeping no history of prior versions.
Why it's wrong here
Direct database edits enable fast changes but provide no audit trail or rollback path, so a bad prompt cannot be reverted and there is no record of who changed what. This fails the auditability and reversibility requirements and introduces risk of accidental corruption in the production data store.
- ✓
Store prompts in an external configuration store with version history, and have the application load the active prompt version at runtime with a rollback control.
Why this is correct
An external versioned configuration store lets the engineer edit prompts and activate a new version without redeploying, while the version history provides a full audit trail. A rollback control restores a prior version instantly, satisfying both rapid iteration and reversibility for the triage tool.
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.