You are transitioning a Claude-based deployment from design into implementation.
Which handoff package most directly supports a clean transition?
Option C provides the minimum coherent package required to move from architectural intent to implementable and supportable delivery. The architecture overview establishes system boundaries and component relationships. Architecture Decision Records preserve the context and trade-offs behind key choices. Component contracts define interfaces, schemas, responsibilities, failure behavior, and integration assumptions.
The evaluation framework and reference set allow the implementation team to confirm that prompts, models, retrieval components, and tool integrations continue to meet the defined quality, safety, latency, and cost thresholds. Runbooks translate operational knowledge into repeatable procedures, while the on-call playbook defines detection, escalation, containment, and recovery actions. The known-limitations register prevents unsupported behavior from being mistaken for an implementation defect and helps stakeholders manage residual risk.
Options A and B depend excessively on slides or undocumented verbal knowledge. Option D provides implementation material without explaining the system-level decisions, operating model, acceptance criteria, or limitations. Source code cannot substitute for architectural and operational documentation.
A clean transition does not mean the architect can never be consulted. It means routine implementation and support do not depend on undocumented knowledge held by a single individual.
Study Guide references/topics: Design-to-implementation handoff; ADRs; component contracts; reference evaluations; runbooks; operational playbooks; limitations management.
===============
A senior architect is managing stakeholder expectations for a Claude-based reporting assistant midway through development. Stakeholders have escalating concerns about response latency.
Which two actions most directly address stakeholder expectation alignment in this situation? (Select two.)
Expectation alignment begins with measured evidence. Option A gives stakeholders the median experience through p50 latency and the slower-tail experience through p95, then compares both with the agreed SLA. The measurements should reflect representative input sizes, concurrency, retrieval activity, tool calls, geographic routing, and cache conditions.
If the target remains infeasible after reasonable optimization, Option E establishes the correct governance response. The architect should collaboratively revise the SLA, scope, cost envelope, model choice, or user-experience design rather than silently accepting a breach or making unilateral changes. Any revision should document the business impact and accepted trade-offs.
Option B commits all resources before the problem's severity, causes, and business priority have been established. Option C wrongly treats latency as uncontrollable; model selection, prompt length, retrieval depth, caching, streaming, and architecture can materially affect it. Option D introduces an unvalidated provider and could create quality, security, compliance, and integration regressions.
Expectation management is not merely communicating bad news. It requires transparent measurements, credible optimization options, explicit trade-offs, and jointly approved commitments that the production architecture can actually satisfy.
Study Guide references/topics: SLA alignment; p50 and p95 latency; stakeholder negotiation; evidence-based communication; architectural trade-offs; production constraints.
===============
A managed agent deployment for claims triage has grown from 6 tools to 34 tools over 18 months as product teams added capabilities. Triage accuracy has declined from 91 percent to 78 percent, and average tool-selection latency has increased by 2.3 seconds. A junior engineer has proposed adding a tool-router agent in front of the current agent to filter the tool list per request.
Which two findings should you present to justify capability decomposition before adding the router? (Select two.)
Each correct answer presents part of the solution.
Four distinct workflow domains indicate that the agent's responsibilities have expanded beyond a cohesive capability boundary. Decomposing the deployment into domain-focused agents reduces each agent's tool-selection space and produces clearer prompts, permissions, evaluations, and ownership. Option E strengthens this conclusion because placing a model-based router before the existing overloaded agent adds latency, cost, and another failure point without correcting the underlying capability sprawl. Overlapping descriptions should be clarified, while unused tools may simply be removed; neither finding alone proves that separate domain agents are required. Public documentation of a pattern is not evidence that it fits this workload. Anthropic emphasizes simple composable patterns, clearly differentiated tools, and empirical evaluation before adding orchestration complexity. Building Effective Agents
You are supporting a team whose Claude Code sessions consistently load 60 or more MCP tools from many servers, exhausting context budget before the session begins.
Which adjustment most directly addresses this issue without removing capability?
Tool Search applies progressive discovery to a large tool catalog. Instead of inserting every MCP tool's complete JSON schema and description into the initial context, Claude receives limited discovery information and loads the full definitions only when a task requires them. This preserves the available context for instructions, repository content, conversation history, and tool results without removing the underlying capabilities.
Anthropic's Claude Code documentation states that Tool Search keeps MCP context usage low by deferring tool definitions until Claude needs them. Only the tools actually selected enter the working context. Claude Code MCP Tool Search
Anthropic's advanced-tool-use guidance also describes conventional multi-server configurations consuming tens of thousands of tokens before work begins, while on-demand discovery substantially reduces that overhead. Advanced Tool Use
Option B solves context pressure by destroying required functionality. Option C worsens the constraint by adding more prompt tokens. Option D expands the exact source of context bloat.
The team should also improve server and tool descriptions so discovery returns the correct tools, monitor tool-selection quality, and keep frequently required foundational tools non-deferred only when evaluations justify the additional context cost.
Study Guide references/topics: MCP scaling; Tool Search; progressive discovery; deferred schemas; context-budget management; tool-selection accuracy.
===============
Engineering leadership wants to roll out Claude Skills to 280 developers across 14 teams. Skills will encode internal coding standards, code-review checklists, and incident-postmortem templates. Leadership has asked how to govern Skill authorship so that Skills remain trustworthy without bottlenecking on a single central team.
Which governance model should you recommend?
Federated authorship allows each domain team to maintain the procedural knowledge it understands while preserving organization-wide trust through a central publication gate. Team authors can update coding standards, review practices, and postmortem procedures without waiting for a single platform group to write every change. Central reviewers can validate ownership, security, tool permissions, duplication, versioning, testing evidence, and compliance before publication. Per-developer or fully decentralized publication creates inconsistent and potentially unsafe Skills. Fully centralized authorship becomes a scalability bottleneck and separates content maintenance from domain expertise. Anthropic describes Skills as packages of instructions, scripts, and resources and warns that repository Skills may grant broad tool access, making formal review essential. Claude Code Skills
Ryan Green
12 days agoAdnan Hossain
15 days agoHafsa Rizvi
1 month agoAditya Iyer
2 months agoMing Wu
2 months agoPaul Collins
3 months ago