CCAR-P - Stakeholder Communication & Lifecycle Management (14% of the exam) - Section 6.1

Conduct structured discovery and requirement gathering.

Running discovery before design: identifying stakeholders, current processes, data sources, constraints and success criteria. Candidates should recognise the requirement that has not been gathered yet and the risk of designing before it is known.

stakeholder identificationcurrent-state processconstraints and success criteriadata availability

Practice question for this objective

Free sampleStakeholder Communication & Lifecycle Managementmedium

An Irish hospital group wants Claude to turn discharge notes into summary letters for family doctors. Discovery has captured the stakeholders, the current process (a junior doctor spends about 25 minutes per letter) and a success criterion of a reviewed letter within an hour of discharge. The architect must now choose between calling a provider-hosted model endpoint and deploying through the group's existing cloud tenancy, and the information governance team has not yet been consulted. Which question must discovery answer before that choice is made?

  • AWhether patient-identifiable notes may be processed outside the group's own boundary, and under which data processing agreement. Correct
  • BHow many discharge letters each ward produces on a typical day, so the team can size throughput for the hosted endpoint.
  • CWhich layout and tone family doctors prefer in a discharge letter, so the prompt template can match the group's house format.
  • DWhether clinicians would accept a confidence score shown on each letter, so low-scoring letters can be routed for closer review.
Data residency and processing-agreement constraints for sensitive data must be gathered in discovery before choosing a deployment path, because they decide which paths are permitted. The two candidate designs differ mainly in where patient data travels and who processes it. Throughput, letter format and review routing can all be handled on either path, so they do not decide between them. Whether identifiable health data may leave the group's authorised boundary, and whether the required processing agreement is in place before any data is sent, determines which path is allowed at all.

Why A is correct: Correct. Where patient-identifiable data may be processed, and under what agreement, is a compliance constraint that rules deployment paths in or out. Until information governance answers it, choosing between a provider-hosted endpoint and the group's own tenancy is designing before a binding requirement is known.

Why B is wrong: This is tempting because volume is a standard discovery item and affects capacity planning. It is wrong because either deployment path can be sized for a hospital's daily discharge volume, so the answer does not separate the two options; it assumes the hosted path is already permitted.

Why C is wrong: This is tempting because the doctors receiving the letters are key stakeholders and their acceptance drives adoption. It is wrong because letter format is settled in the prompt and evaluation work on either path; it has no bearing on where patient data may be processed.

Why D is wrong: This is tempting because it looks like a sensible way to target clinical review. It is wrong because it does not bear on the deployment decision, and a model's self-reported confidence is not a reliable accuracy signal to route clinical review on.

See more CCAR-P practice questions, answers explained.

Exam traps in Stakeholder Communication & Lifecycle Management

Answers that look right on this material and are not. Each one is a distractor from a different question in the CCAR-P bank for this domain.

  • Build a working multi-agent prototype in the first fortnight so stakeholders can react to real drafts before any requirements are agreed

    Why it is wrong: Tempting because early demos build stakeholder engagement. It is wrong because it jumps into design and build before discovery has established a baseline or a success criterion, and a multi-agent design is over-engineered for drafting a reply; without agreed measures the demo cannot support a go or no-go decision.

  • Fine-tune a model on the 600 labelled decisions now, and retrain it each quarter when the policy manual is revised.

    Why it is wrong: This is tempting because it matches the sponsor's request and a quarterly retrain appears to handle policy change. It is wrong because 600 examples labelled by teams that agree only 71 per cent of the time would teach the model their inconsistency, and fine-tuning is being chosen before prompt and retrieval work has been tried.

  • The sign-off review missed the vendor, so the privacy team's assessment of the design was incomplete from the start

    Why it is wrong: This is tempting because the privacy assessment did turn out to be incomplete. It is wrong because the vendor was added five months after sign-off, so the reviewers assessed an accurate picture of the system as it then stood; the gap opened later.

Examworthy is not affiliated with or endorsed by Anthropic. Original, blueprint-aligned practice material only.