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?
Answer(s): C
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 PolicyOptions 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.
MULTIPLE CHOICEA 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.)
Answer(s): A,D
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 EvaluationsOption 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.
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?
Answer(s): D
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 PermissionsOptions 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.
MULTIPLE CHOICEA Claude architect is auditing configuration scope assignments.Which two statements correctly identify an appropriate use of user-scope configuration versus other scopes? (Select two.)
Answer(s): A,B
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 ScopesStudy Guide references/topics: User scope; project scope; managed configuration; personal preferences; repository-shared MCP configuration; credential protection.
A financial services client is using Claude to generate personalized investment recommendations for high-net-worth clients. The system combines market data, client portfolio history, regulatory compliance data, and risk profiles into context windows. However, stakeholders are concerned about recommendation quality variance and liability if recommendations don't align with the client's actual financial situation.What is the most important evaluation metric and validation strategy for this use case?
Answer(s): B
The human-in-the-loop evaluation framework is critical for high-stakes financial recommendations because the domain requires expert judgment, regulatory compliance verification, and liability protection. Financial advisors must validate that Claude's recommendations actually match each client's risk profile, financial goals, and regulatory constraints. This approach is not just best practice—it's a governance and risk management imperative. BLEU scores are NLP metrics irrelevant for evaluating financial advice quality. Engagement metrics don't measure recommendation accuracy or compliance. Single pre-deployment testing on synthetic data is insufficient for production financial advice; continuous evaluation and human oversight are essential.
Post your Comments and Discuss Anthropic CCAR-P exam prep with other Community members: