CCAR-P Practice Question: Developer Productivity and Operational Enablement
A platform team maintains a Claude-powered code review assistant. They want to roll out a new system prompt to production safely. The current process involves manually copying the prompt into a deployment script, which has led to drift and accidental overwrites. Which approach best enables safe, auditable prompt deployments?
⚠ Common exam trap
The trap here is assuming that any central storage (like a database or wiki) solves drift, when the real requirement is version control plus automated deployment.
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 the system prompt in a version-controlled repository and use a CI/CD pipeline that validates and deploys prompts via the Anthropic API.
Version-controlled prompts deployed through CI/CD give teams a reviewable, testable, and reversible process. Automated validation catches issues early, and the pipeline ensures every environment uses the same approved prompt. This eliminates manual copying and accidental overwrites while providing an audit trail, directly improving operational reliability and developer velocity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Store the system prompt in a version-controlled repository and use a CI/CD pipeline that validates and deploys prompts via the Anthropic API.
Why this is correct
Version control plus CI/CD provides a single source of truth, peer review, and rollback. Automated validation catches syntax or policy issues before deployment, and deployment through the API ensures consistency. This directly addresses drift and accidental overwrites by making changes traceable and repeatable, which is central to developer productivity and operational enablement.
- ✗
Embed the system prompt directly in the application code and use feature flags to toggle between versions.
Why it's wrong here
Embedding prompts in application code couples prompt changes to code releases, slowing iteration and increasing risk. Feature flags help with gradual rollout but do not provide a history of prompt content or validation. This approach still allows drift if developers edit prompts locally, and it lacks an auditable trail, so it does not solve the core problem.
- ✗
Have each developer maintain their own copy of the system prompt and share updates via a team wiki.
Why it's wrong here
Distributed copies and wiki updates are error-prone and lack enforcement. There is no guarantee that all environments use the same prompt, and manual syncs invite drift. Wikis do not integrate with deployment pipelines, so accidental overwrites remain likely. This approach increases operational overhead and undermines reliability, making it unsuitable for safe production rollouts.
- ✗
Store the system prompt in a database and update it directly in production when changes are needed.
Why it's wrong here
Direct production updates bypass review and testing, risking outages or policy violations. While a database can be a central store, without version control and CI/CD it offers no audit trail or rollback. This method also encourages ad-hoc changes, which is exactly the drift problem described. It does not provide the safety and auditability required.
About these practice questions
This CCAR-P question is part of Courseiva's 262-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.