Under the objective Apply task decomposition techniques to structure complex requests, complex business problems must be decomposed hierarchically—from macro objectives down to granular operational artifacts.

Before generating low-level execution components such as scheduled email templates or individual checklists, the architect must first establish the high-level structure. This entails defining the overall strategic objective of the program (Option D) to establish success metrics, and identifying the sequential lifecycle phases (e.g., Pre-boarding, Day 1, Week 1, 30-60-90 days) of the onboarding journey (Option B). Once the overarching framework and chronological phases are clearly defined, prompt engineers can systematically task Claude with drafting the supporting content for each specific phase. Piloting (Option A) and full rollout (Option E) occur downstream after artifact creation, while budgetary negotiations (Option C) are outside workflow decomposition.

A sound assessment begins by establishing who will receive or rely on the output, the consequences of an incorrect result, and whether the resulting action can be reversed. This initial impact analysis determines the level of scrutiny required. The assessor should then identify the data involved, especially personal, confidential, regulated, or otherwise sensitive information. Once the use case and its information exposure are understood, it can be compared meaningfully against organizational AI policies, legal requirements, and regulatory restrictions.

The next step is to decide whether the use case should proceed, be modified with safeguards, or be rejected. Documentation comes last because it records the completed assessment, decision, supporting evidence, restrictions, and rationale for auditability. Therefore, the correct order is 3,5,1,4,2.

This sequencing reflects the AI Fluency principles of Delegation and Diligence: humans determine whether and how AI should be used and remain responsible for the consequences. Anthropic also advises users to be thoughtful about highly sensitive personal and business information. Options A, C, and D place policy review or data classification before the use case’s audience and impact have been properly established. Anthropic AI Fluency

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

Under the objective Differentiate between Claude model types (e.g., Haiku, Sonnet, Opus) (Domain 3: Product and Model Selection), Anthropic structures its model family across three clear tiers of intelligence, latency, and cost:

Claude Haiku: The fastest, most cost-efficient, and lightweight model designed for high-volume, low-latency tasks and simple classification.

Claude Sonnet: The balanced, versatile enterprise workhorse combining high intelligence and throughput for everyday knowledge-work tasks.

Claude Opus: The frontier model offering deep reasoning and analytical capacity for complex, multi-step problem solving at higher latency and operational cost.

Option C perfectly summarizes these structural trade-offs. Options A, B, and D misrepresent the capability hierarchy, speed profiles, and architectural tiering of the Claude family.

Under the objective Create effective system-level instructions (Domain 5: Configuration and Knowledge Management), engineering project-level system instructions follows a top-down operational framework.

Before authoring specific formatting rules, edge-case handlers, or role prompts, the author must first establish the high-level boundary architecture: defining the core objective and purpose of the Project, the target audience, and the explicit constraints/guardrails the model must respect (Option C). These foundational boundaries dictate what the model should do, what it must refuse or escalate, and how it must interact with attached reference knowledge. Attempting to validate instructions against test requests (Option B) or iteratively refine them (Option A) requires a drafted system prompt to exist first. Distributing instructions to team collaborators (Option D) is the final operational rollout step after validation is complete.

Under the objective Understand ethical implications of AI usage, applying AI in human resources demands rigorous bias auditing to ensure fair, standardized, and legally defensible evaluation practices.

Structured interviewing requires that questions focus strictly on observable, job-related competencies and avoid implicit assumptions or biased phrasing that could systematically disadvantage candidates from diverse non-traditional backgrounds (Option A). Human review must verify that Claude-generated questions remain objective, relevant, and standardized across applicants. Assuming AI outputs are unbiased by default and checking only stylistic tone (Option B) introduces compliance and equity risks. Injecting unstructured, ad-hoc questions per candidate (Option C) or scrambling question order inconsistently (Option D) undermines standardization and equitable scoring across applicant pools.

Option B provides the strongest balance between operational efficiency and proportionate human oversight. The historical correction rate demonstrates that Claude’s output cannot safely be treated as uniformly reliable, while the high weekly volume makes universal manual processing unnecessarily inefficient. A risk-based triage design allows clearly defined, low-value, reversible cases to proceed through tightly controlled automation while routing ambiguous or higher-impact cases to accountable human decision-makers.

