CCAR-P Exam Claude Certified Architect - Professional https://www.passquestion.com/ccar-p.html 35% OFF on All, Including CCAR-P Questions and Answers Pass CCAR-P Exam with PassQuestion CCAR-P questions and answers in the first attempt. https://www.passquestion.com/ 1. You are reviewing instrumentation in a multi-agent system. Which two findings constitute valid observability gaps in the instrumentation? Each correct answer presents a complete solution. (Select two.) A. Trace spans for each agent step are exported to the shared distributed-tracing backend. B. Latency and token usage on every span are emitted to the central metrics pipeline. C. Tool-call payloads and outcomes are recorded with redaction applied to known sensitive fields. D. Model identity and version on each turn are not recorded with the turn artifacts. E. Request-scoped correlation identifiers do not propagate across agent and tool calls. Answer: D, E Explanation: Model identity and version are essential diagnostic dimensions. Without them, operators cannot correlate a behavioral change with a model migration, reproduce the conditions of a failed turn, compare performance among model versions, or distinguish model drift from prompt, retrieval, and application defects. Therefore, the omission described in Option D is a genuine observability gap. Option E is equally significant. A multi-agent execution normally crosses orchestration, model, agent, MCP, and tool boundaries. If the request-scoped correlation identifier or distributed trace context is lost at any boundary, the resulting spans cannot reliably be reconstructed into one end-to-end transaction. Anthropic’s monitoring guidance explains that distributed tracing links a user prompt to the API requests and tool executions it initiates; it also documents propagation of W3C trace context to supported subprocesses and outbound MCP requests. Claude Code Monitoring Options A and B describe healthy telemetry coverage rather than gaps. Option C is also appropriate because recording tool interactions supports investigation, while redaction reduces the risk of exposing sensitive data in logs. Study Guide references/topics: Integration—observability challenges at scale; distributed tracing; correlation identifiers; model-version attribution; privacy-aware tool telemetry. PassQuestion CCAR-P Practice Questions 2 / 16 2. You are designing a content moderation classifier that processes high volumes of user-generated comments under a tight per-message latency budget using well-defined classification labels. Which model selection best aligns with the workload? A. Opus, because every moderation decision requires maximum reasoning depth regardless of classification complexity. B. Haiku, because its latency and cost profile align with high-volume classification workloads that require limited reasoning depth. C. Sonnet, because larger general-purpose models are preferred even when workload latency requirements are strict. D. Sonnet with extended thinking enabled, because deeper reasoning should be applied to every moderation request to improve edge-case handling. Answer: B Explanation: Haiku is the appropriate starting point because the workload is high-volume, latency-sensitive, and based on a stable closed set of moderation labels. These characteristics favor a fast, cost-efficient model capable of consistent classification without incurring the additional inference time and expense associated with deeper reasoning. Anthropic’s model-selection guidance requires architects to balance capability, speed, and cost rather than automatically selecting the most capable model. Its content-moderation guidance specifically identifies Haiku as a cost-effective option for processing moderation workloads at substantial scale. Choosing the Right Model, Content Moderation Opus is disproportionate to a routine closed-set classification problem. Sonnet may become justified if evaluation demonstrates that Haiku fails materially on complex policy distinctions, multilingual ambiguity, or adversarial edge cases, but it should not be selected merely because it is larger. Enabling extended thinking on every request would further increase latency and token consumption without evidence that the additional reasoning improves the defined success metrics. The correct architectural practice is to establish a representative moderation evaluation set, validate Haiku against accuracy and safety thresholds, and escalate only the cases that genuinely need deeper reasoning. Study Guide references/topics: Model selection; capability–latency–cost trade-offs; classification workloads; evaluation-driven routing; moderation architecture. PassQuestion CCAR-P Practice Questions 3 / 16 3. You are compiling continuity practices that span the deployment lifecycle. Which two practices belong on the list? Each correct answer presents a complete solution. (Select two.) A. Maintain a stakeholder register and notify the listed parties at every phase transition event. B. Carry the evaluation framework and reference set forward across iterations rather than rebuilding each time. C. Archive every phase deliverable in long-term storage to preserve a record of what was produced. D. Capture lessons learned at the end of each phase and surface them as inputs to the next phase. E. Lock decisions made in early phases to prevent revisiting them as later phases begin. Answer: B, D Explanation: Lifecycle continuity depends on preserving validated knowledge and feeding operational learning back into subsequent phases. Carrying the evaluation framework and reference set forward, as stated in Option B, creates a stable baseline across prompt changes, model migrations, retrieval adjustments, and architectural revisions. Rebuilding the evaluation system each time would undermine longitudinal comparison because changes in the test framework could be mistaken for changes in solution performance. Option D establishes the second essential continuity mechanism: lessons from discovery, design, implementation, deployment, and production monitoring become explicit inputs to the next phase. This closes the feedback loop and prevents recurring defects, invalid assumptions, and operational findings from being lost at organizational handoffs. Option A is overly mechanical. Stakeholders should receive communications relevant to their responsibilities and decision rights, not indiscriminate notifications at every transition. Option C confuses comprehensive archival with lifecycle continuity; retention must follow business, regulatory, security, and records-management requirements rather than an unconditional “archive everything” policy. Option E is directly contrary to iterative architecture. Decisions should be documented and governed, but material evidence or changed requirements must be allowed to reopen them. Study Guide references/topics: Lifecycle phases; evaluation continuity; reference datasets; feedback loops; lessons learned; decision records; iterative architecture governance. PassQuestion CCAR-P Practice Questions 4 / 16 4. A revenue projection assistant has missed its monthly cost target by 38 percent. Profiling shows three contributors: a 6,000-token policy preamble repeated on every call (45 percent of cost), retrieval of historical sales chunks averaging 3,000 tokens per call (30 percent), and inference on a flagship-tier model (25 percent). Stakeholders require that projection accuracy remain unchanged. Which two optimizations should you sequence first to reduce cost without affecting accuracy? Each correct answer presents part of the solution. (Select two.) A. Reduce the number of historical sales chunks retrieved across each query run. B. Truncate the policy preamble to remove non-essential clauses from the prompt. C. Enable prompt caching on the static policy preamble across the recurring calls. D. Switch the workload to a smaller, faster Claude model tier across all queries. E. Cache common retrieved sales chunks accessed across many of the daily queries. Answer: C, E Explanation: The required sequence must reduce repeated computation without changing the information or model capability used to generate projections. Prompt caching the static 6,000-token policy preamble directly addresses the largest cost contributor while preserving the complete instruction set. Anthropic states that cache reads cost substantially less than uncached input tokens, making repeated, stable prompt prefixes an ideal caching target. Prompt Caching Caching frequently reused historical-sales chunks applies the same principle to the retrieval layer. When identical, version-controlled chunks are repeatedly fetched and supplied to the model, caching their retrieval or reusable representation eliminates redundant work while maintaining the same evidence available to the projection process. The cache must use appropriate invalidation or source-version keys so updated sales data cannot be replaced by stale content. Options A and B modify the information supplied to Claude. Fewer sales chunks could remove relevant historical evidence, while truncating policy instructions could alter constraints or projection behavior. Option D introduces a model-capability change and therefore cannot guarantee unchanged accuracy without a comparative evaluation. Those interventions may be considered later, but only after representative regression testing establishes equivalence. Study Guide references/topics: Cost profiling; prompt caching; retrieval caching; cache invalidation; accuracy-preserving optimization; model and context trade-offs. PassQuestion CCAR-P Practice Questions 5 / 16 5. You are supporting an engineer whose newly added MCP server does not appear in their Claude Code session. Which diagnostic step should be tried first? A. Disable every MCP server in the configuration to isolate the issue, removing all tool access rather than confirming whether the new server is registered. B. Switch the team to a different Claude product family unrelated to the existing workflow, abandoning the current configuration rather than diagnosing the registration issue. C. Verify the MCP server is registered using the listing command, then reconnect the session if needed, since configuration changes typically require a restart to take effect. D. Reinstall the developer’s operating system from scratch, discarding all local configuration and tool state before attempting any targeted diagnostic steps. Answer: C Explanation: The first diagnostic action must establish whether Claude Code has loaded the MCP server configuration and whether it can connect to the registered endpoint. The official management command is claude mcp list; within Claude Code, /mcp can also be used to inspect server status. The listing distinguishes registered and connected servers from configurations that require authentication, approval, or connection troubleshooting. Connect Claude Code to Tools via MCP If the server was added or its configuration changed after the current session began, reconnecting or restarting the relevant Claude Code session is a proportionate next step. This ensures that configuration state and available tool definitions are refreshed before more intrusive troubleshooting begins. If the server is listed but unhealthy, the engineer can then inspect it with claude mcp get <name> and investigate transport, command path, credentials, workspace approval, or endpoint connectivity. Options A, B, and D are operationally unsound because they discard working capabilities or environments before confirming the basic registration state. Disabling all MCP servers eliminates useful diagnostic comparisons; changing product families abandons the relevant configuration; reinstalling the operating system is grossly disproportionate and risks destroying evidence needed for diagnosis. Study Guide references/topics: Claude Code environment configuration; MCP registration; server-status inspection; session refresh; targeted operational troubleshooting. PassQuestion CCAR-P Practice Questions 6 / 16 6. You are identifying signals that a deployment should re-enter design rather than continue iterating in place. Which signal most directly indicates the need for a new design cycle? A. A runbook step requires a clarification edit to improve on-call guidance accuracy, which can be handled as a documentation update without changes to component responsibilities or core contracts. B. A dashboard alert threshold needs a small numerical adjustment to reduce false-positive noise, which can be handled as an operational configuration change without a new design cycle. C. A minor copy edit is requested in a customer-facing string within the existing UI, which can be handled as a localized content change without altering component responsibilities or contracts. D. The system’s current architecture cannot meet the new requirements without changes to component responsibilities or core contracts. Answer: D Explanation: A new design cycle is warranted when the required change crosses an architectural boundary. Option D explicitly states that the existing architecture cannot satisfy the new requirements without redistributing component responsibilities or altering core contracts. Such changes may affect service ownership, orchestration, data flows, integration interfaces, security boundaries, failure handling, evaluation strategy, and operational accountability. They therefore require renewed discovery, impact analysis, design review, stakeholder approval, and regression planning. Options A, B, and C are localized maintenance activities. Clarifying a runbook improves operational documentation but does not change the deployed system’s structure. Adjusting an alert threshold is a controlled operational tuning activity, provided the change remains within established monitoring policy. Editing customer-facing copy is similarly confined to the presentation or content layer. None of these changes inherently invalidates component contracts or architectural assumptions. An architect should distinguish between iteration within an approved design and evidence that the design itself no longer supports the required outcome. Re-entering design for every minor adjustment creates unnecessary governance overhead; continuing local iteration after architectural assumptions have failed creates unmanaged technical and operational risk. Option D is the only signal that establishes a structural incompatibility. Study Guide references/topics: Lifecycle feedback loops; design re-entry criteria; architectural significance; component responsibilities; interface contracts; controlled operational iteration. PassQuestion CCAR-P Practice Questions 7 / 16 7. A security team is evaluating two proposed controls. Control A adds an outbound tool allow-list with destination restrictions and per-call review. Control B scores responses against a stable adversarial evaluation set after each model-version change. Which two risk categories are correctly matched to these controls? (Select two.) A. Control A — prompt injection from adversarial content in retrieved data B. Control A — silent quality drift after a model-version upgrade C. Control A — data exfiltration via outbound tool calls D. Control B — data exfiltration via outbound tool calls E. Control B — silent quality drift after a model-version upgrade Answer: C, E Explanation: Control A directly constrains the outbound action surface. An allow-list limits which tools and destinations may receive data, while per-call review introduces an approval boundary before information leaves the controlled environment. These measures therefore address data exfiltration through outbound tool calls, making Option C correct. Anthropic’s security guidance recommends least privilege, narrowly scoped permissions, sandboxing, and limiting access to sensitive information and actions so that a compromised agent can cause minimal damage. Mitigate Jailbreaks and Prompt Injections Control B addresses model-version drift. Running a stable adversarial evaluation set after each version change creates a consistent comparison baseline and detects regressions that might otherwise remain invisible during routine testing. This correctly maps Control B to silent quality drift, making Option E correct. Anthropic’s migration guidance repeatedly calls for workload reevaluation because instruction following, style, reasoning, and agent behavior can differ between versions. Model Migration Guide Control A may limit the consequences of successful prompt injection, but it does not prevent or directly detect adversarial instructions in retrieved content. Control B measures behavioral performance but does not impose outbound authorization controls. Each control must therefore be mapped to the risk it most directly mitigates. Study Guide references/topics: Tool governance; least privilege; exfiltration controls; adversarial evaluations; model-change regression testing; defense in depth. PassQuestion CCAR-P Practice Questions 8 / 16 8. A Claude architect at a health services organization is defining evaluation metrics for a clinical-summary pipeline. The pipeline must remain within a per-query cost ceiling and must never surface patient data to unauthorized roles. Which two metrics directly address these requirements? (Select two.) A. BLEU score computed against a human-annotated reference summary set B. Role-based access-control enforcement rate measured on a red-team dataset C. Throughput measured as successful requests processed per minute D. Per-query token cost measured against the defined cost ceiling E. Response latency at the 95th percentile across a one-week sample window Answer: B, D Explanation: The evaluation metrics must map directly to the two stated requirements. Role-based access-control enforcement rate, tested against a red-team dataset, measures whether requests from unauthorized identities, roles, or access paths are consistently denied. It converts the privacy and authorization requirement into an observable security metric and exposes bypass conditions that ordinary functional tests may miss. Because the requirement says patient data must never reach unauthorized roles, the acceptance threshold should be effectively 100% enforcement across representative and adversarial cases. Per-query token cost directly measures compliance with the financial constraint. The metric should include uncached input, cache reads and writes where applicable, output tokens, thinking tokens, and any other billable components attributed to the request. Results can then be compared with the defined ceiling across normal, boundary, and worst-case inputs. Anthropic’s evaluation guidance identifies privacy preservation and price as distinct success criteria and emphasizes that criteria must be specific, measurable, and relevant to the application. Define Success Criteria and Build Evaluations BLEU may assess textual similarity but does not test authorization or cost. Throughput and percentile latency are valuable operational metrics, yet neither directly answers the two requirements in the scenario. Study Guide references/topics: Multidimensional evaluation; privacy preservation; authorization testing; red-team datasets; token-cost measurement; requirement-to-metric traceability. PassQuestion CCAR-P Practice Questions 9 / 16 9. An architect is reviewing a set of architecture documentation packages before handing off a Claude-based pipeline to an implementation team. Which two characteristics indicate that a documentation package is sufficient to support implementation without ongoing architect involvement? (Select two.) A. The document specifies integration contracts, configuration schemas, and expected input/output shapes for each component. B. The document includes a decision log that records the rationale for key architectural choices and the alternatives rejected. C. The document provides a high-level narrative description of the business problem without component-level detail. D. The document includes the architect’s contact information for questions arising during implementation. E. The document lists all Claude models that were evaluated but does not specify which was selected or why. Answer: A, B Explanation: Implementation-ready documentation must provide both executable specifications and preserved architectural reasoning. Option A supplies the contracts an implementation team needs to build components independently: configuration schemas, accepted inputs, produced outputs, validation requirements, and integration boundaries. These details prevent teams from inventing incompatible assumptions about data structures, tool behavior, error handling, or component ownership. Option B complements the technical contracts with a decision log. Recording the selected design, underlying constraints, alternatives considered, and reasons for rejection enables implementers to distinguish deliberate architectural decisions from accidental omissions. It also prevents previously rejected approaches from being reintroduced without new evidence. A high-level business narrative in Option C may explain purpose but cannot direct component-level implementation. Contact information in Option D provides an escalation route, but documentation is not sufficient if routine progress still depends on the architect’s availability. Option E records activity rather than a decision; a model list without the selected model and selection rationale leaves critical cost, latency, capability, and evaluation assumptions unresolved. A strong handoff package should permit implementation, testing, and support teams to proceed while escalating only genuinely new architectural questions. Study Guide references/topics: Architecture documentation; interface contracts; configuration schemas; Architecture Decision Records; implementation handoff; decision traceability. PassQuestion CCAR-P Practice Questions 10 / 16 10. You are defining transparency practices for a customer-facing assistant whose responses are materially shaped by AI. Which transparency practice most directly supports responsible deployment? A. Misrepresent the AI’s role in producing responses in order to make the assistant feel more trustworthy or more human, undermining informed user consent and organizational transparency. B. Refuse to answer any user question about how the responses were produced or whether AI was involved, treating the AI’s role as confidential operational information. C. Disclose AI involvement to end users in line with the organization’s transparency policy and provide a documented path to reach a human when needed. D. Disclose AI involvement only to internal staff and operators while withholding that information from the end users whose interactions are materially shaped by the AI system. Answer: C Explanation: Responsible deployment requires users to receive an accurate representation of the system with which they are interacting. Option C provides that transparency while also establishing a practical escalation path. Disclosure should be proportionate to the material role AI plays, expressed in language appropriate to the audience, and aligned with organizational policy and applicable regulatory obligations. A documented human-contact route is important when the assistant cannot resolve an issue, produces a disputed result, encounters a high-impact exception, or handles a matter requiring human authority. Anthropic’s Responsible Scaling Policy recognizes escalation to human reviewers as an appropriate safeguard for edge cases and situations requiring human judgment. Responsible Scaling Policy Options A and D intentionally conceal material AI involvement from affected users, weakening informed decision-making, auditability, and trust. Option B is also unsuitable because transparency does not require revealing proprietary prompts, confidential controls, or internal security mechanisms; however, it does require an honest explanation of AI involvement and the system’s operational role. The correct design combines disclosure, understandable limitations, human escalation, and records demonstrating that the organization’s transparency requirements are consistently applied. Study Guide references/topics: AI transparency; informed user interaction; human escalation; responsible deployment; disclosure policy; operational accountability. PassQuestion CCAR-P Practice Questions 11 / 16 11. A Claude architect is leading the discovery phase for a new AI-powered customer service solution. Which two activities are characteristic of structured discovery and requirement gathering for a Claude-based deployment? (Select two.) A. Facilitating stakeholder workshops to surface latency, accuracy, and compliance constraints before scoping begins. B. Selecting the Claude model tier based on the architect’s prior project experience before stakeholder input is collected. C. Generating an initial prototype and iterating based on user reaction rather than written requirements. D. Documenting explicit success criteria and failure thresholds that will gate production deployment. E. Deferring constraint documentation until the integration design phase to avoid scope creep. Answer: A, D Explanation: Structured discovery begins by eliciting constraints from the people who own the business outcome, operate the process, manage risk, and will use or support the deployed system. Stakeholder workshops in Option A identify measurable expectations concerning accuracy, latency, throughput, cost, privacy, compliance, escalation, and acceptable failure behavior before the solution is scoped. Option D converts those expectations into production gates. Success criteria must be explicit enough to evaluate empirically, while failure thresholds must determine when the design requires remediation, human review, or rejection. Anthropic’s evaluation guidance states that successful LLM applications begin with defined success criteria and evaluations that measure performance against them. It characterizes strong criteria as specific, measurable, achievable, and relevant. Define Success Criteria and Build Evaluations Option B prematurely selects a model before the workload profile is known. Option C can supplement discovery, but reaction-driven prototyping cannot replace documented requirements and acceptance criteria. Option E postpones essential constraints until architectural commitments may already have been made. The discovery output should create traceability from stakeholder objectives to requirements, evaluation metrics, architecture decisions, and deployment gates. Study Guide references/topics: Structured discovery; stakeholder workshops; nonfunctional requirements; success criteria; failure thresholds; production readiness gates. PassQuestion CCAR-P Practice Questions 12 / 16 12. You are integrating Claude Code into a workflow that runs against a production database. Which guardrail design most directly preserves safety on data-modifying operations? A. Allow Claude Code to write directly to the production database without subagent scoping, read-only credential defaults, or human confirmation gates on data-modifying operations. B. Configure the database MCP server with a fully privileged credential that can perform any read or write operation, and allow all operations to proceed without explicit human confirmation. C. Disable all logging and auditing on database operations through the MCP server to reduce alert noise, removing the observability needed to detect unintended data modifications. D. Configure the database MCP server with a read-only credential by default, restrict the subagent’s tool list to read-only operations, and require explicit human confirmation on any operation that would modify data. Answer: D Explanation: Option D applies three complementary controls. First, a read-only database credential creates an authorization boundary outside the model; prompt instructions alone cannot convert that credential into write access. Second, restricting the subagent’s tool list reduces capability exposure by preventing the agent from selecting unrelated or unnecessarily privileged operations. Third, explicit human confirmation creates a deliberate approval gate before any exceptional data-changing action is executed. This is defense in depth. If Claude misinterprets a request or processes malicious instructions from untrusted content, the restricted credential and tool configuration limit the available action surface. Human review then protects operations with potentially irreversible production consequences. Logging and audit trails should remain enabled to record the actor, request, tool call, approval, affected records, and outcome. Anthropic documents that Claude Code begins with read-only permissions in Manual mode and requests approval for actions that modify the environment. Its permission system also supports granular allow, ask, and deny controls for MCP tools and subagents. Claude Code Security, Configure Permissions Options A and B eliminate least privilege and approval boundaries. Option C removes essential detection and forensic evidence. Study Guide references/topics: Production database safety; least privilege; read-only defaults; MCP permissions; subagent scoping; human confirmation; auditability. PassQuestion CCAR-P Practice Questions 13 / 16 13. A Claude architect is auditing configuration scope assignments. Which two statements correctly identify an appropriate use of user-scope configuration versus other scopes? (Select two.) A. Persisting personal editor theme preferences that follow an engineer across projects. B. Saving a preferred Claude response language that applies to all repositories the engineer uses. C. Enforcing a company-wide policy that disables a feature for all engineers. D. Defining MCP server endpoints shared by all contributors to a specific repository. E. Storing API authentication keys so they are not committed to version control. Answer: A, B Explanation: User scope applies to one engineer across every project and is therefore appropriate for portable personal preferences. Option A fits this definition because an interface theme belongs to the individual rather than to a repository or organization. Option B also fits because Claude Code provides a language setting for the preferred response language, and placing that preference in user scope makes it apply across repositories. Option C requires managed configuration because an organization-wide security control must be centrally deployed and resistant to individual override. Option D belongs in project scope because repository-specific MCP endpoints must be shared consistently with that repository’s contributors. Option E describes credential handling rather than merely a preference assignment. Credentials must not be placed in a repository, but avoiding version control alone is insufficient. They must be stored through a supported secure authentication mechanism, protected environment configuration, operating-system credential facility, or approved secrets manager—not inserted as plaintext into an ordinary settings file. Anthropic defines user scope as affecting one user across all projects, project scope as shared repository configuration, and managed scope as the location for enforceable organizational controls. It also explicitly lists themes and other personal settings as user-scope use cases. Claude Code Configuration Scopes Study Guide references/topics: User scope; project scope; managed configuration; personal preferences; repository-shared MCP configuration; credential protection. PassQuestion CCAR-P Practice Questions 14 / 16 14. You are transitioning a Claude-based deployment from design into implementation. Which handoff package most directly supports a clean transition? A. The most recent set of design presentation slides without component-level diagrams, interface contracts, an evaluation framework with a reference set, runbooks, or a known-limitations register. B. A verbal walkthrough conducted on the day of handoff with no written architecture overview, ADRs, component contracts, evaluation framework, runbooks, playbook, or known limitations. C. Architecture overview, ADRs, component contracts, evaluation framework with reference set, runbooks, on-call playbook, and known limitations. D. Source code alone with no integrating architecture overview, ADRs, component contracts, evaluation framework, runbooks, on-call playbook, or known-limitations register to support the delivery team. Answer: C Explanation: Option C provides the minimum coherent package required to move from architectural intent to implementable and supportable delivery. The architecture overview establishes system boundaries and component relationships. Architecture Decision Records preserve the context and trade-offs behind key choices. Component contracts define interfaces, schemas, responsibilities, failure behavior, and integration assumptions. The evaluation framework and reference set allow the implementation team to confirm that prompts, models, retrieval components, and tool integrations continue to meet the defined quality, safety, latency, and cost thresholds. Runbooks translate operational knowledge into repeatable procedures, while the on-call playbook defines detection, escalation, containment, and recovery actions. The known-limitations register prevents unsupported behavior from being mistaken for an implementation defect and helps stakeholders manage residual risk. Options A and B depend excessively on slides or undocumented verbal knowledge. Option D provides implementation material without explaining the system-level decisions, operating model, acceptance criteria, or limitations. Source code cannot substitute for architectural and operational documentation. A clean transition does not mean the architect can never be consulted. It means routine implementation and support do not depend on undocumented knowledge held by a single individual. Study Guide references/topics: Design-to-implementation handoff; ADRs; component contracts; reference evaluations; runbooks; operational playbooks; limitations management. PassQuestion CCAR-P Practice Questions 15 / 16 15. When communicating an architectural decision to a security and compliance reviewer, which content set is most aligned with that audience’s primary concerns? A. Feature delivery schedule, roadmap dependencies, and scope boundaries for the product manager. B. Implementation timeline, component interfaces, and deployment sequence for the engineering team. C. Threat model, control mappings, residual-risk acceptance criteria, and audit traceability. D. Decision rationale, business outcomes, and high-level risk summary for executive review. Answer: C Explanation: Security and compliance reviewers must determine whether material threats have been identified, whether required controls address those threats, how remaining exposure will be accepted, and whether the decision can be demonstrated during an audit. Option C supplies exactly that evidence. The threat model establishes protected assets, trust boundaries, adversaries, attack paths, and likely failure modes. Control mappings connect technical and procedural safeguards to organizational policies, regulatory requirements, and assurance frameworks. Residual-risk acceptance criteria define which risks may remain after mitigation, who has authority to accept them, and when further treatment is mandatory. Audit traceability connects requirements and decisions to implementation evidence, evaluations, approvals, logs, and operational monitoring. Option A is designed primarily for product management. Option B addresses engineering planning and execution. Option D is appropriate for an executive sponsor who requires business justification and a concise risk summary but normally does not perform detailed control verification. Audience adaptation should not alter the architectural decision itself. It changes the depth, terminology, evidence, and ordering used to communicate the decision. Security and compliance reviewers require verifiable control evidence rather than only schedule, implementation, or business-level summaries. Study Guide references/topics: Audience-specific communication; threat modeling; compliance control mapping; residual-risk acceptance; audit evidence; architectural decision traceability. PassQuestion CCAR-P Practice Questions 16 / 16