Option A correctly matches the model tier to the workload. An interactive, high-volume workflow with light reasoning places greater importance on response speed, operational efficiency, and cost than on maximum reasoning depth. Haiku is positioned as the fast, lightweight Claude model for responsive tasks, making it the appropriate starting choice.

Option B uses a criterion unrelated to performance. Option C is incorrect because model tiers differ in capability, latency, and cost characteristics. Option D prioritizes advanced reasoning even though the scenario explicitly states that reasoning demands are light and rapid responses are required. Selecting a more capable model than the task needs can increase latency and expense without producing a meaningful business benefit.

Model selection should still be validated empirically. The team should define an acceptable quality threshold, test representative customer-success requests, measure response latency and task accuracy, and confirm that Haiku meets the required service level. If the real workload contains complex exceptions, the workflow could route only those cases to a more capable model. Anthropic’s current learning materials characterize Haiku as its fastest option for lightweight work, while its prompt-engineering guidance identifies model selection as a direct lever for improving cost and latency. Anthropic’s Claude learning resources

================

Under the objective Identify, diagnose, and resolve issues with underperforming prompts and/or poor outputs (Domain 7: Troubleshooting and Optimization), troubleshooting follows a structured diagnostic protocol.

The troubleshooting sequence begins with symptom identification: reading the output end-to-end to categorize the exact flaw (e.g., factual error, structural omission, tone mismatch) (Step 3). Second, the practitioner performs an input-output diff: comparing the deficient output against the prompt instructions to spot instruction omissions or ambiguities (Step 4). Third, the practitioner forms a testable hypothesis regarding which prompt element caused the failure (Step 1). Fourth, they execute a controlled experiment by applying a single targeted prompt adjustment and observing the revised output (Step 2). Finally, they document the verified root cause and solution (Step 5). This establishes the order 3, 4, 1, 2, 5.

Under the objective Align model selection with task requirements (e.g., cost, speed, quality), model evaluation follows a structured engineering workflow prior to benchmark testing.

Before running comparative empirical tests on a representative sample dataset, the team must first establish evaluation criteria: defining the required output quality bar, maximum acceptable latency, throughput targets, and budget constraints (Option A). Next, the team maps those requirements against known model family characteristics (Haiku, Sonnet, Opus) to select the appropriate candidate models for testing (Option C). Once requirements are set and candidates selected, empirical sample testing can proceed. Promoting models to production (Option D), securing final platform/security rollout sign-offs (Option E), and ongoing regression testing for new model releases (Option B) are downstream deployment activities that occur after testing is completed.

Under the objective Integrate Claude into existing workflows to augment or redesign workflows, successfully incorporating AI into established business processes follows a structured systems engineering and change management lifecycle.

The sequence begins with baseline process mapping: documenting current as-is operational steps, role owners, and governance checkpoints (Step 2). Next, practitioners perform task decomposition to identify high-leverage opportunities for Claude augmentation while explicitly designating where human judgment must remain (Step 4). Once target touchpoints are identified, the technical and operational interface must be specified: defining the exact inputs, prompt structures, expected outputs, and hand-off protocols (Step 5). Before organization-wide adoption, the redesigned workflow is piloted with a representative cohort to gather empirical feedback and address friction points (Step 1). Finally, documentation and standard operating procedures (SOPs) are finalized for broad rollout (Step 3). This establishes the order 2, 4, 5, 1, 3.

Options B and E apply organizational governance and data-minimization requirements before the file enters Claude’s execution environment. The associate must first establish whether Code Execution is an approved processing method for the file’s classification. If the information exceeds the approved sensitivity level, the user must escalate to privacy, security, legal, or another designated authority rather than proceeding independently.

The file must also be inspected for customer identifiers, confidential fields, regulated information, credentials, or data unrelated to the calculation. Unnecessary fields should be removed, redacted, or anonymized. A sandbox limits interaction with the surrounding system, but it does not change the sensitivity of uploaded data, provide authorization, or override the organization’s handling rules. Therefore, Options C and D incorrectly treat technical isolation as a governance exemption. Option A allows urgency to displace mandatory review.

