Question 250
An audit of a frontend component repair effort asks how to make sure that long project guidance is divided into maintainable source files. Which implementation should be selected?
- use CLAUDE.md imports to organize referenced instructions
- place personal instructions in the user-level CLAUDE.md
- duplicate full instruction paragraphs in every directory
- place a dedicated CLAUDE.md in the relevant directory
Explanation
Correct Answer
A:For a frontend component repair effort, modular imports keep a short entry point while preserving reviewed details in separate files; this directly establishes that long project guidance is divided into maintainable source files instead of relying on an unrelated workflow control.
Incorrect Answers
B:Although global personal guidance is available to that user's sessions without committing preferences to the project, that only supports the distinct goal that a developer has private preferences that should not change team guidance, not the requirement that long project guidance is divided into maintainable source files in a frontend component repair effort.
C:In a frontend component repair effort, copying guidance encourages drift when policies change; as a result, the stated requirement that long project guidance is divided into maintainable source files would still not be met.
D:Although directory-specific context can refine instructions for work under that subtree, that only supports the distinct goal that only a nested service uses specialized implementation rules, not the requirement that long project guidance is divided into maintainable source files in a frontend component repair effort.
Question 251
The release gate for an order-cancellation service requires that sensitive tool calls are denied before they reach an executor; it also requires that a delegated reviewer has no production write capability. Which TWO actions meet the specified checks? Choose TWO.
- register a PreToolUse hook that checks the operation against policy
- write a stronger instruction in the system prompt
- provide only the read-oriented tools required by that reviewer
- give the reviewer every administrative tool and ask for restraint
Explanation
Correct Answers
A:For an order-cancellation service, pre-execution interception can reject a disallowed call rather than relying on post-hoc advice, which directly establishes that sensitive tool calls are denied before they reach an executor; the separate requirement that a delegated reviewer has no production write capability is handled by a different action.
C:For an order-cancellation service, agent-scoped tool exposure prevents a write path in a read-only role, which directly establishes that a delegated reviewer has no production write capability; the separate requirement that sensitive tool calls are denied before they reach an executor is handled by a different action.
Incorrect Answers
B:For an order-cancellation service, an instruction alone does not provide deterministic execution-time authorization, so this option cannot establish that sensitive tool calls are denied before they reach an executor; correctly addressing a delegated reviewer has no production write capability elsewhere does not repair that deficiency.
D:For an order-cancellation service, prompt restraint is weaker than withholding execution capability, so this option cannot establish that a delegated reviewer has no production write capability; correctly addressing sensitive tool calls are denied before they reach an executor elsewhere does not repair that deficiency.
Question 252
When designing a compliance interpretation research team, the requirement is not satisfied unless the reviewer does not simply echo the generator's confidence and a partially successful multi-agent job reports its limitations. Which implementation addresses the two independent conditions?
- provide the generator's score as the sole review criterion; and aggregate per-agent success and incomplete-state metadata
- give the reviewer the source and rubric, not only the draft's self-rating; and aggregate per-agent success and incomplete-state metadata
- give the reviewer the source and rubric, not only the draft's self-rating; and mark the whole request successful when any one branch returns data
- provide the generator's score as the sole review criterion; and mark the whole request successful when any one branch returns data
Explanation
Correct Answer
B:In a compliance interpretation research team, independent evidence lets a critic challenge unsupported assertions; alongside this, partial status lets the coordinator qualify conclusions and retry missing branches, satisfying the distinct requirements that the reviewer does not simply echo the generator's confidence and that a partially successful multi-agent job reports its limitations.
Incorrect Answers
A:In a compliance interpretation research team, partial status lets the coordinator qualify conclusions and retry missing branches, but anchoring on a self-assigned grade hides actual defects; therefore the separate requirement that the reviewer does not simply echo the generator's confidence would remain unsatisfied.
C:In a compliance interpretation research team, independent evidence lets a critic challenge unsupported assertions, but some required evidence may still be missing; therefore the separate requirement that a partially successful multi-agent job reports its limitations would remain unsatisfied.
D:In a compliance interpretation research team, anchoring on a self-assigned grade hides actual defects and some required evidence may still be missing; the design would fail both conditions: the reviewer does not simply echo the generator's confidence and a partially successful multi-agent job reports its limitations.
Question 253
Before expanding a static analysis automation, the owner must demonstrate that only a nested service uses specialized implementation rules, while also demonstrating that CI failures provide actionable evidence to maintainers. Which design provides both controls?
- put all service-only details in the repository root instruction file; and persist structured errors, relevant logs, and a bounded diagnostic summary
- place a dedicated CLAUDE.md in the relevant directory; and discard the runner logs and keep only the assistant's final sentence
- place a dedicated CLAUDE.md in the relevant directory; and persist structured errors, relevant logs, and a bounded diagnostic summary
- put all service-only details in the repository root instruction file; and discard the runner logs and keep only the assistant's final sentence
Explanation
Correct Answer
C:In a static analysis automation, directory-specific context can refine instructions for work under that subtree; alongside this, stable artifacts help maintainers reproduce the problem without rerunning a chat, satisfying the distinct requirements that only a nested service uses specialized implementation rules and that CI failures provide actionable evidence to maintainers.
Incorrect Answers
A:In a static analysis automation, stable artifacts help maintainers reproduce the problem without rerunning a chat, but globalizing narrow rules adds irrelevant instructions to unrelated work; therefore the separate requirement that only a nested service uses specialized implementation rules would remain unsatisfied.
B:In a static analysis automation, directory-specific context can refine instructions for work under that subtree, but the missing trace impedes diagnosis of command or infrastructure failures; therefore the separate requirement that CI failures provide actionable evidence to maintainers would remain unsatisfied.
D:In a static analysis automation, globalizing narrow rules adds irrelevant instructions to unrelated work and the missing trace impedes diagnosis of command or infrastructure failures; the design would fail both conditions: only a nested service uses specialized implementation rules and CI failures provide actionable evidence to maintainers.
Question 254
During review of a returns-and-billing assistant, an unmet criterion states that one specialist's crash does not discard other verified outputs. Which measure resolves this specific gap?
- propagate task IDs, error codes, and correlation references
- restart every agent and erase prior results after a single crash
- isolate branch failures and preserve completed artifacts for coordination
- aggregate per-agent success and incomplete-state metadata
Explanation
Correct Answer
C:For a returns-and-billing assistant, fault containment avoids losing good work while a failed branch is repaired; this directly establishes that one specialist's crash does not discard other verified outputs instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although tracing execution lineage helps route the incident to the right failing component, that only supports the distinct goal that the coordinator can identify which subagent produced a broken artifact, not the requirement that one specialist's crash does not discard other verified outputs in a returns-and-billing assistant.
B:In a returns-and-billing assistant, unaffected branches would be redone and provenance could be lost; as a result, the stated requirement that one specialist's crash does not discard other verified outputs would still not be met.
D:Although partial status lets the coordinator qualify conclusions and retry missing branches, that only supports the distinct goal that a partially successful multi-agent job reports its limitations, not the requirement that one specialist's crash does not discard other verified outputs in a returns-and-billing assistant.
Question 255
Before expanding a legacy service decomposition, the owner must demonstrate that a repeatable code-review procedure is available as a named workflow, while also demonstrating that a team compares two candidate patches against the same baseline. Which design provides both controls?
- retype the entire procedure in every conversation; and choose whichever patch has the more persuasive natural-language summary
- create a documented reusable skill in SKILL.md; and evaluate alternatives using the same tests and scoped diffs
- implement only create a documented reusable skill in SKILL.md; make no corresponding change for the second requirement
- retype the entire procedure in every conversation; and evaluate alternatives using the same tests and scoped diffs
- create a documented reusable skill in SKILL.md; and choose whichever patch has the more persuasive natural-language summary
Explanation
Correct Answer
B:In a legacy service decomposition, skills package instructions and supporting resources for invocation across similar tasks; alongside this, consistent acceptance evidence reveals which candidate improves the relevant behavior, satisfying the distinct requirements that a repeatable code-review procedure is available as a named workflow and that a team compares two candidate patches against the same baseline.
Incorrect Answers
A:In a legacy service decomposition, manual repetition produces drift and loses shared revisions and rhetorical fluency does not establish code correctness; the design would fail both conditions: a repeatable code-review procedure is available as a named workflow and a team compares two candidate patches against the same baseline.
C:In a legacy service decomposition, skills package instructions and supporting resources for invocation across similar tasks, but the independent mechanism for the other criterion is absent: consistent acceptance evidence reveals which candidate improves the relevant behavior; as written, the design does not ensure that a team compares two candidate patches against the same baseline.
D:In a legacy service decomposition, consistent acceptance evidence reveals which candidate improves the relevant behavior, but manual repetition produces drift and loses shared revisions; therefore the separate requirement that a repeatable code-review procedure is available as a named workflow would remain unsatisfied.
E:In a legacy service decomposition, skills package instructions and supporting resources for invocation across similar tasks, but rhetorical fluency does not establish code correctness; therefore the separate requirement that a team compares two candidate patches against the same baseline would remain unsatisfied.
Question 256
In a dependency upgrade initiative, the immediate design requirement is that tool-call logging does not modify a successful tool result. Which change most directly establishes that behavior?
- rewrite every tool result as a free-form paraphrase
- use a PostToolUse processing hook to standardize the returned data
- use an observation-only hook for telemetry when rewriting is unnecessary
- record the tool name, permitted inputs, outcome, and task identifier in a hook
Explanation
Correct Answer
C:For a dependency upgrade initiative, separating instrumentation from mutation reduces the risk of corrupting evidence; this directly establishes that tool-call logging does not modify a successful tool result instead of relying on an unrelated workflow control.
Incorrect Answers
A:In a dependency upgrade initiative, summaries can discard fields that subsequent steps require; as a result, the stated requirement that tool-call logging does not modify a successful tool result would still not be met.
B:Although post-execution interception can clean result fields and attach useful status without changing the model's tool selection, that only supports the distinct goal that tool output is normalized before it enters the agent context, not the requirement that tool-call logging does not modify a successful tool result in a dependency upgrade initiative.
D:Although runtime instrumentation observes actual proposed or completed tool activity, that only supports the distinct goal that every high-impact tool invocation produces an audit event, not the requirement that tool-call logging does not modify a successful tool result in a dependency upgrade initiative.
Question 257
While preparing a static analysis automation for deployment, engineers must ensure that multiple draft branches are merged without contradictory statements; they must also ensure that few-shot material does not contain contradictory answer labels. Which combination best satisfies those requirements?
- create a reconciliation stage that checks citations and resolves overlaps; and keep historical examples even after the labeling policy changes
- concatenate every agent's conclusion into the final report; and keep historical examples even after the labeling policy changes
- create a reconciliation stage that checks citations and resolves overlaps; and audit examples against the current decision rubric before use
- concatenate every agent's conclusion into the final report; and audit examples against the current decision rubric before use
Explanation
Correct Answer
C:In a static analysis automation, synthesis must select mutually consistent claims with defensible evidence; alongside this, consistent labels reinforce the intended criteria rather than training ambiguity into the prompt, satisfying the distinct requirements that multiple draft branches are merged without contradictory statements and that few-shot material does not contain contradictory answer labels.
Incorrect Answers
A:In a static analysis automation, synthesis must select mutually consistent claims with defensible evidence, but stale demonstrations can contradict the updated standard; therefore the separate requirement that few-shot material does not contain contradictory answer labels would remain unsatisfied.
B:In a static analysis automation, raw merger preserves disagreements and duplicated statements and stale demonstrations can contradict the updated standard; the design would fail both conditions: multiple draft branches are merged without contradictory statements and few-shot material does not contain contradictory answer labels.
D:In a static analysis automation, consistent labels reinforce the intended criteria rather than training ambiguity into the prompt, but raw merger preserves disagreements and duplicated statements; therefore the separate requirement that multiple draft branches are merged without contradictory statements would remain unsatisfied.
Question 258
An audit of a test failure triage bot asks how to make sure that an alternate implementation is explored without rewriting the original branch. Which implementation should be selected?
- resume the stored session by its identifier
- initialize a fresh session with a verified structured summary
- continue changing the original session as though it were an isolated experiment
- fork the existing session into a separate line of exploration
Explanation
Correct Answer
D:For a test failure triage bot, a fork supports competing paths while preserving the original session history; this directly establishes that an alternate implementation is explored without rewriting the original branch instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although session resumption retains the recorded conversation and avoids rebuilding the entire task from scratch, that only supports the distinct goal that a developer returns to an interrupted session with prior reasoning, not the requirement that an alternate implementation is explored without rewriting the original branch in a test failure triage bot.
B:Although a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, that only supports the distinct goal that a new agent gets only durable context from a completed job, not the requirement that an alternate implementation is explored without rewriting the original branch in a test failure triage bot.
C:In a test failure triage bot, the experiment then shares and alters the active thread's direction; as a result, the stated requirement that an alternate implementation is explored without rewriting the original branch would still not be met.
Question 259
An audit of an order-cancellation service asks how to make sure that a failed high-stakes step prevents a false final success signal. Which implementation should be selected?
- return a typed failure status with its origin to the coordinator
- apply a bounded backoff only to classified retryable errors
- enforce required-stage completion before publishing a success status
- ignore errors after the first successful agent completion
Explanation
Correct Answer
C:For an order-cancellation service, a final gate must account for every mandatory stage rather than aggregate optimistic text; this directly establishes that a failed high-stakes step prevents a false final success signal instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although an operational error must remain distinguishable from a valid empty result, that only supports the distinct goal that a failed retrieval agent does not masquerade as having found no matches, not the requirement that a failed high-stakes step prevents a false final success signal in an order-cancellation service.
B:Although transient failures can heal without re-running permanently invalid requests, that only supports the distinct goal that a transient upstream outage is retried safely, not the requirement that a failed high-stakes step prevents a false final success signal in an order-cancellation service.
D:In an order-cancellation service, later failures can invalidate the claimed result; as a result, the stated requirement that a failed high-stakes step prevents a false final success signal would still not be met.
Question 260
For a service dependency exploration tool, acceptance depends on demonstrating that test-specific naming conventions run only when touching test files. Which approach is the strongest fit?
- keep project-wide security guidance in shared instructions rather than a narrow path glob
- add a .claude/rules file with paths matching the API subtree
- create separate path-specific rule files for each package
- use a test-file glob in the rules frontmatter
- apply the same test naming rule to every source file
Explanation
Correct Answer
D:For a service dependency exploration tool, glob matching limits enforcement guidance to the intended file families; this directly establishes that test-specific naming conventions run only when touching test files instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although cross-cutting obligations should not disappear when an agent changes directories, that only supports the distinct goal that a common security rule remains active across the project, not the requirement that test-specific naming conventions run only when touching test files in a service dependency exploration tool.
B:Although path-scoped rules load when the target context matches, keeping unrelated tasks clean, that only supports the distinct goal that API conventions apply only to source files under an API directory, not the requirement that test-specific naming conventions run only when touching test files in a service dependency exploration tool.
C:Although scoped conventions avoid contradictory patterns between codebases sharing a monorepo, that only supports the distinct goal that two nested packages follow distinct framework conventions, not the requirement that test-specific naming conventions run only when touching test files in a service dependency exploration tool.
E:In a service dependency exploration tool, production files and configuration do not share the test naming context; as a result, the stated requirement that test-specific naming conventions run only when touching test files would still not be met.