You are evaluating a Claude-based deployment for adherence to a specific regulation.
Which two steps must be completed BEFORE mapping deployment data flows to specific regulatory clauses?
(Select two.)
Each correct answer presents part of the solution.

• A. Compare the in-place controls against the regulatory requirements to identify any compliance gaps.
• B. Identify the applicability of the regulation based on data types, jurisdiction, and audience.
• C. Schedule the remediation work with the engineering team based on the prioritized gap findings.
• D. Inventory the vendor-provided compliance tooling and confirm which compliance affordances are in place.
• E. Document the identified gaps along with recommended remediations and residual risk for sign-off.

Explanation: Only visible for Prep4away members. You can sign-up / login (it's free).

You are transitioning a Claude-based deployment from design into implementation.
Which handoff package most directly supports a clean transition?

• A. Architecture overview, ADRs, component contracts, evaluation framework with reference set, runbooks, on-call playbook, and known limitations.
• B. 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.
• C. 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.
• D. A verbal walkthrough conducted on the day of handoff with no written architecture overview, ADRs, component contracts, evaluation framework, runbooks, playbook, or known limitations.

Explanation: Only visible for Prep4away members. You can sign-up / login (it's free).

You are defining an SLA for a Claude-based assistant.
Which SLA definition is most operationally meaningful?

• A. A measurable target with a defined metric, threshold, evaluation window, and consequence for breach- for example, "p95 per-request latency under 800 ms over a 28-day window."
• B. A qualitative commitment such as "the system will be fast and reliable," which names no metric, threshold, or evaluation window.
• C. A target that names the metric and threshold but omits the evaluation window and breach consequence, leaving compliance periods and remediation triggers undefined.
• D. A target tied to a stakeholder sentiment measure such as "the team feels satisfied," which cannot be measured objectively or used to trigger a documented breach response.

Explanation: Only visible for Prep4away members. You can sign-up / login (it's free).

You are classifying token-management tactics by where each tactic applies in the request lifecycle: "Input Preparation," "Prompt Construction," or "Output Handling."

Explanation:
* Persist the validated output for downstream consumption and audit - Output Handling
* Order prompt sections so cacheable content appears before per-request content - Prompt Construction
* Summarize prior conversation history when full history is no longer needed - Input Preparation
* Validate the model's structured output against the expected schema - Output Handling
* Move stable repeated content into a cacheable prefix at the beginning of the prompt - Prompt Construction
* Trim retrieved passages to spans relevant to the user's question - Input Preparation Input preparation determines what evidence and history should enter the request, so summarization and retrieval trimming belong there. Prompt construction determines ordering and cache boundaries; stable repeated instructions must precede dynamic per-request content to maximize cache reuse. Output handling begins after generation and includes schema validation, persistence, auditing, and downstream delivery.
Mixing these responsibilities creates inefficient prompts and weak validation boundaries. Anthropic's context guidance emphasizes curating the smallest useful context because unnecessary tokens can reduce recall and accuracy. Prompt caching similarly depends on a stable reusable prefix, while structured outputs or schema validation protect downstream systems from malformed responses. Context windows ; prompt caching

You are preparing a HIPAA-eligible deployment for a healthcare customer.
Which configuration supports HIPAA compliance using Anthropic-offered tools?

• A. An ad-hoc personal Claude account used by individual clinicians for PHI-related tasks, with no Business Associate Agreement, no Zero Data Retention, and no audit logging configured.
• B. Disabling all audit logging so that no PHI is recorded in any log store, on the assumption that the absence of logs satisfies HIPAA requirements without a signed BAA.
• C. Claude Free with no contractual addendum, since consumer products meet HIPAA requirements out of the box.
• D. Claude Enterprise with a signed Business Associate Agreement, Zero Data Retention enabled, and audit logging configured for compliance tracking.

Explanation: Only visible for Prep4away members. You can sign-up / login (it's free).