Your team is designing a customer support system that integrates Claude with your company's CRM,ticketing system, and knowledge base. Support agents will use Claude to suggest responses, but agents remain in control of all customer communications. The team is debating whether to optimize for the Claude 3.5 Haiku model (faster, cheaper, smaller) or Claude 3.5 Sonnet (more capable, higher accuracy).Which factors should primarily drive this model selection decision?
Answer(s): C
Optimal model selection requires holistic analysis of task requirements, not just cost or capability in isolation. For support response suggestions, you must evaluate whether Haiku's speed and cost advantages outweigh any quality gaps, considering that agents review and modify responses before sending them. Context retrieval from CRM and knowledge base, agent workflow latency expectations, and total operational cost (including time spent by agents correcting poor suggestions) all factor into the decision. A phased evaluation with production data is more rigorous than arbitrary trials. Cost minimization alone ignores quality impact on agent efficiency. Choosing purely on capability ignores cost and latency trade-offs in an agent-supervised context where Haiku may be sufficient.
During an architectural review, the security team identifies a risk that adversarial content injected into retrieved documents could manipulate the model's behavior.Which mitigation most directly addresses this threat?
Answer(s): A
The scenario describes indirect prompt injection: malicious instructions are embedded in third-party content that Claude processes as retrieved evidence. Option A addresses the threat at the appropriate boundary by classifying retrieved material as untrusted, screening it before use, and validating the model's output before it can influence downstream actions.Anthropic recommends placing untrusted third-party content in clearly identified tool-result structures, explicitly instructing Claude that retrieved content cannot override system or user instructions, screening tool output for injection attempts, and applying output validation. Mitigate Jailbreaks and Prompt InjectionsCitations in Option B improve factual traceability but do not prevent embedded instructions from attempting to redirect model behavior. An outbound destination allow-list in Option C limits the damage that a compromised agent can cause through tool calls, but it does not directly detect or neutralize the injected content. Option D is valuable for detecting behavioral regression after a model change, not for controlling a specific malicious document during runtime.A production implementation should combine content provenance, structural separation, injection screening, least-privilege tools, output-schema validation, and human confirmation for consequential actions.Study Guide references/topics: Indirect prompt injection; untrusted retrieved content; input classification; output validation; layered runtime guardrails.
HOTSPOT (Drag and Drop is not supported)You are evaluating model-selection claims used by a peer team.For each statement, select yes if the statement is generally true. Otherwise, select no.QUESTION IMAGE:
CORRECT AREA HIGHLIGHTED
You are explaining the precedence of Claude Code configuration scopes to the team.Which precedence ordering, from highest to lowest, is correct?
The correct general precedence is managed configuration, command-line arguments, local configuration, project configuration, and then user configuration.Managed configuration has the highest authority because it contains centrally administered organizational and compliance controls that ordinary engineers must not be able to override. Command-line arguments provide temporary session-level overrides where the relevant setting permits them. Local settings apply to one user within a specific repository and take precedence over the shared project configuration. Project settings apply to every contributor using that repository and override general user preferences. User settings form the lowest tier because they provide personal defaults across projects and apply only when no higher-precedence source supplies a value.Anthropic documents this order explicitly: managed, command line, local, project, and user. It also notes that permission rules may merge rather than behave as simple scalar overrides, and certain security-sensitive keys have specialized precedence behavior. Claude Code Configuration ScopesThe ordering allows personal customization without permitting it to defeat repository conventions or centrally mandated security requirements. Architects must still examine the merge behavior of the individual configuration property rather than assuming every array or permission rule is replaced wholesale.Study Guide references/topics: Claude Code configuration; scope precedence; managed policies; local overrides; project settings; user defaults.
A Claude architect needs to ensure that a security-hardening flag cannot be disabled by any individual engineer after it is set.Which configuration scope correctly enforces this requirement?
Managed configuration is designed for organization-wide security and compliance controls that individual users and repositories must not override. Applying the hardening flag centrally establishes an administrative policy boundary and prevents engineers from disabling the control through user, project, or local settings.Anthropic identifies managed scope as the appropriate location for security policies, non-overridable compliance requirements, and standardized configurations deployed by IT or DevOps. Managed values ordinarily take precedence over command-line arguments and every user-controlled settings scope. Claude Code SettingsOption A depends on every engineer maintaining the setting and allows the user to edit or delete it. Option B affects only pipeline execution and does not protect local, interactive, IDE, or other execution paths. Option D standardizes the setting within the repository but does not make it tamper-resistant; contributors with repository write access could alter the file, use higher-precedence local settings where permitted, or operate outside the repository configuration.The implementation should also verify active policy delivery, monitor configuration-change events, and test that startup or execution fails safely if the managed setting is absent or invalid. Central definition without enforcement and verification would not fully satisfy the requirement.Study Guide references/topics: Managed settings; non-overridable controls; enterprise hardening; policy enforcement; configuration governance; defense against local override.
Post your Comments and Discuss Anthropic CCAR-P exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CCAR-P content, but please register or login to continue.