Question 790
Before expanding a nightly code quality job, the owner must demonstrate that a partially successful multi-agent job reports its limitations, while also demonstrating that multiple draft branches are merged without contradictory statements. Which design provides both controls?
- mark the whole request successful when any one branch returns data; and concatenate every agent's conclusion into the final report
- mark the whole request successful when any one branch returns data; and create a reconciliation stage that checks citations and resolves overlaps
- aggregate per-agent success and incomplete-state metadata; and concatenate every agent's conclusion into the final report
- aggregate per-agent success and incomplete-state metadata; and create a reconciliation stage that checks citations and resolves overlaps
Explanation
Correct Answer
D:In a nightly code quality job, partial status lets the coordinator qualify conclusions and retry missing branches; alongside this, synthesis must select mutually consistent claims with defensible evidence, satisfying the distinct requirements that a partially successful multi-agent job reports its limitations and that multiple draft branches are merged without contradictory statements.
Incorrect Answers
A:In a nightly code quality job, some required evidence may still be missing and raw merger preserves disagreements and duplicated statements; the design would fail both conditions: a partially successful multi-agent job reports its limitations and multiple draft branches are merged without contradictory statements.
B:In a nightly code quality job, synthesis must select mutually consistent claims with defensible evidence, 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.
C:In a nightly code quality job, partial status lets the coordinator qualify conclusions and retry missing branches, 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 791
A team operating a test failure triage bot wants to establish two separate behaviors: the CI parser receives predictable machine-readable Claude output; in addition, test-specific naming conventions run only when touching test files. Which plan implements both?
- request the CLI JSON output format and parse its documented structure; and use a test-file glob in the rules frontmatter
- scrape a human-oriented terminal transcript with regular expressions; and use a test-file glob in the rules frontmatter
- scrape a human-oriented terminal transcript with regular expressions; and apply the same test naming rule to every source file
- request the CLI JSON output format and parse its documented structure; and apply the same test naming rule to every source file
Explanation
Correct Answer
A:In a test failure triage bot, machine-readable envelopes avoid brittle extraction from colored console prose; alongside this, glob matching limits enforcement guidance to the intended file families, satisfying the distinct requirements that the CI parser receives predictable machine-readable Claude output and that test-specific naming conventions run only when touching test files.
Incorrect Answers
B:In a test failure triage bot, glob matching limits enforcement guidance to the intended file families, but presentation formatting can change and break the parser; therefore the separate requirement that the CI parser receives predictable machine-readable Claude output would remain unsatisfied.
C:In a test failure triage bot, presentation formatting can change and break the parser and production files and configuration do not share the test naming context; the design would fail both conditions: the CI parser receives predictable machine-readable Claude output and test-specific naming conventions run only when touching test files.
D:In a test failure triage bot, machine-readable envelopes avoid brittle extraction from colored console prose, but production files and configuration do not share the test naming context; therefore the separate requirement that test-specific naming conventions run only when touching test files would remain unsatisfied.
Question 792
An incident postmortem for a customs paperwork processor requires controls so that a missing value is represented without fabricating a string and that a large batch shares a consistent evaluation rubric. Which paired remedy covers both failure modes?
- allow null in the field schema and define its semantics; and change the classification criteria mid-batch without version tracking
- force the model to populate every unknown value with a guess; and change the classification criteria mid-batch without version tracking
- allow null in the field schema and define its semantics; and freeze the prompt version and schema for the submission set
- force the model to populate every unknown value with a guess; and freeze the prompt version and schema for the submission set
Explanation
Correct Answer
C:In a customs paperwork processor, explicit nullable types distinguish genuine absence from empty or invented data; alongside this, versioned common instructions make independently processed records comparable, satisfying the distinct requirements that a missing value is represented without fabricating a string and that a large batch shares a consistent evaluation rubric.
Incorrect Answers
A:In a customs paperwork processor, explicit nullable types distinguish genuine absence from empty or invented data, but mixed rubrics undermine consistent downstream aggregation; therefore the separate requirement that a large batch shares a consistent evaluation rubric would remain unsatisfied.
B:In a customs paperwork processor, fabricated values preserve schema appearance but destroy factual accuracy and mixed rubrics undermine consistent downstream aggregation; the design would fail both conditions: a missing value is represented without fabricating a string and a large batch shares a consistent evaluation rubric.
D:In a customs paperwork processor, versioned common instructions make independently processed records comparable, but fabricated values preserve schema appearance but destroy factual accuracy; therefore the separate requirement that a missing value is represented without fabricating a string would remain unsatisfied.
Question 793
In a repository release validation process, the engineering team must guarantee that untrusted project MCP definitions receive approval in interactive Claude Code sessions. What is the most appropriate control?
- automatically approve every MCP definition found in a cloned repository
- review and approve project-scoped server configuration before connecting interactively
- commit a reviewed project .mcp.json without credentials
- verify server connection, transport, and exposed tool availability
Explanation
Correct Answer
B:For a repository release validation process, interactive project trust checks limit execution of unfamiliar server commands and endpoints; this directly establishes that untrusted project MCP definitions receive approval in interactive Claude Code sessions instead of relying on an unrelated workflow control.
Incorrect Answers
A:In a repository release validation process, repository content can include unexpected executable commands and unattended sessions require explicit policy controls; as a result, the stated requirement that untrusted project MCP definitions receive approval in interactive Claude Code sessions would still not be met.
C:Although project-scoped configuration can be distributed with the repository while keeping secrets external, that only supports the distinct goal that a team shares a repository-specific MCP server configuration, not the requirement that untrusted project MCP definitions receive approval in interactive Claude Code sessions in a repository release validation process.
D:Although tool discovery depends on a live configured integration, not just the prompt wording, that only supports the distinct goal that a missing MCP capability is diagnosed before changing prompts, not the requirement that untrusted project MCP definitions receive approval in interactive Claude Code sessions in a repository release validation process.
Question 794
The architect for a legacy service decomposition needs to ensure that a coding agent inspects a known source file without changing it. What should the team implement?
- use Write for file creation
- use Bash with an approved test command
- use Read on the identified file
- run arbitrary shell commands to modify the file during inspection
Explanation
Correct Answer
C:For a legacy service decomposition, file reading provides exact content for analysis without executing the project; this directly establishes that a coding agent inspects a known source file without changing it instead of relying on an unrelated workflow control.
Incorrect Answers
A:Although writing a new artifact is appropriate when no existing target needs surgical modification, that only supports the distinct goal that a new source file is created from supplied content, not the requirement that a coding agent inspects a known source file without changing it in a legacy service decomposition.
B:Although the shell can run build tools and return execution feedback that Read cannot supply, that only supports the distinct goal that the agent executes tests and examines their exit status, not the requirement that a coding agent inspects a known source file without changing it in a legacy service decomposition.
D:In a legacy service decomposition, mutation is unnecessary for a read-only code review; as a result, the stated requirement that a coding agent inspects a known source file without changing it would still not be met.
Question 795
In an automated CI review service, the acceptance criteria require that path-scoped rules are loaded for all intended source directories and that a team compares two candidate patches against the same baseline. Which paired implementation meets both?
- add more prose telling the model to remember the missing rule; and evaluate alternatives using the same tests and scoped diffs
- update the rule's paths glob to include the actual target paths; and evaluate alternatives using the same tests and scoped diffs
- add more prose telling the model to remember the missing rule; and choose whichever patch has the more persuasive natural-language summary
- update the rule's paths glob to include the actual target paths; and choose whichever patch has the more persuasive natural-language summary
Explanation
Correct Answer
B:In an automated CI review service, correct glob coverage determines whether conditional guidance is in context; alongside this, consistent acceptance evidence reveals which candidate improves the relevant behavior, satisfying the distinct requirements that path-scoped rules are loaded for all intended source directories and that a team compares two candidate patches against the same baseline.
Incorrect Answers
A:In an automated CI review service, consistent acceptance evidence reveals which candidate improves the relevant behavior, but instructions outside the matched scope still will not be loaded; therefore the separate requirement that path-scoped rules are loaded for all intended source directories would remain unsatisfied.
C:In an automated CI review service, instructions outside the matched scope still will not be loaded and rhetorical fluency does not establish code correctness; the design would fail both conditions: path-scoped rules are loaded for all intended source directories and a team compares two candidate patches against the same baseline.
D:In an automated CI review service, correct glob coverage determines whether conditional guidance is in context, 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 796
An architecture review of a static analysis automation finds two missing guarantees: test-specific naming conventions run only when touching test files; a coding agent inspects a known source file without changing it. What two-part change closes both gaps?
- apply the same test naming rule to every source file; and use Read on the identified file
- use a test-file glob in the rules frontmatter; and use Read on the identified file
- apply the same test naming rule to every source file; and run arbitrary shell commands to modify the file during inspection
- use a test-file glob in the rules frontmatter; and run arbitrary shell commands to modify the file during inspection
Explanation
Correct Answer
B:In a static analysis automation, glob matching limits enforcement guidance to the intended file families; alongside this, file reading provides exact content for analysis without executing the project, satisfying the distinct requirements that test-specific naming conventions run only when touching test files and that a coding agent inspects a known source file without changing it.
Incorrect Answers
A:In a static analysis automation, file reading provides exact content for analysis without executing the project, but production files and configuration do not share the test naming context; therefore the separate requirement that test-specific naming conventions run only when touching test files would remain unsatisfied.
C:In a static analysis automation, production files and configuration do not share the test naming context and mutation is unnecessary for a read-only code review; the design would fail both conditions: test-specific naming conventions run only when touching test files and a coding agent inspects a known source file without changing it.
D:In a static analysis automation, glob matching limits enforcement guidance to the intended file families, but mutation is unnecessary for a read-only code review; therefore the separate requirement that a coding agent inspects a known source file without changing it would remain unsatisfied.
Question 797
The release gate for a research PDF metadata pipeline requires that tool responses are associated with the exact invocations that produced them; it also requires that only one approved write tool is callable in a sensitive stage. Which TWO actions meet the specified checks? Choose TWO.
- let the model select from a broad global list of tools
- return tool_result blocks using the original tool_use_id values
- restrict the stage's allowed tool set and verify permissions in the executor
- return tool results with newly invented identifiers
Explanation
Correct Answers
B:For a research PDF metadata pipeline, correlation identifiers bind asynchronous or parallel results to the right requests, which directly establishes that tool responses are associated with the exact invocations that produced them; the separate requirement that only one approved write tool is callable in a sensitive stage is handled by a different action.
C:For a research PDF metadata pipeline, capability scoping narrows possible side effects before model selection, which directly establishes that only one approved write tool is callable in a sensitive stage; the separate requirement that tool responses are associated with the exact invocations that produced them is handled by a different action.
Incorrect Answers
A:For a research PDF metadata pipeline, excess capabilities create avoidable routing and authorization risk, so this option cannot establish that only one approved write tool is callable in a sensitive stage; correctly addressing tool responses are associated with the exact invocations that produced them elsewhere does not repair that deficiency.
D:For a research PDF metadata pipeline, the model cannot reliably associate a result with an outstanding call, so this option cannot establish that tool responses are associated with the exact invocations that produced them; correctly addressing only one approved write tool is callable in a sensitive stage elsewhere does not repair that deficiency.
Question 798
Production readiness for an internal developer coding workflow depends on ensuring that the report is not drafted before evidence is checked and that a team shares a repository-specific MCP server configuration. Select the most appropriate combined approach.
- start drafting at the same time as the source search and assume success; and commit a reviewed project .mcp.json without credentials
- implement only commit a reviewed project .mcp.json without credentials; make no corresponding change for the first requirement
- start drafting at the same time as the source search and assume success; and configure each contributor's personal MCP registry manually
- place evidence validation before the drafting stage; and configure each contributor's personal MCP registry manually
- place evidence validation before the drafting stage; and commit a reviewed project .mcp.json without credentials
Explanation
Correct Answer
E:In an internal developer coding workflow, a dependent stage must receive validated inputs to avoid propagating unsupported conclusions; alongside this, project-scoped configuration can be distributed with the repository while keeping secrets external, satisfying the distinct requirements that the report is not drafted before evidence is checked and that a team shares a repository-specific MCP server configuration.
Incorrect Answers
A:In an internal developer coding workflow, project-scoped configuration can be distributed with the repository while keeping secrets external, but the writer may treat unverified or absent evidence as real; therefore the separate requirement that the report is not drafted before evidence is checked would remain unsatisfied.
B:In an internal developer coding workflow, project-scoped configuration can be distributed with the repository while keeping secrets external, but the independent mechanism for the other criterion is absent: a dependent stage must receive validated inputs to avoid propagating unsupported conclusions; as written, the design does not ensure that the report is not drafted before evidence is checked.
C:In an internal developer coding workflow, the writer may treat unverified or absent evidence as real and local personal settings do not create a reproducible team project setup; the design would fail both conditions: the report is not drafted before evidence is checked and a team shares a repository-specific MCP server configuration.
D:In an internal developer coding workflow, a dependent stage must receive validated inputs to avoid propagating unsupported conclusions, but local personal settings do not create a reproducible team project setup; therefore the separate requirement that a team shares a repository-specific MCP server configuration would remain unsatisfied.
Question 799
An architecture review of a backend API maintenance team finds two missing guarantees: documentation-only conventions do not dilute code-editing tasks; conflicting guidance from different files is detected before rollout. What two-part change closes both gaps?
- scope documentation style rules to matching documentation paths; and assume the model will infer which contradictory rule to follow
- place all documentation writing rules in a global user file; and audit overlapping CLAUDE.md files and resolve instruction contradictions
- scope documentation style rules to matching documentation paths; and audit overlapping CLAUDE.md files and resolve instruction contradictions
- place all documentation writing rules in a global user file; and assume the model will infer which contradictory rule to follow
Explanation
Correct Answer
C:In a backend API maintenance team, conditional loading keeps instruction context relevant to the file being worked on; alongside this, clear ownership and scope prevent two directions from competing in the same coding task, satisfying the distinct requirements that documentation-only conventions do not dilute code-editing tasks and that conflicting guidance from different files is detected before rollout.
Incorrect Answers
A:In a backend API maintenance team, conditional loading keeps instruction context relevant to the file being worked on, but unresolved conflicts create inconsistent output across directories; therefore the separate requirement that conflicting guidance from different files is detected before rollout would remain unsatisfied.
B:In a backend API maintenance team, clear ownership and scope prevent two directions from competing in the same coding task, but those conventions will follow unrelated code tasks; therefore the separate requirement that documentation-only conventions do not dilute code-editing tasks would remain unsatisfied.
D:In a backend API maintenance team, those conventions will follow unrelated code tasks and unresolved conflicts create inconsistent output across directories; the design would fail both conditions: documentation-only conventions do not dilute code-editing tasks and conflicting guidance from different files is detected before rollout.
Question 800
While preparing a monorepo feature modernization project for deployment, engineers must ensure that documentation-only conventions do not dilute code-editing tasks; they must also ensure that a coding assistant first identifies relevant files in a large repository. Which combination best satisfies those requirements?
- implement only scope documentation style rules to matching documentation paths; make no corresponding change for the second requirement
- scope documentation style rules to matching documentation paths; and discover paths using Glob before reading contents
- place all documentation writing rules in a global user file; and read the entire repository recursively into one prompt
- place all documentation writing rules in a global user file; and discover paths using Glob before reading contents
- scope documentation style rules to matching documentation paths; and read the entire repository recursively into one prompt
Explanation
Correct Answer
B:In a monorepo feature modernization project, conditional loading keeps instruction context relevant to the file being worked on; alongside this, staged path discovery prevents unrelated modules from saturating the context, satisfying the distinct requirements that documentation-only conventions do not dilute code-editing tasks and that a coding assistant first identifies relevant files in a large repository.
Incorrect Answers
A:In a monorepo feature modernization project, conditional loading keeps instruction context relevant to the file being worked on, but the independent mechanism for the other criterion is absent: staged path discovery prevents unrelated modules from saturating the context; as written, the design does not ensure that a coding assistant first identifies relevant files in a large repository.
C:In a monorepo feature modernization project, those conventions will follow unrelated code tasks and large context dumps bury important code among irrelevant files; the design would fail both conditions: documentation-only conventions do not dilute code-editing tasks and a coding assistant first identifies relevant files in a large repository.
D:In a monorepo feature modernization project, staged path discovery prevents unrelated modules from saturating the context, but those conventions will follow unrelated code tasks; therefore the separate requirement that documentation-only conventions do not dilute code-editing tasks would remain unsatisfied.
E:In a monorepo feature modernization project, conditional loading keeps instruction context relevant to the file being worked on, but large context dumps bury important code among irrelevant files; therefore the separate requirement that a coding assistant first identifies relevant files in a large repository would remain unsatisfied.