Question 10
A public-funding proposal writer needs an independent check that every material assertion is supported before publication. In a different workflow, an online returns bot routes simple questions through several expensive specialists without improving outcomes. Which TWO orchestration changes address these distinct problems? Choose TWO.
- Run independent specialists in parallel with a merge contract
- Delegate only specialized subtasks that add measurable value
- Separate independent critique from generation
- Version the handoff artifacts between agents
- Use a coordinator to route distinct specialist tasks
Explanation
Correct Answers
B:Introduce a specialist only when its independent expertise, tool scope, or parallelism beats a simpler call on representative evaluations; measuring the contribution of each delegate reveals needless orchestration layers; its corresponding workstream should be validated by marginal quality improvement per added specialist against its incremental cost and latency.
C:A distinct verifier with a rubric and evidence access can challenge unsupported assertions before an external document is released; targeted seeded errors test whether critique catches defects rather than merely rewriting prose; its corresponding workstream should be validated by verified claim support rate after independent critique on seeded unsupported drafts.
Incorrect Answers
A:Parallel fan-out followed by deterministic aggregation can shorten wall-clock time if each branch has its own contract and errors are handled; parallel fan-out is unsafe when tasks mutate the same state or depend on each other's evolving outputs; its natural acceptance measure is p95 end-to-end latency and deterministic merge completeness under one-branch failures, which does not satisfy the separate workstreams being assessed.
D:Immutable, versioned handoff artifacts and typed schemas prevent one agent from consuming ambiguous or mismatched intermediate state; artifact versioning governs exchange correctness, not whether the underlying market facts were researched accurately; its natural acceptance measure is zero stale-artifact merges across concurrent revision and retry scenarios, which does not satisfy the separate workstreams being assessed.
E:A coordinator can dispatch scoped subagents and merge their typed outputs while restricting each specialist's context and tools; specialist routing adds handoffs and can be wasteful for one small, homogeneous transformation; its natural acceptance measure is completed reports with correctly scoped evidence and no cross-specialty data leakage, which does not satisfy the separate workstreams being assessed.
Question 11
A European financial institution must substantiate where sensitive records travel through inference, retrieval, logs, and subprocessors. A separate American clinical-services provider is evaluating a system that would process regulated patient information. Which TWO compliance actions are essential to the respective deployment decisions? Choose TWO.
- Check HIPAA business associate and safeguard requirements
- Implement accountable access, deletion, and retention processes
- Map data residency commitments to actual processing paths
- Assess privacy risks and lawful processing grounds early
- Minimize personal data and specify retention purpose
Explanation
Correct Answers
A:Confirm the specific service and contract support relevant HIPAA obligations, including any required business associate agreement and safeguards; compliance verification must match the actual product configuration and agreement; its corresponding workstream should be validated by approved contracting, access controls, and PHI data-flow verification for the selected service path.
C:Trace storage, inference, retrieval, logs, backups, and subprocessors against contractual and legal location requirements; a full data-flow audit finds secondary exports that primary-storage checks miss; its corresponding workstream should be validated by verified geographic processing paths for all sensitive request components.
Incorrect Answers
B:Map data copies, implement lifecycle deletion where required, and retain audit evidence of the authorized request and its completion; deleting the original row does not automatically erase embeddings, caches, or observability copies; its natural acceptance measure is deletion-request completion across all inventoried repositories within policy deadlines, which does not satisfy the separate workstreams being assessed.
D:Involve privacy counsel to assess applicable lawful bases, transparency, rights, and whether a data-protection impact assessment is required before release; technical model accuracy does not establish permission to process sensitive personal information; its natural acceptance measure is completion of required privacy assessment and recorded resolution of high risks before go-live, which does not satisfy the separate workstreams being assessed.
E:Limit processing to necessary authorized fields, define a lawful purpose and retention controls, and document relevant privacy obligations; broad encryption does not justify collecting more personal data than the task needs; its natural acceptance measure is sensitive-field inclusion rate in prompts and retention-policy compliance, which does not satisfy the separate workstreams being assessed.
Question 12
A business unit wants to procure an entire Claude platform before verifying its most important workflow's data feasibility. Which design decision directly addresses this constraint?
- Set an evidence gate before moving beyond discovery
- Plan deprecation and rollback from the start
- Use bounded pilots with exit criteria before expansion
- Run a recurring monitoring-to-improvement loop
- Include security and governance checks during design
Explanation
Correct Answer
A:Require validated problem scope, value hypothesis, data authority, and feasibility evidence before full design commitment; stage gates prevent costly commitment to untested assumptions; evaluate the design with closure of high-risk feasibility questions before design approval.
Incorrect Answers
B:Inventory consumers, define migration dates and fallback, preserve data obligations, and test the rollback or retirement path; removing an old endpoint alone does not manage hidden dependencies or operational continuity; this alternative would measure successful retirement with zero unplanned dependent-system failures; it does not establish closure of high-risk feasibility questions before design approval for the described use case.
C:Define pilot size, critical acceptance metrics, escalation paths, and scale-up criteria before broad deployment; more launch enthusiasm does not replace production-like testing under load and edge conditions; this alternative would measure pilot gate pass rate with defined performance and safety thresholds; it does not establish closure of high-risk feasibility questions before design approval for the described use case.
D:Feed production samples and feedback into versioned evals, prioritize changes, and release improvements behind regression gates; a one-time launch test cannot guarantee reliability under changing input distributions; this alternative would measure cycle time from detected drift to validated improvement without safety regression; it does not establish closure of high-risk feasibility questions before design approval for the described use case.
E:Incorporate threat modeling, authorization, data processing, and human oversight into architecture acceptance before implementation hardens; post-build security sign-off is costly and may not undo prior unauthorized processing; this alternative would measure resolution of high-severity architecture risks before implementation approval; it does not establish closure of high-risk feasibility questions before design approval for the described use case.
Question 13
Several internal applications consume the same customer-directory MCP endpoint. Compatibility and permission tests run from different client identities. Which result would prove the shared contract is secure and portable?
- Reproducible build results with denied commands outside the approved allowlist
- Event-to-index update delay and duplicate-event idempotency under replay
- Successful authenticated task exchange with each agent retaining its own permission checks
- Search coverage, tool cost, and provenance checks with no application-owned execution endpoint
- Cross-client contract compatibility and unauthorized-action denial for the same MCP service
Explanation
Correct Answer
E:Testing both interoperability and permission enforcement captures the two essential concerns; measure cross-client contract compatibility and unauthorized-action denial for the same MCP service at the release gate; a maintained MCP server can standardize discoverable tool and resource contracts while each client still enforces authentication and trust.
Incorrect Answers
A:Execution tests check both the developer outcome and the sandbox boundary; a bounded CLI execution environment can reuse standard developer tools with explicit directory and command permissions; this tests reproducible build results with denied commands outside the approved allowlist; the actual release condition is cross-client contract compatibility and unauthorized-action denial for the same MCP service.
B:Event-driven tests verify timely updates without wasteful polling loops; an authenticated event or webhook integration can trigger bounded processing only when upstream state changes; this tests event-to-index update delay and duplicate-event idempotency under replay; the actual release condition is cross-client contract compatibility and unauthorized-action denial for the same MCP service.
C:Boundary tests verify interoperability without merging authorities; an agent-to-agent contract can exchange bounded tasks and outputs while preserving local autonomy, identity, and authority of each specialist system; this tests successful authenticated task exchange with each agent retaining its own permission checks; the actual release condition is cross-client contract compatibility and unauthorized-action denial for the same MCP service.
D:Managed execution should reduce infrastructure burden without weakening answer grounding; a supported server-executed tool can offload execution to the provider while the application retains usage, privacy, and result-validation responsibilities; this tests search coverage, tool cost, and provenance checks with no application-owned execution endpoint; the actual release condition is cross-client contract compatibility and unauthorized-action denial for the same MCP service.
Question 14
A healthcare operations application will process protected clinical information using a selected Claude deployment route. Which release evidence would establish that agreements, security controls, and actual data flows have been assessed for that route?
- Deletion-request completion across all inventoried repositories within policy deadlines
- Documented authorization-boundary mapping for every service handling regulated data
- Verified geographic processing paths for all sensitive request components
- Approved contracting, access controls, and PHI data-flow verification for the selected service path
Explanation
Correct Answer
D:Compliance verification must match the actual product configuration and agreement; measure approved contracting, access controls, and PHI data-flow verification for the selected service path at the release gate; confirm the specific service and contract support relevant HIPAA obligations, including any required business associate agreement and safeguards.
Incorrect Answers
A:End-to-end lifecycle tests verify more than the source system's delete operation; map data copies, implement lifecycle deletion where required, and retain audit evidence of the authorized request and its completion; this tests deletion-request completion across all inventoried repositories within policy deadlines; the actual release condition is approved contracting, access controls, and PHI data-flow verification for the selected service path.
B:Boundary-specific checks prevent assuming certification transfers between unrelated services; verify the specific service, region, impact level, boundary, and agency authorization requirements with security officials before selection; this tests documented authorization-boundary mapping for every service handling regulated data; the actual release condition is approved contracting, access controls, and PHI data-flow verification for the selected service path.
C:A full data-flow audit finds secondary exports that primary-storage checks miss; trace storage, inference, retrieval, logs, backups, and subprocessors against contractual and legal location requirements; this tests verified geographic processing paths for all sensitive request components; the actual release condition is approved contracting, access controls, and PHI data-flow verification for the selected service path.
Question 15
A scholarship screening copilot flags possible eligibility issues that affect subsequent human decisions. What should the solution architect recommend?
- Test accessibility of generated explanations and interfaces
- Provide a route to challenge significant recommendations
- Measure errors across relevant user subgroups
- Design an override path proportionate to consequences
- Expose evidence and decision boundaries to affected users
Explanation
Correct Answer
B:Provide a contest and correction process with accountable human ownership for significant impacts; remedy effectiveness measures whether affected people can obtain meaningful reconsideration; evaluate the design with time to resolve substantiated challenges and proportion of cases with documented review.
Incorrect Answers
A:Include accessibility requirements, assistive-technology testing, and inclusive content rubrics in evaluation and design; factual accuracy alone does not make the interface usable to everyone; this alternative would measure task completion by users of tested assistive technologies on representative flows; it does not establish time to resolve substantiated challenges and proportion of cases with documented review for the described use case.
C:Evaluate suitable subgroup error rates and access outcomes, with privacy-aware sampling and appropriate fairness review; overall accuracy cannot establish comparable treatment for every affected population; this alternative would measure quality and escalation parity across predeclared language segments; it does not establish time to resolve substantiated challenges and proportion of cases with documented review for the described use case.
D:Preserve an authorized override and recovery route scaled to decision consequences, with feedback recorded for evaluation; human review after an irreversible action may be too late to prevent harm; this alternative would measure successful intervention before seeded high-impact incorrect actions are committed; it does not establish time to resolve substantiated challenges and proportion of cases with documented review for the described use case.
E:Distinguish evidence, uncertainty, and advisory status with accessible citations and a path to authoritative decisions; a polished explanation without provenance may create false confidence in unsupported reasoning; this alternative would measure user comprehension of advisory status and source-citation validity; it does not establish time to resolve substantiated challenges and proportion of cases with documented review for the described use case.
Question 16
Sequential waits dominate latency even though the three read-only assessments have no dependencies. What design correction resolves the reported failure?
- Delegate only specialized subtasks that add measurable value
- Version the handoff artifacts between agents
- Use a coordinator to route distinct specialist tasks
- Run independent specialists in parallel with a merge contract
Explanation
Correct Answer
D:Parallel fan-out followed by deterministic aggregation can shorten wall-clock time if each branch has its own contract and errors are handled; this validates concurrency benefits without silently dropping a missing assessment; verify the repair using p95 end-to-end latency and deterministic merge completeness under one-branch failures.
Incorrect Answers
A:More agents by themselves do not provide additional knowledge, authority, or better outcomes; introduce a specialist only when its independent expertise, tool scope, or parallelism beats a simpler call on representative evaluations; that control is assessed by marginal quality improvement per added specialist against its incremental cost and latency; the incident instead requires p95 end-to-end latency and deterministic merge completeness under one-branch failures.
B:Artifact versioning governs exchange correctness, not whether the underlying market facts were researched accurately; immutable, versioned handoff artifacts and typed schemas prevent one agent from consuming ambiguous or mismatched intermediate state; that control is assessed by zero stale-artifact merges across concurrent revision and retry scenarios; the incident instead requires p95 end-to-end latency and deterministic merge completeness under one-branch failures.
C:Specialist routing adds handoffs and can be wasteful for one small, homogeneous transformation; a coordinator can dispatch scoped subagents and merge their typed outputs while restricting each specialist's context and tools; that control is assessed by completed reports with correctly scoped evidence and no cross-specialty data leakage; the incident instead requires p95 end-to-end latency and deterministic merge completeness under one-branch failures.
Question 17
Prompt caching is enabled for a policy assistant, yet per-request identifiers are inserted before the stable policy material. Almost every request incurs cache-creation cost. Which change should restore reuse without caching private identifiers as shared content?
- Load specialized Skills only when the task needs them
- Cache a stable, high-volume prompt prefix
- Keep dynamic fields out of cached prefix content
- Instrument cache effectiveness with token usage counters
- Modularize shared task instructions for consistent reuse
Explanation
Correct Answer
C:Move changing metadata after the stable prefix so cache keys remain reusable across otherwise similar requests; controlled request pairs reveal avoidable cache invalidation; verify the repair using prefix reuse ratio when request metadata changes across calls.
Incorrect Answers
A:Skills provide reusable guidance, not a separate security boundary or a substitute for approved tool permissions; keep Skills discoverable and load task-relevant instructions or resources on demand, maintaining scope and permission constraints; that control is assessed by task success with reduced irrelevant instruction tokens across mixed workflows; the incident instead requires prefix reuse ratio when request metadata changes across calls.
B:Caching helps repeated identical prefixes; it does not improve a model's answer accuracy on missing knowledge; put reusable instructions and reference material in a consistent prefix and use supported prompt-cache controls while placing variable requests afterward; that control is assessed by cache-read input tokens and end-to-end latency over repeated requests; the incident instead requires prefix reuse ratio when request metadata changes across calls.
D:A faster model might improve latency but would not explain a missing cache hit on identical prompts; compare cache-creation and cache-read token telemetry and inspect prefix ordering, eligible size, and reuse timing; that control is assessed by sustained cache-read token share under repeated workload replay; the incident instead requires prefix reuse ratio when request metadata changes across calls.
E:Prompt modularity simplifies governance; it cannot alone guarantee that a sensitive tool call is authorized; maintain a versioned reusable prompt module with explicit parameters and regression tests across consumers; that control is assessed by cross-application prompt-version alignment and regression pass rate; the incident instead requires prefix reuse ratio when request metadata changes across calls.
Question 18
A software team wants consistent build commands, code style, and testing expectations across developers using Claude Code. Which intervention is most appropriate for this use case?
- Use specialized subagents with bounded tools and instructions
- Version team-wide CLAUDE.md guidance with the repository
- Use managed configuration to constrain dangerous permissions
- Scope MCP connections by project and user identity
Explanation
Correct Answer
B:Put reviewed repository-specific guidance in a shared CLAUDE.md file with appropriate scope and code review; reproducible onboarding shows whether team guidance is discoverable and current; evaluate the design with consistency of generated changes with repository build and test conventions across fresh sessions.
Incorrect Answers
A:Give each delegated role explicit objectives, context limits, and tool permissions with clear return artifacts; delegation without role scoping merely multiplies the number of powerful agents; this alternative would measure subagent task completion with zero out-of-scope tool access; it does not establish consistency of generated changes with repository build and test conventions across fresh sessions for the described use case.
C:Use organization-managed policy and supported permission configuration so enforced restrictions cannot be casually overridden by per-user convenience settings; personal preference files are not a trustworthy substitute for centrally governed high-risk permissions; this alternative would measure denial of prohibited commands after attempts to override local and project configuration; it does not establish consistency of generated changes with repository build and test conventions across fresh sessions for the described use case.
D:Choose appropriate configuration scope and per-user or service authorization for MCP servers, avoiding shared cross-project secrets; a working connection does not prove the assistant is restricted to the user's intended project resources; this alternative would measure access denial for cross-project MCP resources under user identity tests; it does not establish consistency of generated changes with repository build and test conventions across fresh sessions for the described use case.
Question 19
An engineering team reports that prompt caching is configured but needs financial proof under its real workload. Which observed token pattern is stronger evidence than the mere presence of a cache flag?
- Net cost per accepted request across realistic interarrival times
- Cache-read input tokens and end-to-end latency over repeated requests
- Sustained cache-read token share under repeated workload replay
- Task success with reduced irrelevant instruction tokens across mixed workflows
Explanation
Correct Answer
C:Cache-specific counters distinguish a configuration issue from ordinary inference variance; measure sustained cache-read token share under repeated workload replay at the release gate; compare cache-creation and cache-read token telemetry and inspect prefix ordering, eligible size, and reuse timing.
Incorrect Answers
A:Reuse-adjusted economics tests whether the caching decision pays off under actual traffic; assess eligible caching windows, traffic frequency, and write/read economics against real reuse intervals before selecting a cache policy; this tests net cost per accepted request across realistic interarrival times; the actual release condition is sustained cache-read token share under repeated workload replay.
B:Cache-hit telemetry verifies the optimization rather than relying on estimated token savings; put reusable instructions and reference material in a consistent prefix and use supported prompt-cache controls while placing variable requests afterward; this tests cache-read input tokens and end-to-end latency over repeated requests; the actual release condition is sustained cache-read token share under repeated workload replay.
D:On-demand loading must retain quality while avoiding unnecessary context overhead; keep Skills discoverable and load task-relevant instructions or resources on demand, maintaining scope and permission constraints; this tests task success with reduced irrelevant instruction tokens across mixed workflows; the actual release condition is sustained cache-read token share under repeated workload replay.
Question 20
A distributed team uses Claude to generate code on different laptops and sees inconsistent local test results. Which approach best meets the stated requirement?
- Run reproducible CI gates on assisted code
- Generate documentation from verified source and review it
- Use test-first acceptance cases for generated changes
- Break large refactors into independently reviewable changes
Explanation
Correct Answer
A:Execute standardized linting, type checks, tests, and security scanning in versioned CI environments before merges; independent automation prevents environmental drift from masquerading as code correctness; evaluate the design with cI pass reproducibility on clean builds with locked dependencies.
Incorrect Answers
B:Ground documentation generation in current code, schemas, and tests, then validate examples and have owners review changes; fluent prose generated from old context is not a reliable record of a current API contract; this alternative would measure documented endpoint examples executing successfully against the reviewed build; it does not establish cI pass reproducibility on clean builds with locked dependencies for the described use case.
C:Define executable tests and expected behavior before relying on AI-generated implementation, then review failures and iterate; merely reading generated code for plausibility does not replace tests of business invariants; this alternative would measure passing unit and property tests including specified rounding boundaries; it does not establish cI pass reproducibility on clean builds with locked dependencies for the described use case.
D:Use small scoped changes, compatibility checkpoints, and separate pull requests tied to specific tests; one massive patch can reduce initial coordination but increases regression and rollback risk; this alternative would measure review time and defect localization per incremental change set; it does not establish cI pass reproducibility on clean builds with locked dependencies for the described use case.