Question 640
Production readiness for a developer codebase exploration assistant depends on ensuring that two nested packages follow distinct framework conventions and that only a nested service uses specialized implementation rules. Select the most appropriate combined approach.
- write one ambiguous instruction for both packages; and place a dedicated CLAUDE.md in the relevant directory
- write one ambiguous instruction for both packages; and put all service-only details in the repository root instruction file
- create separate path-specific rule files for each package; and put all service-only details in the repository root instruction file
- create separate path-specific rule files for each package; and place a dedicated CLAUDE.md in the relevant directory
Explanation
Correct Answer
D:In a developer codebase exploration assistant, scoped conventions avoid contradictory patterns between codebases sharing a monorepo; alongside this, directory-specific context can refine instructions for work under that subtree, satisfying the distinct requirements that two nested packages follow distinct framework conventions and that only a nested service uses specialized implementation rules.
Incorrect Answers
A:In a developer codebase exploration assistant, directory-specific context can refine instructions for work under that subtree, but the model must guess which framework convention applies; therefore the separate requirement that two nested packages follow distinct framework conventions would remain unsatisfied.
B:In a developer codebase exploration assistant, the model must guess which framework convention applies and globalizing narrow rules adds irrelevant instructions to unrelated work; the design would fail both conditions: two nested packages follow distinct framework conventions and only a nested service uses specialized implementation rules.
C:In a developer codebase exploration assistant, scoped conventions avoid contradictory patterns between codebases sharing a monorepo, 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.
Question 641
The architect for a pull-request review pipeline needs to ensure that the reviewer does not simply echo the generator's confidence. What should the team implement?
- give the reviewer the source and rubric, not only the draft's self-rating
- provide the generator's score as the sole review criterion
- combine independent review with schema and business-rule validation
- separate factual, structural, and policy review passes
Explanation
Correct Answer
A:For a pull-request review pipeline, independent evidence lets a critic challenge unsupported assertions; this directly establishes that the reviewer does not simply echo the generator's confidence instead of relying on an unrelated workflow control.
Incorrect Answers
B:In a pull-request review pipeline, anchoring on a self-assigned grade hides actual defects; as a result, the stated requirement that the reviewer does not simply echo the generator's confidence would still not be met.
C:Although a critique may improve quality but cannot enforce machine-testable invariants by itself, that only supports the distinct goal that a high-risk result passes deterministic checks in addition to model critique, not the requirement that the reviewer does not simply echo the generator's confidence in a pull-request review pipeline.
D:Although specialized criteria can detect different failure modes without one overloaded evaluation instruction, that only supports the distinct goal that a complex document receives focused quality checks, not the requirement that the reviewer does not simply echo the generator's confidence in a pull-request review pipeline.
Question 642
In a technical review of a build verification pipeline, the architect must address the following constraints together: reviewer changes remain auditable; a developer returns to an interrupted session with prior reasoning. Which change set is most defensible?
- overwrite an automated answer without preserving the reviewer decision; and resume the stored session by its identifier
- overwrite an automated answer without preserving the reviewer decision; and start an unrelated new session and assume it knows past actions
- log the reviewer identity, decision, justification, and artifact version; and start an unrelated new session and assume it knows past actions
- log the reviewer identity, decision, justification, and artifact version; and resume the stored session by its identifier
Explanation
Correct Answer
D:In a build verification pipeline, a versioned approval trail supports diagnosis and later governance reviews; alongside this, session resumption retains the recorded conversation and avoids rebuilding the entire task from scratch, satisfying the distinct requirements that reviewer changes remain auditable and that a developer returns to an interrupted session with prior reasoning.
Incorrect Answers
A:In a build verification pipeline, session resumption retains the recorded conversation and avoids rebuilding the entire task from scratch, but the final state loses the reason it changed; therefore the separate requirement that reviewer changes remain auditable would remain unsatisfied.
B:In a build verification pipeline, the final state loses the reason it changed and a fresh context lacks the prior interaction unless the facts are deliberately supplied; the design would fail both conditions: reviewer changes remain auditable and a developer returns to an interrupted session with prior reasoning.
C:In a build verification pipeline, a versioned approval trail supports diagnosis and later governance reviews, but a fresh context lacks the prior interaction unless the facts are deliberately supplied; therefore the separate requirement that a developer returns to an interrupted session with prior reasoning would remain unsatisfied.
Question 643
An architecture review of a claims form processing assistant finds two missing guarantees: tool responses are associated with the exact invocations that produced them; one agent's draft is reviewed independently for errors. What two-part change closes both gaps?
- return tool results with newly invented identifiers; and ask the draft generator to declare its own work perfect
- return tool_result blocks using the original tool_use_id values; and use a separate review pass with explicit criteria
- return tool_result blocks using the original tool_use_id values; and ask the draft generator to declare its own work perfect
- implement only return tool_result blocks using the original tool_use_id values; make no corresponding change for the second requirement
- return tool results with newly invented identifiers; and use a separate review pass with explicit criteria
Explanation
Correct Answer
B:In a claims form processing assistant, correlation identifiers bind asynchronous or parallel results to the right requests; alongside this, independent criticism exposes omissions that unstructured self-praise can miss, satisfying the distinct requirements that tool responses are associated with the exact invocations that produced them and that one agent's draft is reviewed independently for errors.
Incorrect Answers
A:In a claims form processing assistant, the model cannot reliably associate a result with an outstanding call and self-assessment without a second criterion-based pass is weak evidence; the design would fail both conditions: tool responses are associated with the exact invocations that produced them and one agent's draft is reviewed independently for errors.
C:In a claims form processing assistant, correlation identifiers bind asynchronous or parallel results to the right requests, but self-assessment without a second criterion-based pass is weak evidence; therefore the separate requirement that one agent's draft is reviewed independently for errors would remain unsatisfied.
D:In a claims form processing assistant, correlation identifiers bind asynchronous or parallel results to the right requests, but the independent mechanism for the other criterion is absent: independent criticism exposes omissions that unstructured self-praise can miss; as written, the design does not ensure that one agent's draft is reviewed independently for errors.
E:In a claims form processing assistant, independent criticism exposes omissions that unstructured self-praise can miss, but the model cannot reliably associate a result with an outstanding call; therefore the separate requirement that tool responses are associated with the exact invocations that produced them would remain unsatisfied.
Question 644
In a supplier invoice extractor, the immediate design requirement is that a user-facing chat answer returns with low latency. Which change most directly establishes that behavior?
- identify failed records and resubmit only safe retry candidates
- submit the one message to an offline batch and block for completion
- use synchronous Messages requests for the interactive path
- freeze the prompt version and schema for the submission set
Explanation
Correct Answer
C:For a supplier invoice extractor, the caller needs an immediate result rather than an asynchronously retrieved batch output; this directly establishes that a user-facing chat answer returns with low latency instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although selective retry avoids paying again for already successful items, that only supports the distinct goal that a partially failed batch is repaired efficiently, not the requirement that a user-facing chat answer returns with low latency in a supplier invoice extractor.
B:In a supplier invoice extractor, batch scheduling is a poor fit for a live conversational deadline; as a result, the stated requirement that a user-facing chat answer returns with low latency would still not be met.
D:Although versioned common instructions make independently processed records comparable, that only supports the distinct goal that a large batch shares a consistent evaluation rubric, not the requirement that a user-facing chat answer returns with low latency in a supplier invoice extractor.
Question 645
An audit of an after-sales issue resolver identifies two unmet requirements: source identity survives multi-agent research handoffs and reviewer changes remain auditable. Select TWO actions that remedy those particular deficiencies.
- strip all citation fields before sending the writer its inputs
- carry citation identifiers and retrieval context through synthesis
- log the reviewer identity, decision, justification, and artifact version
- overwrite an automated answer without preserving the reviewer decision
Explanation
Correct Answers
B:For an after-sales issue resolver, provenance metadata must remain attached when intermediate summaries are merged, which directly establishes that source identity survives multi-agent research handoffs; the separate requirement that reviewer changes remain auditable is handled by a different action.
C:For an after-sales issue resolver, a versioned approval trail supports diagnosis and later governance reviews, which directly establishes that reviewer changes remain auditable; the separate requirement that source identity survives multi-agent research handoffs is handled by a different action.
Incorrect Answers
A:For an after-sales issue resolver, the writer cannot reliably reconstruct which source supports each conclusion, so this option cannot establish that source identity survives multi-agent research handoffs; correctly addressing reviewer changes remain auditable elsewhere does not repair that deficiency.
D:For an after-sales issue resolver, the final state loses the reason it changed, so this option cannot establish that reviewer changes remain auditable; correctly addressing source identity survives multi-agent research handoffs elsewhere does not repair that deficiency.
Question 646
An audit of a static analysis automation asks how to make sure that a shared skill can take a supplied target name or file path. Which implementation should be selected?
- configure the skill to run in an isolated forked context where supported
- define how the skill accepts and uses invocation arguments
- copy a separate static instruction file for every target path
- declare allowed-tools for the skill and enforce executor permissions
Explanation
Correct Answer
B:For a static analysis automation, parameterized workflows apply one reviewed procedure to different resources without hardcoding targets; this directly establishes that a shared skill can take a supplied target name or file path instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although a fork isolates exploratory work and returns a concise result to its caller, that only supports the distinct goal that a delegated skill should not fill the caller's active context, not the requirement that a shared skill can take a supplied target name or file path in a static analysis automation.
C:In a static analysis automation, duplicated procedures are costly to maintain and can diverge; as a result, the stated requirement that a shared skill can take a supplied target name or file path would still not be met.
D:Although tool restrictions narrow the agent's operational capability while the skill runs, that only supports the distinct goal that a high-risk workflow only invokes specifically approved capabilities, not the requirement that a shared skill can take a supplied target name or file path in a static analysis automation.
Question 647
An audit of a typed API generator project identifies two unmet requirements: API conventions apply only to source files under an API directory and a patch that fails regression tests is diagnosed and corrected. Select TWO actions that remedy those particular deficiencies.
- inspect failure evidence and revise the smallest relevant change
- add a .claude/rules file with paths matching the API subtree
- rewrite large unrelated modules before re-running tests
- put API-specific formatting rules in always-on project guidance
Explanation
Correct Answers
A:For a typed API generator project, test-driven feedback pinpoints a specific unmet behavior for the next iteration, which directly establishes that a patch that fails regression tests is diagnosed and corrected; the separate requirement that API conventions apply only to source files under an API directory is handled by a different action.
B:For a typed API generator project, path-scoped rules load when the target context matches, keeping unrelated tasks clean, which directly establishes that API conventions apply only to source files under an API directory; the separate requirement that a patch that fails regression tests is diagnosed and corrected is handled by a different action.
Incorrect Answers
C:For a typed API generator project, broad edits create new regression surfaces while the cause remains unclear, so this option cannot establish that a patch that fails regression tests is diagnosed and corrected; correctly addressing API conventions apply only to source files under an API directory elsewhere does not repair that deficiency.
D:For a typed API generator project, frontend and documentation tasks then receive irrelevant instructions, so this option cannot establish that API conventions apply only to source files under an API directory; correctly addressing a patch that fails regression tests is diagnosed and corrected elsewhere does not repair that deficiency.
Question 648
When designing a test failure triage bot, the requirement is not satisfied unless untrusted project MCP definitions receive approval in interactive Claude Code sessions and a specialist handoff retains its prerequisites and evidence. Which implementation addresses the two independent conditions?
- review and approve project-scoped server configuration before connecting interactively; and send a structured state packet with completed checks and unresolved decisions
- automatically approve every MCP definition found in a cloned repository; and handoff only a conversational sentence saying the stage is finished
- review and approve project-scoped server configuration before connecting interactively; and handoff only a conversational sentence saying the stage is finished
- automatically approve every MCP definition found in a cloned repository; and send a structured state packet with completed checks and unresolved decisions
- implement only review and approve project-scoped server configuration before connecting interactively; make no corresponding change for the second requirement
Explanation
Correct Answer
A:In a test failure triage bot, interactive project trust checks limit execution of unfamiliar server commands and endpoints; alongside this, a typed transition preserves obligations and facts between workflow stages, satisfying the distinct requirements that untrusted project MCP definitions receive approval in interactive Claude Code sessions and that a specialist handoff retains its prerequisites and evidence.
Incorrect Answers
B:In a test failure triage bot, repository content can include unexpected executable commands and unattended sessions require explicit policy controls and the receiving stage cannot audit what actually passed; the design would fail both conditions: untrusted project MCP definitions receive approval in interactive Claude Code sessions and a specialist handoff retains its prerequisites and evidence.
C:In a test failure triage bot, interactive project trust checks limit execution of unfamiliar server commands and endpoints, but the receiving stage cannot audit what actually passed; therefore the separate requirement that a specialist handoff retains its prerequisites and evidence would remain unsatisfied.
D:In a test failure triage bot, a typed transition preserves obligations and facts between workflow stages, but repository content can include unexpected executable commands and unattended sessions require explicit policy controls; therefore the separate requirement that untrusted project MCP definitions receive approval in interactive Claude Code sessions would remain unsatisfied.
E:In a test failure triage bot, interactive project trust checks limit execution of unfamiliar server commands and endpoints, but the independent mechanism for the other criterion is absent: a typed transition preserves obligations and facts between workflow stages; as written, the design does not ensure that a specialist handoff retains its prerequisites and evidence.
Question 649
For a multi-repository troubleshooting agent, a reviewer identifies two independent obligations: a tool receives a typed and bounded request and the agent executes tests and examines their exit status. Which proposal should be approved?
- accept one unstructured free-text argument for every operation; and inspect the test configuration only with Read and claim tests passed
- define required properties and types in the input schema and validate arguments at the execution boundary; and use Bash with an approved test command
- define required properties and types in the input schema and validate arguments at the execution boundary; and inspect the test configuration only with Read and claim tests passed
- accept one unstructured free-text argument for every operation; and use Bash with an approved test command
Explanation
Correct Answer
B:In a multi-repository troubleshooting agent, input schemas describe legal arguments, while explicit validation prevents unsupported values from reaching tool logic; alongside this, the shell can run build tools and return execution feedback that Read cannot supply, satisfying the distinct requirements that a tool receives a typed and bounded request and that the agent executes tests and examines their exit status.
Incorrect Answers
A:In a multi-repository troubleshooting agent, unconstrained prose leaves parsing and validation errors to ad hoc handler inference and reading configuration does not execute a test suite; the design would fail both conditions: a tool receives a typed and bounded request and the agent executes tests and examines their exit status.
C:In a multi-repository troubleshooting agent, input schemas describe legal arguments, while explicit validation prevents unsupported values from reaching tool logic, but reading configuration does not execute a test suite; therefore the separate requirement that the agent executes tests and examines their exit status would remain unsatisfied.
D:In a multi-repository troubleshooting agent, the shell can run build tools and return execution feedback that Read cannot supply, but unconstrained prose leaves parsing and validation errors to ad hoc handler inference; therefore the separate requirement that a tool receives a typed and bounded request would remain unsatisfied.
Question 650
In a database migration coding project, the engineering team must guarantee that an approved plan is translated into controlled edits and tests. What is the most appropriate control?
- investigate in plan-oriented or read-only mode first
- remain in read-only planning and claim the code was updated
- present ordered changes, risks, and verification steps before switching to execution
- exit the planning stage and perform scoped implementation with verification
Explanation
Correct Answer
D:For a database migration coding project, planning describes intended operations while execution applies and checks them; this directly establishes that an approved plan is translated into controlled edits and tests instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although inspection can establish architecture and change scope without side effects, that only supports the distinct goal that the team obtains a read-only survey of an unfamiliar module, not the requirement that an approved plan is translated into controlled edits and tests in a database migration coding project.
B:In a database migration coding project, a proposal alone does not modify repository state; as a result, the stated requirement that an approved plan is translated into controlled edits and tests would still not be met.
C:Although an explicit review point aligns the agent's work with the authorized scope, that only supports the distinct goal that the implementation plan receives stakeholder sign-off, not the requirement that an approved plan is translated into controlled edits and tests in a database migration coding project.