Anthropic explains that Code Execution runs in an isolated container, while also warning that file-processing configurations and network access create security considerations. Its privacy guidance recommends careful treatment of highly sensitive personal and confidential information. The correct control is to minimize and authorize the data before uploading it, not rely solely on the sandbox afterward. Anthropic’s Code Execution security guidance

================

Under the objective Apply data, privacy sensitivity, regulatory policies, and privacy considerations, managing confidential or market-sensitive figures requires controlling memory persistence and data retention settings.

Pre-announcement financial figures represent material non-public information (MNPI) that must not persist beyond the immediate analytical session. Option E applies privacy controls by utilizing Incognito mode, which ensures the session does not contribute to long-term memory or persist in chat history. Option B achieves the same data protection control in standard chat by explicitly toggling off Memory contributions, ensuring the sensitive number is not saved into persistent memory where it could leak into future unrelated prompts. Conversely, proceeding with default settings (Option A), assuming brief discussions avoid retention (Option C), or enabling persistent memory retention for confidential figures (Option D) creates serious compliance and insider data exposure risks.

Under the objective Edit, adapt, refine, and compare the output generated by Claude model(s) for the intended audience (Domain 2: Output Evaluation and Validation), adapting generated text requires restructuring content to match the executive decision-making style of the stakeholders.

Executive and investor audiences operate under strict time constraints and prioritize the bottom-line financial outcome before examining underlying mechanics (following the Minto Pyramid / Bottom-Line-Up-Front principle). Option C correctly structures the executive narrative: opening immediately with the headline financial figures, following with a concise breakdown of key operational drivers, and concluding with forward-looking guidance. Structuring the briefing chronologically (Option D) or burying core financial results in the middle of operational prose (Option A) creates cognitive friction and wastes time. Leading with the forward outlook before establishing current financial performance (Option B) lacks context.

A Skill from an unfamiliar party must be treated as untrusted until its origin and behavior are reviewed. Option A verifies provenance and confirms that the Skill is permitted by the organization’s governance process. Option B applies least privilege by examining what the Skill can access or execute and determining whether those capabilities are necessary for its stated task.

Public availability, popularity, or favorable reviews do not establish security. A Skill can contain instructions, scripts, dependencies, external calls, or other resources capable of causing unintended actions or exposing data. Therefore, Options C and D substitute reputation for technical and organizational validation. Option E is also unsafe because Skills may execute code or access resources available in the surrounding environment; assumed workflow boundaries are not a reliable security control.

Anthropic warns that malicious or compromised Skills can create prompt-injection, unauthorized-access, and data-exfiltration risks. Its guidance instructs users to install Skills only from trusted sources and to inspect bundled files, scripts, dependencies, network calls, and requested operations before enabling them. Organizational allowlists and permission reviews provide complementary controls: one establishes trust in the source, while the other limits what the Skill may do. Anthropic’s Skill security guidance

================

Under the objective Identify, diagnose, and resolve issues with underperforming prompts and/or poor outputs, diagnosing incomplete outputs requires mapping the specific failure mode directly to the corresponding prompt component.

When a model reliably answers some inquiries but completely omits another, the root cause is typically prompt ambiguity or buried instructions within dense prose. Strengthening the core task statement by explicitly enumerating the required deliverables (e.g., using numbered lists or tagged XML blocks like < question_1 > , < question_2 > , < question_3 > ) and mandating a complete response for each item (Option D) provides clear structural constraints that prevent omissions. Adding generic background context (Option A), changing persona framing (Option C), or relaxing output formatting constraints (Option B) fails to address the underlying instruction-following issue.

Under the objective Iterate prompts to improve output quality, systematic prompt optimization relies on disciplined, hypothesis-driven iteration using controlled variables.

When a prompt yields a partially acceptable result, modifying a single isolated element at a time—such as refining role framing, adjusting format constraints, or adding specific negative constraints—allows the user to establish clear causality between the prompt modification and the resulting output change (Option A). Documenting the effect of each adjustment ensures reproducible, predictable improvements. Conversely, making multiple simultaneous revisions (Options C and D) confounds the evaluation, making it impossible to determine which specific change helped or degraded output quality. Discarding work entirely on each run (Option B) eliminates incremental learning and increases iteration time.