CCAR-P Practice Question: Stakeholder Communication and Lifecycle Management

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Promise 100% accuracy for all complex logic tasks to secure stakeholder buy-in.

  Why it's wrong here

  Promising perfect accuracy for LLMs is fundamentally dishonest and creates a major liability for the project. Architects must manage expectations regarding probabilistic outcomes and potential hallucinations, ensuring that stakeholders understand the need for human-in-the-loop validation or robust system design to handle errors in critical business workflows.

• ✓

  Define specific, measurable KPIs related to task completion time and accuracy rates.

  Why this is correct

  Defining clear KPIs provides a shared language for project success. This objective measurement allows stakeholders to evaluate the system's performance against concrete business goals, preventing the project from drifting into undefined territory where success is subjective and difficult to prove, thereby improving project governance and communication.

• ✓

  Schedule a weekly demo that showcases edge cases to highlight system limitations.

  Why this is correct

  Transparency regarding limitations is crucial for building long-term trust. By proactively showcasing where the model struggles, you ensure stakeholders understand the boundaries of the technology, which helps in designing appropriate user interfaces and fallback mechanisms, ultimately leading to a more robust and realistic production integration strategy.

• ✗

  Exclude non-technical stakeholders from the evaluation process to maintain focus.

  Why it's wrong here

  Excluding stakeholders results in a system that may meet technical requirements but fails to serve business needs. Inclusion is essential for identifying domain-specific nuances that engineers might overlook, and keeping stakeholders engaged throughout the evaluation ensures that the delivered solution remains aligned with shifting business goals and expectations.

• ✗

  Automate all stakeholder status reports to avoid any human interaction.

  Why it's wrong here

  Automated reports lack the necessary nuance for interpreting project health and risks. While automation is useful for data delivery, human interaction is required to contextualize findings, manage project expectations, and navigate the interpersonal dynamics of stakeholder relationships that are essential for long-term project success and continued institutional support.