The classification rules must be explicit and independently tested. Relevant factors could include refund amount, unusual transaction history, policy exceptions, disputed facts, suspected fraud, and the confidence or completeness of the available evidence. Standard cases would remain subject to human approval, while high-risk cases would receive supervisor review.

Options A and C rely primarily on retrospective sampling. That approach may detect patterns of errors, but it does not prevent an incorrect refund from being issued in an individual case. Option D preserves strong oversight but requires manual approval for every transaction, failing to use risk differentiation to address the cycle-time problem.

Claude should augment the workflow through classification, evidence gathering, and recommendation. Human authority must remain at the points where uncertainty, financial impact, or policy exceptions make an error more consequential.

Options A and B apply data minimization appropriately. The redacted job description contains the content necessary for adaptation without exposing unnecessary identifying information. Likewise, an anonymized HR-policy summary provides the policy substance required for rewriting while removing personal details. Both inputs are proportionate to routine content-generation tasks.

Options C, D, and E contain sensitive employee information. Accommodation records may reveal health or disability-related information and normally require heightened confidentiality and a clearly authorized business purpose. Named salary information is confidential compensation data. Employee identifiers and hire dates can be used to identify or profile individual workers and are unnecessary merely to personalize onboarding communications. Supplying such information would violate the principle of using only the minimum data necessary for the task.

Anthropic advises users to be thoughtful about sharing sensitive personal, health, financial, and confidential business information. Its customer-support implementation guidance also recommends removing personally identifiable information unless it is explicitly required and authorized. Organizational classification rules, approved tools, access controls, contractual terms, and applicable privacy requirements must still be followed even when information has been partially redacted. Anthropic’s sensitive-data guidance

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

Answer D is the intended answer. A connected knowledge source may temporarily return an earlier document version when its searchable index has not yet processed a recent revision. The three-hour interval strongly points to synchronization or indexing latency rather than a reasoning or prompting failure. The worker should verify the document’s modification time in Google Drive, open the cited source, retry the retrieval, and, if necessary, provide the document directly by URL.

Option A claims that the old version remains fixed for the entire chat session, which is not an established connector rule. Option B invents a separate permission group without supporting evidence; permissions ordinarily determine whether the user can access a file, not which historical version is visible. Option C is also unsupported because Claude does not normally choose an obsolete version merely because it is longer.

However, this question reflects an older indexed-connector model. Anthropic’s current documentation states that Google Docs added directly to chats or private Projects synchronize from Google Drive and should provide the latest version. Therefore, D remains the best answer among the choices and is likely the expected exam answer, but the item should be reviewed if it is intended to test current Claude behavior. Anthropic: Google Workspace connectors

The correct sequence is 4,3,1,5,2. Optimization must begin by mapping the current workflow, including its steps, owners, inputs, handoffs, and decision points. Without an accurate current-state map, the team cannot reliably associate delays or defects with a particular stage. It should then use measured evidence—such as processing time, waiting time, queue length, rework, or error frequency—to identify the actual bottleneck.

After locating the constraint, the team can apply a targeted improvement to that step. Changing the workflow before identifying the bottleneck, as in Option C, risks optimizing a noncritical activity while leaving the primary delay untouched. The change should next be piloted with a limited group and compared against the previous baseline. This determines whether the intervention improves throughput or quality without creating downstream problems. Only after a successful pilot should the process be rolled out broadly and formally documented.

This sequence is consistent with Anthropic’s evaluation approach: define measurable criteria, test changes against representative conditions, and validate performance before production use. Option D identifies the bottleneck before establishing the workflow map needed to interpret the measurements. Anthropic’s evaluation guidance

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

Under the objective Identify, diagnose, and resolve issues with underperforming prompts and/or poor outputs, workflow optimization must be rooted in evidence-based diagnostics before making modifications to system instructions or prompt chains.

The diagnostic phase requires two prerequisite steps: establishing a quantitative baseline by measuring quality metrics, latency, token spend, and human intervention frequency across recent historical runs (Option D), and conducting a bottleneck analysis to pinpoint the exact sub-steps responsible for performance degradation, excessive token cost, or quality defects (Option B). Implementing changes without these baseline diagnostics leads to blind iterations. Deployment (Option C) and SOP updates (Option E) are downstream execution phases, while leadership notifications (Option A) occur after solutions are verified.