Question 360
The API responds with a credential-related authorization failure for a deployed worker. What is the most direct implementation choice?
- Correct a malformed request before resubmission
- Refresh authentication on unauthorized calls
- Treat repeated server errors as a dependency outage
- Register a client tool with input_schema
Explanation
Correct Answer
B:The operator checks key validity, workspace scope, and secret injection before retrying; notably, sending the same invalid secret repeatedly will not solve the auth problem.
Incorrect Answers
A:Client-side schema validation fixes the payload and prevents fruitless retries; the requirement instead turns on this behavior: the operator checks key validity, workspace scope, and secret injection before retrying; a network backoff cannot make an invalid request body well formed.
C:A circuit breaker and fallback degrade gracefully while limiting repeated failed traffic; in contrast, the operator checks key validity, workspace scope, and secret injection before retrying, while a longer prompt or higher max_tokens does not restore an unavailable upstream server.
D:Tool definitions describe names, parameters, and types so Claude can propose structured calls; this addresses a separate concern, not the fact that the operator checks key validity, workspace scope, and secret injection before retrying; defining a schema does not grant access to an external system automatically.
Question 361
A downstream service expects a customer risk result with a number, reason code, and source IDs. Which engineering practice is the strongest match?
- Use POST for a Messages generation request
- Use typed deserialization for a structured result
- Validate the outer JSON object schema
- Handle null and missing values distinctly
Explanation
Correct Answer
B:Typed parsing converts validated JSON into an explicit application data contract; the important constraint is that free-form text parsing with ad hoc regular expressions is brittle under wording changes.
Incorrect Answers
A:The endpoint creates a new inference result from a JSON request and is invoked as an HTTP POST, whereas the requirement calls for another behavior: typed parsing converts validated JSON into an explicit application data contract; treating it as a cacheable read-only GET would not express the required request body.
C:Schema checking enforces required keys, types, and nested structures consistently; the requirement instead turns on this behavior: typed parsing converts validated JSON into an explicit application data contract; a parseable JSON string can still violate the endpoint's semantic contract.
D:Type-aware validation preserves nullability and missing-field semantics for downstream logic; this cannot substitute for the behavior that typed parsing converts validated JSON into an explicit application data contract, because coercing every absent property to an empty value can distort business decisions.
Question 362
A coding workflow depends on an installed plugin that may not exist on a teammate's machine. What should the team do at this decision point?
- Manage SDK dependencies through a lockfile
- Declare integration dependencies explicitly
- Remove unused integrations
- Review plugin permissions before activation
Explanation
Correct Answer
B:Configuration and onboarding document required tool integrations and supported versions; the important constraint is that assuming every client has identical external tools makes behavior unpredictable.
Incorrect Answers
A:Locked dependencies produce repeatable runtime behavior from tested package versions, whereas the requirement calls for another behavior: configuration and onboarding document required tool integrations and supported versions; loose version ranges can introduce changes without deliberate evaluation.
C:Decommissioning unneeded capabilities reduces the exposed attack surface and maintenance burden; the requirement instead turns on this behavior: configuration and onboarding document required tool integrations and supported versions; merely hiding a tool from a menu may not revoke its underlying credential.
D:Least-privilege permission review limits what installed integrations can access; this cannot substitute for the behavior that configuration and onboarding document required tool integrations and supported versions, because a friendly plugin description is not a security audit.
Question 363
A user's administrative permission is revoked while an assistant chat remains open. Which design would meet this acceptance criterion?
- Expire stale ephemeral sessions
- Separate tenant-specific conversation state
- Invalidate session privileges after role changes
- Expose a safe retry action after transient faults
Explanation
Correct Answer
C:Authorization checks must reflect current permissions rather than those cached at session creation; its operational boundary is that prior approval of one request does not authorize later actions forever.
Incorrect Answers
A:Time-based cleanup limits unnecessary data retention and reduces exposure; the requirement instead turns on this behavior: authorization checks must reflect current permissions rather than those cached at session creation; persistent global memory is inappropriate for short-lived sensitive tasks.
B:Tenant isolation is enforced in storage queries, tools, and context assembly; this cannot substitute for the behavior that authorization checks must reflect current permissions rather than those cached at session creation, because merely instructing the model not to mix tenants is an inadequate barrier.
D:The UI can offer a bounded retry with clear status rather than silently losing the task; this addresses a separate concern, not the fact that authorization checks must reflect current permissions rather than those cached at session creation; the backend must still prevent duplicated side effects when retrying.
Question 364
A requirements prompt is becoming unwieldy because reviewers mix evidence, constraints, and format rules, then request essay-length answers even for yes/no triage. Which TWO editing changes improve structure and output discipline? Choose TWO.
- Specify a strict response schema
- Provide contrastive edge-case examples
- Avoid unnecessary verbosity constraints
- Use named sections for long complex requirements
- Use explicit delimiters for source passages
Explanation
Correct Answers
C:Output guidance should match the amount of reasoning and explanation the task actually needs; longer responses can add unsupported details rather than increasing precision; in quick triage, output length should follow the actual task rather than a fixed page target.
D:Structured headings make independent instructions easier to distinguish and check, although structure cannot rescue contradictory or factually impossible requirements.
Incorrect Answers
A:Schema constraints and subsequent validation improve consistent downstream parsing; the missing capability is more specific: output guidance should match the amount of reasoning and explanation the task actually needs; they cannot guarantee that the values are factually correct.
B:Distinct positive and near-miss cases teach the actual boundary between labels; by comparison, the intended solution relies on this: output guidance should match the amount of reasoning and explanation the task actually needs; repeating many easy cases offers little information about ambiguous ones.
E:Marking the passage's bounds clarifies which content is data rather than a user command; however, the critical mechanism here is that output guidance should match the amount of reasoning and explanation the task actually needs, and delimiters help interpretation but do not replace tool-level security.
Question 365
Developers repeatedly need the same review checklist and workflow instructions across related tasks. What should be implemented to solve this problem?
- Use a custom slash command for a named recurring action
- Use an interactive session for exploratory editing
- Use hooks for deterministic lifecycle checks
- Use a reusable Skill for repeatable know-how
Explanation
Correct Answer
D:A Skill packages reusable task guidance so the coding agent can apply a consistent procedure; in production, guidance does not grant access to a tool or enforce backend authorization.
Incorrect Answers
A:A named command exposes reusable prompt-driven workflow entry points inside Claude Code; this addresses a separate concern, not the fact that a Skill packages reusable task guidance so the coding agent can apply a consistent procedure; a command definition still depends on the session's tool permissions and context.
B:An interactive coding session supports iterative commands and review as context evolves; here, the controlling capability is that a Skill packages reusable task guidance so the coding agent can apply a consistent procedure, but automating every command without supervision is unnecessary for a human-led investigation.
C:Configured hooks invoke developer-controlled checks at defined event boundaries; the missing capability is more specific: a Skill packages reusable task guidance so the coding agent can apply a consistent procedure; a conversational instruction to perform the check is not equivalent to a guaranteed hook.
Question 366
A multilingual routing workflow confuses adjacent categories and an executive-summary generator imitates the wrong style. It also needs test examples that reflect realistic customer traffic. Which THREE example-design techniques address these issues? Choose THREE.
- Provide contrastive edge-case examples
- Compare revisions on fixed metrics
- Include a counterexample with correction
- Test prompt examples for representativeness
- Give a correct representative example
- Use explicit delimiters for source passages
Explanation
Correct Answers
A:Distinct positive and near-miss cases teach the actual boundary between labels; the important constraint is that repeating many easy cases offers little information about ambiguous ones.
C:Showing an unacceptable output and its corrected form highlights a specific formatting mistake; notably, a negative example without the correct alternative may create confusion; the correction demonstrates summary style rather than solving multilingual routing by itself.
D:Broader cases reveal where examples bias the model toward a narrow pattern; its operational boundary is that more examples do not automatically fix poor dataset coverage.
Incorrect Answers
B:Measured pass rates and error types reveal tradeoffs between candidates; the requirement instead turns on this behavior: distinct positive and near-miss cases teach the actual boundary between labels; choosing solely by stylistic preference can hide data-quality regressions.
E:A compact demonstration clarifies the intended input-to-output mapping; this addresses a separate concern, not the fact that distinct positive and near-miss cases teach the actual boundary between labels; examples should match the required schema and not use private customer records.
F:Marking the passage's bounds clarifies which content is data rather than a user command; here, the controlling capability is that distinct positive and near-miss cases teach the actual boundary between labels, but delimiters help interpretation but do not replace tool-level security.
Question 367
A high-traffic inference client repeatedly opens costly new network connections. Which solution matches the actual constraint?
- Set the requested API version header where required
- Set client-side network timeouts
- Apply backpressure to input queues
- Use connection pooling where supported
Explanation
Correct Answer
D:Reusing connections can reduce handshake overhead and improve request efficiency; the implementation must still recognize that pools still need concurrency caps and safe idle connection management.
Incorrect Answers
A:Version negotiation constrains accepted fields and response behavior for an endpoint; this cannot substitute for the behavior that reusing connections can reduce handshake overhead and improve request efficiency, because omitting required version information or assuming an arbitrary revision can break compatibility.
B:Connect and read deadlines bound network waits and allow controlled failure behavior; in contrast, reusing connections can reduce handshake overhead and improve request efficiency, while token limits describe model output, not HTTP socket lifetime.
C:Backpressure or queue admission control protects worker memory and service availability; this addresses a separate concern, not the fact that reusing connections can reduce handshake overhead and improve request efficiency; unlimited buffering merely postpones overload until the system fails.
Question 368
A new codebase has no agent-facing project notes and contributors need an agreed starting point. What is the most direct implementation choice?
- Use an interactive session for exploratory editing
- Keep secrets outside coding-agent memory files
- Initialize repository guidance deliberately
- Use CLAUDE.md for repository instructions
Explanation
Correct Answer
C:An initialization workflow can help establish and review useful CLAUDE.md guidance for the repository, although generated notes must be checked before being treated as authoritative development policy.
Incorrect Answers
A:An interactive coding session supports iterative commands and review as context evolves; by comparison, the intended solution relies on this: an initialization workflow can help establish and review useful CLAUDE.md guidance for the repository; automating every command without supervision is unnecessary for a human-led investigation.
B:Credentials remain in protected stores or environment controls rather than committed textual guidance; the needed capability is different—an initialization workflow can help establish and review useful CLAUDE.md guidance for the repository—and a shared file can be copied, logged, and inherited by unintended readers.
D:A project instruction file provides contextual guidance when Claude Code works in that repository; however, the critical mechanism here is that an initialization workflow can help establish and review useful CLAUDE.md guidance for the repository, and it is explanatory context rather than a security boundary enforcing tool privileges.
Question 369
A remote server offers actions against private customer records to many different client identities. What is the correct engineering decision?
- Protect remote MCP authentication and authorization
- Use a client-side transport adapter
- Expose an MCP resource for read-oriented context
- Use stdio for a local subprocess integration
Explanation
Correct Answer
A:Credentials and resource-scoped checks ensure each caller sees only permitted tools and records; protocol compatibility alone does not establish who the caller is.
Incorrect Answers
B:Transport abstraction lets the same protocol-level concepts operate over supported connection methods, whereas the requirement calls for another behavior: credentials and resource-scoped checks ensure each caller sees only permitted tools and records; a transport switch does not erase server deployment or security requirements.
C:Resources represent accessible data that a client can retrieve and supply as context; however, the critical mechanism here is that credentials and resource-scoped checks ensure each caller sees only permitted tools and records, and a resource's text cannot authorize additional tool actions by itself.
D:Standard input and output suit tightly coupled local client-server interactions; the requirement instead turns on this behavior: credentials and resource-scoped checks ensure each caller sees only permitted tools and records; the server's standard output must remain protocol-clean instead of mixing human debug prints.
Question 370
A retrieved PDF embeds instructions demanding a secret transfer unrelated to the user's question. Which design would meet this acceptance criterion?
- Label external text as untrusted input
- Attach source IDs to retrieved excerpts
- Use an external source refresh for changing facts
- Track source timestamps or versions
Explanation
Correct Answer
A:Trust-boundary marking prevents source content from being promoted to application authority; the implementation must still recognize that labels should be backed by tool restrictions because prompts can be attacked.
Incorrect Answers
B:Citation metadata lets downstream logic connect statements to original retrieved material; the missing capability is more specific: trust-boundary marking prevents source content from being promoted to application authority; without accurate source mapping, fabricated references can look convincing.
C:Refetching authoritative information avoids treating outdated context as eternally current; by comparison, the intended solution relies on this: trust-boundary marking prevents source content from being promoted to application authority; the model should not invent a change simply because its history is old.
D:Version metadata allows the agent to prefer current evidence and flag historical material; the needed capability is different—trust-boundary marking prevents source content from being promoted to application authority—and timestamp alone does not establish which source is authoritative.