CCAR-P Practice Question: Developer Productivity and Operational Enablement
A team is rolling out an internal Claude-powered assistant for their engineering organization. Adoption is low and developers report that they do not trust the answers for anything beyond trivial questions. The enablement lead wants to increase adoption by making the assistant's behavior more transparent and debuggable. Which change best supports that goal?
⚠ Common exam trap
The trap here is treating low adoption as a model quality problem and reaching for temperature or scope changes, when the actual blocker is that developers cannot see how answers are produced.
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
✓
Expose the system prompt, the tools available, and the retrieved context used for each answer, and log request IDs for support.
Trust grows when developers can see the inputs that shaped an answer. Exposing the system prompt, available tools, and retrieved context lets engineers verify whether the assistant had the right information and instructions. Logging request IDs enables targeted investigation of bad answers, turning vague distrust into specific, fixable issues that the enablement team can address.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Restrict the assistant to answering only questions about internal documentation and disable all other capabilities.
Why it's wrong here
Narrowing scope may reduce some bad answers, but it does not make the assistant's behavior transparent or debuggable. Developers still cannot see why a documentation answer was produced. This limits usefulness without addressing the underlying trust problem, so it is unlikely to raise adoption meaningfully.
- ✗
Hide the system prompt and tool definitions from users to keep the interface simple.
Why it's wrong here
Hiding the system prompt and tool definitions makes the assistant a black box, which is the opposite of transparency. Developers cannot reason about why an answer was produced or whether the assistant had access to the right context. This would likely deepen distrust rather than improve adoption.
- ✓
Expose the system prompt, the tools available, and the retrieved context used for each answer, and log request IDs for support.
Why this is correct
Showing the instructions, tools, and retrieved context lets developers verify why an answer was produced and whether the assistant had the right information. Request IDs make it possible to investigate specific bad answers with support. This transparency directly addresses the trust gap that is suppressing adoption across the engineering organization.
- ✗
Increase the model's temperature so answers vary more and feel more natural to developers.
Why it's wrong here
Higher temperature increases variability, which makes answers harder to reproduce and therefore harder to trust. Developers evaluating technical guidance need consistent, verifiable outputs. This change would make debugging more difficult and would likely reduce confidence rather than increase it.
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.