CCAR-P Practice Question: Developer Productivity and Operational Enablement
Your team wants to adopt a 'Configuration-as-Code' approach for LLM prompts. Which tool is most suited for managing this?
⚠ Common exam trap
Test-takers frequently select ad-hoc prompt management tools or local shared drives, ignoring that Git-based repositories integrated with CI/CD pipelines are required for true Configuration-as-Code workflows.
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
✓
A Git-based repository integrated with a CI/CD pipeline.
Version control systems (like Git) combined with modern CI/CD pipelines are the best tools for Configuration-as-Code. By treating prompts as code, teams gain the benefits of peer reviews, version history, and automated testing, which are essential for LLM operational enablement. This approach ensures that changes to model behavior are transparent, reproducible, and easily reversible, significantly reducing the risk of production incidents and improving team collaboration on prompt engineering tasks.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A shared Excel spreadsheet on a local company server.
Why it's wrong here
Excel spreadsheets are not suitable for version control or collaborative engineering. They lack audit trails, branching, and automated validation, which are all critical requirements for production-grade software management. Using Excel for prompt management is an anti-pattern that creates significant operational risk and hampers effective developer collaboration.
- ✓
A Git-based repository integrated with a CI/CD pipeline.
Why this is correct
Git provides the standard for versioning, peer-reviewed changes, and auditability. Integrating this into a CI/CD pipeline allows for automated testing of prompts against golden datasets before they are deployed. This is the professional, industry-standard approach for managing LLM configuration in a scalable and robust way.
- ✗
Directly updating the prompts in the model provider's web console.
Why it's wrong here
Updating prompts in a web console lacks the necessary governance, versioning, and code review processes. It creates a 'manual' workflow that is prone to error and makes it nearly impossible to track historical changes or perform automated testing. This is the opposite of a structured configuration-as-code pattern.
- ✗
Hardcoding the prompts in a static configuration file inside the app binary.
Why it's wrong here
Hardcoding prompts in the binary requires a full re-compilation and re-deployment for any change. This is slow, inefficient, and prevents quick experimentation. Configuration-as-code patterns should aim to decouple prompt management from the core application build, allowing for faster and more flexible model iteration.
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.