CCAR-P Practice Question: Stakeholder Communication and Lifecycle Management
Your organization is standardizing a Claude-based internal assistant across three departments with different risk tolerances and workflows. Executive sponsors want a single governance model that keeps the program aligned and auditable as it grows. Which TWO practices should you establish as part of the lifecycle governance? (Choose two.)
⚠ Common exam trap
The trap here is assuming governance must mean either total departmental autonomy or rigid uniformity, when the workable answer is shared standards plus risk-proportionate control.
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
✓
Maintain a central registry of approved use cases, model versions, and evaluation results that all departments reference and update as the program evolves.
Effective lifecycle governance balances consistency with flexibility. A risk-tiered change-control process ensures high-impact modifications receive review while routine iteration stays fast, and a central registry provides shared visibility into approved use cases, models, and evaluation evidence. Together they let three departments with different needs operate under one auditable model without freezing progress or forcing one-size-fits-all artifacts.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Maintain a central registry of approved use cases, model versions, and evaluation results that all departments reference and update as the program evolves.
Why this is correct
A central registry creates a single source of truth for what is deployed, which models are approved, and how quality has been demonstrated. It enables reuse of proven patterns across departments, supports audits, and gives sponsors portfolio-level visibility. It also prevents the common failure where one team unknowingly deploys an unapproved configuration that another team already evaluated and rejected.
- ✓
Define a lightweight change-control process that classifies prompt, model, and configuration changes by risk and requires review for high-impact ones.
Why this is correct
A tiered change-control process keeps iteration fast for low-risk tweaks while ensuring that changes affecting regulated outputs or safety behavior receive scrutiny. It gives auditors a traceable record and prevents silent drift in shared components. This directly supports a multi-department governance model because it scales review effort to actual risk instead of imposing uniform friction on every team.
- ✗
Freeze all prompts and model versions for twelve months so that behavior cannot change while the governance model is being validated.
Why it's wrong here
A twelve-month freeze would prevent necessary fixes for regressions, safety issues, and new requirements, creating its own risk. Governance should make change safe and traceable, not impossible. Freezing also conflicts with the reality that model endpoints evolve, so teams would be forced into unmanaged exceptions anyway, undermining the very control the freeze was meant to provide.
- ✗
Let each department maintain its own independent prompt library, evaluation approach, and release cadence with no shared standards or reporting.
Why it's wrong here
Full autonomy without shared standards defeats the purpose of a single governance model. It produces inconsistent quality, duplicated evaluation work, and no comparable evidence for sponsors or auditors. Divergent release practices also make it impossible to reason about risk across the portfolio, which is exactly what executives asked the governance program to provide.
- ✗
Require every department to use identical prompts and thresholds regardless of their differing workflows and risk tolerances.
Why it's wrong here
Forcing identical prompts and thresholds ignores the stated differences in risk tolerance and workflow, which will produce poor fit in at least one department. Shared governance means common standards, registries, and review processes, not identical artifacts. Imposing uniformity typically leads teams to work around the process, which weakens oversight rather than strengthening it.
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.