CCAR-P Practice Question: Developer Productivity and Operational Enablement
Which TWO metrics are most useful for evaluating developer productivity in an LLM-driven organization? (Choose TWO)
⚠ Common exam trap
Test-takers frequently select traditional software agile metrics like lines of code or commit frequency, which do not accurately reflect LLM engineering productivity.
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
✓
Mean time to deploy a prompt improvement to production.
Measuring productivity in LLM development requires balancing speed of iteration with the quality of the output. Metrics like mean time to deploy prompt changes and the success rate of automated evaluations provide a clear picture of how quickly and effectively a team can work. These indicators help identify bottlenecks in the CI/CD pipeline and ensure that improvements are actually enhancing the system's overall performance rather than just adding complexity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Mean time to deploy a prompt improvement to production.
Why this is correct
Reducing the time between identifying a prompt improvement and deploying it is a key metric for developer velocity. It reflects the efficiency of the CI/CD pipeline and the quality of the surrounding tooling, directly impacting how fast a team can iterate on their LLM features and respond to feedback.
- ✗
Total number of prompts written by a developer each week.
Why it's wrong here
Counting the number of prompts is a vanity metric that ignores quality and impact. A developer could write dozens of ineffective prompts that require continuous rework. Productivity should be measured by the successful deployment of high-performing, reliable prompts that add business value, not by the raw volume of work.
- ✓
Success rate of automated evaluation suites in CI/CD.
Why this is correct
A high success rate in automated evaluation suites indicates that the development process is robust and that new changes are well-vetted. It minimizes the need for manual troubleshooting and increases developer confidence. Tracking this metric helps teams understand how effectively they are preventing regressions and maintaining high quality throughout.
- ✗
Total API usage cost per day for the entire organization.
Why it's wrong here
While important for budgeting, total cost is not a direct measure of developer productivity. It is a business metric influenced by traffic and product adoption. Productivity metrics must focus on the efficiency of the engineering team's output and processes, rather than the scale of the product's consumption in production.
- ✗
Number of lines of code written in the application backend.
Why it's wrong here
Lines of code is a poor measure of productivity, especially in LLM-heavy applications where the logic is often contained within prompts rather than code. This metric encourages bloat and fails to capture the core work of prompt engineering, making it irrelevant for assessing the productivity of an AI-focused engineering team.
About these practice questions
One of 262 original CCAR-P practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.