1/119
Looks like no tags are added yet.
A. Allow access to all tools with read permissions globally across the system.
B. Per-role allow-list of exactly the read-knowledge-base and write-draft-queue tools, enforced at the orchestration layer.
C. Allow access to every tool in the catalog and rely on the model to decline tools it should not use.
D. Disable all tools entirely to achieve a minimal permission surface.
B
A. Determine the minimum detectable effect size and the sample size needed for power.
B. Decide whether to promote, reject, or iterate the candidate based on the analysis.
C. Define the hypothesis and the primary success metric for the comparison.
D. Analyze the results against the predefined success metric and significance threshold.
E. Document the recommendation, the trade-offs accepted, and the alternatives considered.
A,C
A. Add unrestricted access to additional tool categories as well, so that Bash is not asymmetrically more permissive than other tools, expanding the attack surface further in the name of consistency.
B. Approve the unrestricted Bash access as written on the grounds that narrowing the rules would add configuration complexity, accepting the full attack surface for all engineers across all projects.
C. Replace unrestricted Bash with narrowly scoped tool patterns that allow only the specific commands the workflows require, and add explicit deny rules for sensitive operations.
D. Disable all permission rules for the enterprise rollout so every command across every project runs without any tool-pattern scoping or explicit deny rules for sensitive operations.
C
A. Present measured p50 and p95 latency baselines against the agreed SLA thresholds so stakeholders have accurate data.
B. Pause all development until latency concerns are fully resolved.
C. Communicate that latency concerns are a known LLM limitation that cannot be addressed.
D. Replace the current Claude model with a third-party model to signal responsiveness.
E. Revise the SLA definition collaboratively with stakeholders if current targets are not achievable given production constraints.
A,E
A. Enable Tool Search so tool definitions are deferred and discovered on demand rather than loaded into context upfront.
B. Disable every MCP server in the configuration to free up context budget, accepting that the team loses all tool access and cannot perform any MCP-dependent task in the session.
C. Increase the prompt's verbosity with additional instructions and context, which consumes more of the context budget rather than reducing the tool-definition overhead causing the issue.
D. Add additional MCP servers to give the team more capability, which increases rather than reduces the number of tool definitions loaded into the session's context budget.
A
A. Tool calls execute server-side under a least-privilege service principal with scoped permissions.
B. Service credentials are placed in the prompt context, where they can leak into logs and traces.
C. Role-based access control is enforced only at the response-rendering layer after the model accesses restricted data.
D. Per-user OAuth tokens are exchanged with scope-restricted permissions and refreshed within the active session.
E. Tool inputs and outputs are encrypted in transit using transport-layer security between services.
B,C
A. Recognize the first-run permission grant as the cause, document the expected behavior in onboarding guidance, and confirm that subsequent runs succeed.
B. Reinstall the operating system to clear all permission state without first confirming whether the one-time permission grant caused the failure.
C. Disable operating-system permission dialogs entirely, accept the resulting security implications, and proceed without confirming whether the failure recurs.
D. Treat the first-run failure as a permanent fault, replace the MCP server, and do not verify whether subsequent runs succeed.
A
A. An expired TLS certificate blocks outbound API calls to Claude.
B. A database connection timeout causes retrieval to return an empty result set.
C. The model refuses a legitimate query because surface features trigger an overly broad safety pattern.
D. A misconfigured load balancer routes requests to a deprecated API version.
E. The model generates a plausible-sounding answer unsupported by any retrieved document.
C,E
A. Document the assessment outcome and present it to the risk committee.
B. Recommend mitigations and residual-risk acceptance for all identified threats.
C. Identify the assets that the deployment touches, along with the sensitivity of each asset.
D. Recommend mitigations and residual-risk acceptance for risks that remain.
E. Enumerate the threat actors and attack vectors relevant to the deployment.
C,E
A. Embed approved override phrases that users can invoke to bypass guardrails.
B. Lower sampling temperature globally to eliminate all variability in responses.
C. Validate the model output against a structured schema before downstream actions are taken.
D. Layer prompt-level guardrails with runtime content checks rather than relying on either alone.
E. Rely on a single hardened system prompt as the only guardrail mechanism.
C,D
A. The developer's keyboard layout or input-method configuration is the cause of the elevated context consumption, introducing extra tokens before the engineer types any message.
B. Many MCP servers are configured, each contributing tool definitions to the context budget; Tool Search is not enabled, so all definitions load upfront.
C. The model has internal personal preferences or default behaviors that silently consume large portions of context budget before any user message is processed, independent of tool configuration.
D. The font rendering or display-scaling settings of the IDE are converting visual output into additional context tokens, causing the high pre-session context consumption.
B
A. Managed configuration pushed to all endpoints by the administrator.
B. Environment variables set at the operating-system level on each workstation.
C. Project-scope .claude/settings.json and .mcp.json files committed to the repository.
D. Each engineer maintains a personal ~/.claude/settings.json with the shared definitions.
C
A. Tell the engineer to retry the denied action verbatim repeatedly until the denial stops appearing, without inspecting the active permission rules to determine whether the denial is intentional.
B. Disable the permission system entirely across all scopes to remove the denial, eliminating all tool-pattern and deny-rule controls rather than identifying and amending the specific rule.
C. Inspect the active permission rules across all scopes—managed, command-line, local, project, and user—to identify which rule is denying the action and confirm whether it should be amended or remain denied.
D. Grant the engineer unrestricted Bash access to bypass the specific rule causing the denial, removing all tool-pattern constraints rather than amending only the rule in question.
C
A. Claude Code reviews the pull request and posts a structured analysis as a comment, while a human reviewer retains the approval decision under the existing branch-protection rules.
B. Claude Code merges every pull request automatically after completing its analysis, bypassing human approval and the existing branch-protection rules.
C. Claude Code disables all existing branch-protection rules to streamline the merge process, removing human approval as a required gate.
D. Claude Code silently deletes pull requests it assesses as low quality without posting a comment or notifying the author.
A
Which factor should most heavily influence your recommendation?
A. Whether the current seven agents map cleanly to the patterns supported by managed agents.
B. Whether managed agents reduce per-invoice token costs across the existing processing volume.
C. Whether managed agents support the current bus topology used by the platform team.
D. Whether managed agent data handling satisfies the network boundary required by security.
D
A. Identify the audience and the questions the guide must answer for that audience.
B. Translate the guide into the supported regional languages before drafting.
C. Validate the guide with the implementation team and incorporate corrections.
D. Establish the document under version control and assign a review cadence.
E. Outline the guide sections covering the overview, components, contracts, flows, runbooks, and limitations.
A,E
1) Dense vector retrieval is well suited to recovering paraphrased intent against unstructured text.
2) Sparse term-matching retrieval recovers exact terms (such as identifiers and rare tokens) more reliably than dense alone.
3) Structured query retrieval is the right fit for filter-and-aggregate workloads against a relational store with schema and indexes.
4) Hybrid retrieval is identical to dense-only retrieval and shares the same recall characteristics.
5) Random sampling of a data store is a sound retrieval strategy for production Q&A.
Y,Y,Y,N,N
A. Increase the context-window size to allow more retrieved chunks per query.
B. Switch the retrieval index to a denser embedding model to improve chunk-relevance scores.
C. Determine whether the failure reproduces on the previous model version to test for a model mismatch.
D. Reduce the temperature setting to lower response variance across all query types.
E. Inspect the system-prompt grounding instructions to determine whether citation constraints remain intact.
C,E
A. Statement 1: Efficiency; Statement 2: Transformation; Statement 3: Solution Cost; Statement 4: Performance SLA
B. Statement 1: Productivity; Statement 2: Efficiency; Statement 3: Solution Cost; Statement 4: Performance SLA
C. Statement 1: Transformation; Statement 2: Productivity; Statement 3: Solution Cost; Statement 4: Efficiency
D. Statement 1: Efficiency; Statement 2: Productivity; Statement 3: Performance SLA; Statement 4: Solution Cost
A
1) Drafting first-pass investigative reports from semi-structured incident logs for analyst review.
2) Computing real-time fraud scores at sub-50-millisecond latency on a streaming pipeline.
3) Long-context contract review with structured clause extraction and deviation flagging.
4) Replacing a vector index for semantic retrieval over a multi-million-document corpus.
5) Routing inbound support tickets into 30 categories with reasoning for the chosen routing.
Y,N,Y,N,Y
A. Rebuild the entire system architecture from scratch at the start of every iteration cycle regardless of what production telemetry, evaluations, and stakeholder feedback indicate is needed.
B. Stop measuring production outcomes once the deployment has successfully launched, treating the go-live milestone as the end of the evaluation and iteration cycle.
C. Discard the evaluation framework and reference set once the deployment is in production, accepting that future iterations will have no structured basis for measuring the impact of changes.
D. Review production telemetry, sampled output evaluations, and stakeholder feedback to identify the highest-impact change for the next cycle, then plan the change against the evaluation framework.
D
Lựa chọn: A. Code or Hierarchical Specs B. Heterogeneous Short Records C. Long Structured Documents
1) Function-level or section-level chunking for code modules
2) Tree-aware chunking that follows code or specification hierarchy
3) Per-record chunking where each record is one chunk
4) Semantic chunking along clause or paragraph boundaries
5) Fixed-size chunking with overlap for short records of similar length
6) Hierarchical chunking that mirrors document section structure
A,A,B,C,B,C
1) Zero-shot is appropriate as a starting point for closed-set classification when categories and descriptions are provided in the prompt.
2) Adding a few-shot example set with exact field names anchors output formatting on extraction tasks.
3) Chain-of-thought should be the default on every task regardless of complexity.
4) Leading-question framing is best mitigated by asking for an even-handed comparison with stated criteria.
5) Behavioral differences across model versions can be ignored once a prompt has been validated on one version.
Y,Y,N,Y,N
A. Disable adversarial evaluation entirely during model-version upgrade cycles to reduce evaluation cost, accepting that safety drift will go undetected until it appears in production.
B. Rotate adversarial inputs randomly so no two upgrades are scored on the same set.
C. Skip evaluation on each model-version upgrade and rely on user-submitted complaints to surface safety drift after the upgraded model has already served production traffic.
D. Maintain an adversarial evaluation set with version-attributed scoring so each upgrade is measured against the same set before promotion.
D
A. Trusting that the model will intrinsically recognize and reject all bypass attempts without prompt-level instructions, runtime classifiers, scoped permissions, or audit logging.
B. Prompt-level instructions that treat user content as untrusted data, runtime classifiers that detect override attempts, scoped tool permissions that cannot be elevated by user content, and audit logging of attempts.
C. Removing all safety restrictions and guardrails to eliminate the attack surface that bypass attempts target, accepting that this makes the assistant unrestricted for all inputs.
D. Granting users any privilege level they assert in their message content, on the assumption that cooperative behavior requires honoring self-declared authority without independent verification.
B
A. Clear the prompt cache and resubmit all pending requests to eliminate stale cached prefixes.
B. Compare the current system prompt and output schema configuration against the last known good version from before the maintenance window.
C. Switch to a different Claude model tier to rule out provider-side changes as a contributing factor.
D. Increase the max_tokens limit to determine whether output truncation is causing incomplete JSON structures.
E. Replay a set of pre-maintenance requests against the current configuration and inspect the raw model output before downstream parsing.
B,E
A. Per-developer authorship across the 280 engineers with no team-level coordination required.
B. Centralized authorship by a single platform team responsible for every Skill produced.
C. Fully decentralized authorship across the 14 teams with no review before publication.
D. Federated authorship across the 14 teams with a central review and publication gate.
D
A. The most recent set of design presentation slides without component-level diagrams, interface contracts, an evaluation framework with a reference set, runbooks, or a known-limitations register.
B. A verbal walkthrough conducted on the day of handoff with no written architecture overview, ADRs, component contracts, evaluation framework, runbooks, playbook, or known limitations.
C. Architecture overview, ADRs, component contracts, evaluation framework with reference set, runbooks, on-call playbook, and known limitations.
D. Source code alone with no integrating architecture overview, ADRs, component contracts, evaluation framework, runbooks, on-call playbook, or known-limitations register to support the delivery team.
C
A. Validate structured outputs against a schema before downstream actions are executed.
B. Enforce RBAC at the retrieval layer before content enters the model context.
C. Move credentials out of the prompt context and resolve them from a server-side secret store.
D. Add actor attribution to tool-call logs so each call records the initiating user identity.
E. Replace the shared API key with per-user OAuth tokens carrying scope-restricted permissions.
D,E
A. Transparency obligations are satisfied by disclosing that an AI system is in use, without further evaluation.
B. Fairness testing is required only when the training dataset is known to contain protected-class labels.
C. The model may carry demographic biases from pretraining that manifest in screening outcomes regardless of fine-tuning.
D. The system should be evaluated on outcome-disparity metrics across protected groups before deployment.
E. Bias evaluation is unnecessary when the model provider has published a responsible-use policy.
C,D
A. The system must extract a defined set of specific fields from invoice attachments and populate a downstream data record.
B. The system must produce a draft response that a human reviewer can edit before sending.
C. The system must classify inbound tickets into a defined set of categories.
D. The system must respond at p95 latency under 800 milliseconds at the expected request volume.
D
Lựa chọn: A. Model Stage B. Post-Processing C. Pre-Processing
1) Claude-based classification of invoice type
2) Persistence of validated records to the system of record
3) Schema validation of the extracted fields
4) Claude-based extraction of structured invoice fields
5) PII redaction on extracted text prior to model invocation
6) Optical character recognition on scanned invoice images
A,B,B,A,C,C
Which two Discernment-competency observations should you raise BEFORE approving the launch? (Select two.)
A. The acceptance rate alone proves readiness for general production use.
B. The survey response rate may not be statistically representative of all specialists.
C. The unconsidered criteria represent a scope gap in the assistant's input space.
D. Acceptance does not establish whether recommendations remain correct after specialist review.
E. The pilot duration was probably too short to demonstrate reliability across the full year.
C,D
A. Reduce the number of historical sales chunks retrieved across each query run.
B. Truncate the policy preamble to remove non-essential clauses from the prompt.
C. Enable prompt caching on the static policy preamble across the recurring calls.
D. Switch the workload to a smaller, faster Claude model tier across all queries.
E. Cache common retrieved sales chunks accessed across many of the daily queries.
C,E
A. The capability needs to query a live database for the most recent regulatory filings.
B. The capability must also be callable from a developer's command-line interface.
C. The capability requires direct authentication against the corporate identity provider.
D. The capability is procedural knowledge with no live external-system calls required.
D
1) A read-only catalog lookup tool that returns vendor and SKU information
2) An inbox-send tool that emails purchase requests to vendors directly
3) A draft-write tool that creates purchase-request drafts in the review queue
4) A production-database admin tool unrelated to procurement
5) A read-only policy-document tool that returns the relevant procurement policies
Y,N,Y,N,Y
1) Heavier-reasoning models typically consume more of the rate limit and run more slowly than lighter models on the same input.
2) A representative-sample evaluation on the target workload is the right basis for confirming a model selection.
3) The most capable model is always the right choice regardless of the workload profile.
4) Tiered routing can serve routine traffic with a lighter model while reserving a heavier model for traffic that needs its capability.
5) Selecting a model based on which version was most recently announced is the right basis for production decisions.
Y,Y,N,Y,N
Proposal A adds Claude Code to the IDE for inline code generation and review.
Proposal B routes all code-generation requests through a shared Slack bot without IDE integration.
Which two observations most accurately evaluate these proposals against workflow-improvement objectives? (Select two.)
A. Proposal B is superior because centralizing requests in Slack creates an auditable log of all code-generation activity.
B. Proposal B introduces workflow friction by requiring developers to leave the IDE, undermining the productivity objective.
C. Proposal A reduces context switching by providing AI assistance at the point of development without requiring a separate tool.
D. Proposal B improves workflow velocity because Slack notifications create an asynchronous review queue.
E. Both proposals are equivalent because the model capabilities are identical regardless of the integration point.
B,C
A. Summarize each filing once at intake and run all subsequent queries against the summary.
B. Cache the filing as the prompt prefix for reuse across the 14 queries per case.
C. Index filings in a vector store and retrieve only the relevant passages per query.
D. Move the workload to a smaller Claude model to reduce the per-token cost paid.
B
A. Adversarial tests using prompt-injection and malformed-input cases.
B. Regression tests against a stable reference set of previously known-good outputs.
C. Smoke tests that verify core paths after each deployment.
D. Integration tests that verify end-to-end pipeline behavior across all components.
E. Unit tests targeting only individual prompt-template rendering logic.
A,D
A. Enable prompt caching on the static system-prompt prefix to reduce billable input tokens on repeated calls.
B. Route straightforward query types to a smaller, faster Claude model and reserve the full model for complex cases.
C. Increase max_tokens to reduce the frequency of truncated responses requiring follow-up calls.
D. Add a retrieval step that fetches the full source corpus into the context window before generation.
E. Expand the system prompt to include additional few-shot examples on every request.
A,B
A. Compare the in-place controls against the regulatory requirements to identify any compliance gaps.
B. Identify the applicability of the regulation based on data types, jurisdiction, and audience.
C. Schedule the remediation work with the engineering team based on the prioritized gap findings.
D. Document the identified gaps along with recommended remediations and residual risk for signoff.
E. Inventory the vendor-provided compliance tooling and confirm which compliance affordances are in place.
B,E
Each correct answer presents part of the solution.
A. Sample recent summaries to estimate the fabrication frequency across the population.
B. Disable the assistant immediately for all current users without any prior diagnostic analysis.
C. Review whether citation-grounding controls exist anywhere in the current generation pipeline.
D. Communicate to users that the assistant does not fabricate output as a matter of design.
E. Treat the incident as an anecdotal isolated case and take no further investigative action.
A,C
Control A adds an outbound tool allowlist with destination restrictions and per-call review.
Control B scores responses against a stable adversarial evaluation set after each model-version change.
Which two risk categories are correctly matched to these controls? (Select two.)
A. Control A - prompt injection from adversarial content in retrieved data
B. Control A - silent quality drift after a model-version upgrade
C. Control A - data exfiltration via outbound tool calls
D. Control B - data exfiltration via outbound tool calls
E. Control B - silent quality drift after a model-version upgrade
C,E
A. Select the lightest model that consistently meets the quality bar across the sample.
B. Retest the model choice when a new model version becomes available.
C. Choose a candidate model based on the requirements profile and known capabilities.
D. Define the quality bar, latency tolerance, and expected volume for the workload.
E. Sign off the production rollout plan with the platform and security teams.
C,D
A. Dashboard and log references only, without alert definitions, triage steps, escalation paths, or rollback procedures for the on-call engineer to act on.
B. Common alerts and their triage steps, escalation paths, rollback procedures, and references to the relevant dashboards and logs.
C. Alert definitions and triage steps only, without escalation paths, rollback procedures, or references to dashboards and logs for on-call use.
D. Escalation paths and rollback procedures only, without alert definitions, triage steps, or dashboard references to guide initial incident response.
B
A. Hold an open-ended meeting with no pre-distributed agenda or artifacts, and rely on participants' memory to carry decisions and follow-up owners forward.
B. Define a focused agenda, share the artifacts in advance, capture decisions and follow-ups in writing, and confirm action owners and dates.
C. Distribute artifacts at the session start rather than in advance, so stakeholders review materials in real time without preparation before the discussion begins.
D. End the session without recording decisions, follow-up items, action owners, or dates, relying on participant memory to carry the session's outcomes forward.
B
A. Generate documentation from the model's training-data recall without reading any of the actual repository code, accepting that the output will not reflect the current implementation.
B. Have the subagents publish generated documentation directly to the public-facing site without passing through the team's normal review workflow or any human approval step.
C. Configure subagents that read the relevant code files via filesystem and code-search tools, generate the documentation, and emit changes through the team's normal review workflow.
D. Disable all filesystem and code-search tools so the subagents cannot read any repository code, accepting that documentation generation will be entirely disconnected from the actual implementation.
C
1) Authentication and authorization run before retrieval so retrieval can filter by identity.
2) An asynchronous queue absorbs bursty traffic between intake and the model invocation layer.
3) Tax computation is encoded directly in the system prompt rather than in code.
4) Conversation logs include unredacted government identifiers to maximize signal for tuning.
Y,Y,N,N
A. Open with a deep dive into low-level implementation details targeted at engineering leads, and stop there without addressing the business outcomes or trade-offs the executive sponsor needs.
B. Lead with the decision, the business outcomes it serves, and the trade-offs accepted; follow with the technical rationale, alternatives, and implementation implications for the engineering audience.
C. Skip the rationale, alternatives, and trade-off discussion entirely and simply announce the chosen decision, leaving both audiences without the context needed to implement or validate it.
D. Present a single undifferentiated narrative that addresses technical and business concerns with equal weight throughout, treating both audiences as requiring the same depth on every section.
B
A. Augmented LLM with retrieval-augmented generation over the indexed authoritative corpus and citation rendering on each answer.
B. Multi-agent orchestration with a planner, researcher, and writer agent for every query.
C. A pure agent loop with open web-browsing tools to surface the most current policy information, without constraining retrieval to the authoritative internal corpus.
D. A static prompt with the entire policy corpus concatenated into every request.
A
A. Inside the system prompt as a natural-language instruction for Claude to ignore unauthorized documents.
B. At the retrieval layer, before any role-restricted content reaches the prompt-construction step or the model.
C. Nowhere in the pipeline; rely on the model's general refusal behavior to reject unauthorized document access without any enforced access control.
D. After the response is generated, by post-filtering content that should not have been retrieved.
B
A. Opus, because every moderation decision requires maximum reasoning depth regardless of classification complexity.
B. Haiku, because its latency and cost profile align with high-volume classification workloads that require limited reasoning depth.
C. Sonnet, because larger general-purpose models are preferred even when workload latency requirements are strict.
D. Sonnet with extended thinking enabled, because deeper reasoning should be applied to every moderation request to improve edge-case handling.
B
A. Increase response temperature to introduce variability that reduces the likelihood of specific recommendations.
B. Add an output classifier that detects and blocks responses containing regulated investment recommendation language.
C. Limit session length to reduce the volume of queries processed per user per day.
D. Log all user queries to a SIEM for post-hoc compliance review.
E. Define explicit out-of-scope categories in the system prompt with fixed refusal phrasing for investment advice requests.
B,E
A. Hide the scope-addition request from the broader delivery team to avoid a difficult conversation, allowing the change to proceed without team awareness of its timeline implications.
B. Decline the request outright without acknowledging the stakeholder's underlying need or offering alternatives such as deferral, descoping, or timeline extension.
C. Acknowledge the request, describe the scope and timeline implications transparently, and propose options—defer it, descope something else, or extend the timeline—for the stakeholder to choose.
D. Accept the additional scope into the current release without describing the timeline or descoping implications, allowing the delivery plan to absorb unacknowledged changes until they surface as delays.
C
A. The outbound HTTP tool returns a 200 response when the assistant calls an allow-listed domain to fulfil a user-initiated data-lookup request.
B. The user submits a routine question and receives a routine answer.
C. Adversarial content in a retrieved document instructs the model to call the outbound HTTP tool and send sensitive content to an attacker-controlled URL.
D. The internal-document retrieval tool returns a document that the user is authorized to view.
C
A. Confirm that vendor licensing terms permit the planned production use of the model.
B. Verify that outputs do not rely on generalizations about people that the underlying data does not support.
C. Confirm that high-impact decisions retain human accountability rather than being attributed to the model.
D. Restrict ethics review to outputs that exceed a defined model-confidence threshold.
E. Confirm that latency and throughput targets are met across supported user populations.
B,C
A. Centralized log retention for guardrail violations with quarterly review by the security team.
B. Per-role tool allow-lists enforced at the orchestration layer before any tool call executes.
C. User feedback channels that route reported guardrail failures into the product backlog for triage.
D. Periodic refresh of the system prompt wording to keep refusal language current and clear.
E. Adversarial-input coverage in the evaluation set with regression tracking on guardrail performance.
B,E
A. No sampling, relying entirely on user complaints to reveal quality and safety problems after they affect users.
B. Risk-stratified sampling that reviews all low-confidence and high-impact outputs and a smaller random sample of high-confidence routine outputs.
C. Inverse sampling that reviews only high-confidence routine outputs and skips low-confidence and high-impact outputs.
D. Universal review of every output regardless of confidence or throughput impact.
B
A. Recommend that the sponsor revise the request and resubmit it later for evaluation.
B. Begin prototyping a generic assistant against the broad request before the next deadline.
C. Propose a fixed scope that you commit to by default based on your own assumptions.
D. Facilitate a structured discovery to define the failing decision and the target metric.
D
A. Approval rate parity does not by itself assess error rate parity across protected groups.
B. Match with human underwriters does not establish freedom from underwriter-introduced bias.
C. The 94 percent match rate is sufficient evidence of fairness for the assistant's decisions.
D. The fairness team's review process likely missed at least some of the protected groups studied.
E. A larger sample is needed before any meaningful fairness claim can be made about the model.
A,B
A. Disable prompt caching entirely to ensure fresh context processing on every request, preventing stale prefix content from affecting latency-sensitive interactions.
B. Reduce retrieval depth to the top-k passages that historically cover the answer, and cache stable system-prompt content.
C. Increase retrieval depth to the corpus maximum to improve recall regardless of latency.
D. Switch every turn to the heaviest available model to maximize output quality, accepting that the increased model latency will worsen the per-turn SLO rather than improve it.
B
A. Record each session and distribute the recording to stakeholders who could not attend live.
B. Escalate any disagreement among stakeholders to the executive sponsor for binding resolution.
C. Rotate facilitation among the participating stakeholder groups to share ownership of the routine.
D. Set a regular cadence for revisiting expectations and assumptions as conditions evolve over time.
E. Reconcile divergent stakeholder positions explicitly rather than papering over them in the moment.
D,E
A. The document specifies integration contracts, configuration schemas, and expected input/output shapes for each component.
B. The document includes a decision log that records the rationale for key architectural choices and the alternatives rejected.
C. The document provides a high-level narrative description of the system without component-level detail.
D. The document includes the architect's contact information for questions during implementation.
E. The document lists all Claude models that were evaluated but does not specify which was selected or why.
A,B
A. Add a priority instruction directing the model to evaluate all instructions and apply whichever appears most contextually appropriate on each request.
B. Remove or rewrite the gap-filling instruction so the prompt consistently constrains the model to source-supported content.
C. Increase temperature so output randomness masks the contradiction.
D. Keep both instructions and rely on the model to decide which one to follow on each request.
B
A. A workflow pattern, because agentic patterns do not support tool invocations and therefore cannot execute the persist step that writes results to the downstream store.
B. An agentic pattern, because the open-ended planning capability of agents produces more consistent structured outputs than a fixed workflow graph on classification tasks.
C. An agentic pattern, because agents are categorically more accurate than workflows and therefore always preferable regardless of step predictability.
D. A workflow pattern, because the steps are well-defined and predictable per-request token cost is preferred over flexibility.
D
Which two findings should you present to justify capability decomposition before adding the router?
(Select two.) Each correct answer presents part of the solution.
A. Tool descriptions overlap across multiple claim categories within the agent's tool set.
B. Several tools have not been invoked across the most recent 90 days of traffic.
C. The 34 tools serve four distinct claim-workflow domains within the triage scope.
D. The router pattern is well documented in the team's internal architecture guide.
E. The proposed router introduces an additional model call on every incoming request.
A,C
A. User scope (~/.claude/settings.json) on each engineer's machine.
B. Environment variable defined in the CI/CD pipeline only.
C. Managed configuration applied centrally and marked as non-overridable.
D. Project scope (.claude/settings.json) committed to the repository.
C
A. Persisting personal editor theme preferences that follow an engineer across projects.
B. Saving a preferred Claude response language that applies to all repositories the engineer uses.
C. Enforcing a company-wide policy that must not be overridden by individual engineers.
D. Defining MCP server endpoints shared by all contributors to a specific repository.
E. Storing API authentication keys so they are not committed to version control.
A,B
A. Whether the vendor publishes detailed reference documentation for each candidate protocol.
B. Whether the team has prior implementation experience with any of the candidate protocols.
C. Whether the underlying transport supports encryption in transit between the integrated services.
D. Whether the integration must be portable across multiple AI clients in the ecosystem.
E. Whether the interaction is stateless and latency-sensitive or stateful and longer-running.
D,E
A. A direct API call to the existing endpoint with the appropriate scoped credentials.
B. A long-lived stateful session protocol for a stateless single-call interaction.
C. A bespoke streaming protocol layered over an unrelated asynchronous message bus.
D. An agent-to-agent handoff that introduces another Claude-based agent in front of the pricing service.
A
A. Constrain responses to source-supported content, require citations, and add a verification step.
B. Score each new model version against a stable adversarial evaluation set.
C. Replace the shared API key with per-user OAuth tokens to improve access control.
D. Treat retrieved data as untrusted and apply input classifiers at ingestion time.
A
A. No escalation criteria; the model decides independently on every turn whether to escalate, without explicit confidence thresholds, impact categories, or classifier-based ambiguity flags.
B. Escalation only after an affected customer has contacted support to complain, after the automated workflow has already completed without human review.
C. Escalation at the discretion of whoever is available when the team's on-call engineer has spare capacity, without a defined threshold, category, or ambiguity criterion.
D. A confidence score below a defined threshold, presence of high-impact decision categories, ambiguity flags raised by content classifiers, and the user's explicit request for review.
D
A. Integration tests that verify end-to-end behavior across pipeline components.
B. Adversarial tests designed to probe for safety and injection vulnerabilities.
C. Regression tests scored against a stable reference set of known-good behavior.
D. Smoke tests that verify core paths are reachable after each deployment.
C
A. BLEU score computed against a human-annotated reference summary set.
B. Role-based access-control enforcement rate measured on a red-team dataset.
C. Throughput measured as successful requests processed per minute.
D. Per-query token cost measured against the defined cost ceiling.
E. Response latency at the 95th percentile across a one-week sample window.
B,D
A. Component responsibilities, contracts between components, sequence diagrams of the dominant flows, configuration parameters with defaults, and operational runbooks.
B. Component responsibilities and interface contracts only, without sequence diagrams of the dominant flows, configuration parameters with defaults, or runbooks to guide operational tasks.
C. An architecture overview and sequence diagrams for the dominant flows, without interface contracts, configuration-parameter tables, or operational runbooks for the delivery team to follow.
D. An architecture overview and a list of known limitations, without component-level diagrams, interface contracts, configuration parameters, or operational runbooks to support implementation.
A
A. Increase retrieval depth on every request to maximize recall, worsening the dominant cost driver by adding more retrieved tokens per request rather than reducing them.
B. Add additional repeated content to the system prompt to give the model more guidance.
C. Move the long, repeated system prompt into a cacheable prefix and trim retrieved context to the spans relevant to each query.
D. Switch every request to the heaviest available model to maximize output quality, accepting that higher per-request inference cost compounds rather than addresses the dominant cost driver.
C
A. Misrepresent the AI's role in producing responses in order to make the assistant feel more trustworthy or more human, undermining informed user consent and organizational transparency.
B. Refuse to answer any user question about how the responses were produced or whether AI was involved, treating the AI's role as confidential operational information.
C. Disclose AI involvement to end users in line with the organization's transparency policy and provide a documented path to reach a human when needed.
D. Disclose AI involvement only to internal staff and operators while withholding that information from the end users whose interactions are materially shaped by the AI system.
C
A. Removing review eliminates the verification mechanism required for AI-generated output across the workflow.
B. Code-review capacity should be expanded to handle every code change submitted across the team.
C. The threshold should be increased to 200 lines to capture more changes.
D. AI-generated pull requests should be rejected by default across the organization.
E. Line count is a poor proxy for the actual risk introduced by a code change.
A,E
A. A target tied to a stakeholder sentiment measure such as “the team feels satisfied,” which cannot be measured objectively or used to trigger a documented breach response.
B. A measurable target with a defined metric, threshold, evaluation window, and consequence for breach—for example, 'p95 per-request latency under 800 ms over a 28-day window.'
C. A qualitative commitment such as “the system will be fast and reliable,” which names no metric, threshold, or evaluation window.
D. A target that names the metric and threshold but omits the evaluation window and breach consequence, leaving compliance periods and remediation triggers undefined.
B
A. Setting max_tokens to a low value to minimize the volume of text generated per request.
B. Selecting the highest-capability Claude model to maximize diagnostic accuracy.
C. Enforcing role-based access controls so that PHI is retrievable only by authorized personnel.
D. Ensuring patient data is never included in training feedback loops sent to the model provider without a BAA in place.
E. Using streaming responses to reduce perceived latency for clinical users.
C,D
(Select two.) Each correct answer presents part of the solution.
A. Define the sampling strategy and the escalation criteria at each oversight point in the pipeline.
B. Iterate the workflow design based on observed pilot findings before broader rollout to production.
C. Onboard the reviewer pool with role-specific training on the check criteria and escalation procedures.
D. Document the workflow with check criteria, escalation paths, and service-level agreements (SLAs) for each step.
E. Identify the decision points in the pipeline that require human oversight by impact and reversibility.
A,E
A. Use project scope for team-shared Model Context Protocol (MCP) servers and permission rules under version control.
B. Apply managed configuration centrally for security-critical settings that must not be overridden by individual engineers.
C. Use local scope for security-critical permission rules so each engineer can adapt them to ongoing work.
D. Use user scope for team-shared MCP servers so every engineer on the team has consistent access.
E. Use project scope for personal editor preferences so the preferences apply consistently within the project.
A,B
(1) required to complete defined tasks,
(2) frequently used and reduces handoffs,
(3) occasionally useful for unrelated work,
(4) speculative future utility.
Which categories should typically remain in the agent configuration?
A. Only category 3, because occasionally useful tools for unrelated work provide broader coverage and should take priority over tools required for the agent's defined tasks.
B. Only category 4, because speculative future-utility tools provide the most flexibility and should be configured even when no defined task currently requires them.
C. Categories 1 and 2 only, because they map to defined tasks and the agent's regular hand-offs.
D. All four categories, because broader tool access is categorically better for agent performance regardless of whether the tools map to defined tasks or regular hand-offs.
C
A. A slide deck in a presentation folder with no accompanying written rationale.
B. A code comment in a single file that contains an opinion of one engineer.
C. An Architecture Decision Record that states the context, the decision, the alternatives considered, the consequences, and the date and authors.
D. A short verbal note shared during a hallway conversation with no written record.
C
A. Treat all retrieved content as untrusted input and apply input classifiers with output validation.
B. Require citations for each claim and constrain responses to source-supported content.
C. Restrict outbound tool calls to an approved destination allow-list.
D. Score outputs against a stable adversarial evaluation set on each model-version change.
A
A. Discard all quantitative evaluation and replace it with qualitative impressions collected from a small, convenience-selected group that may not represent the tool's full user population.
B. Expand the evaluation set to cover the geographic regions and tenure bands the tool will serve, and rescore the system on the expanded set before broader release.
C. Reduce the evaluation set further to a single demographic subgroup to simplify score interpretation, narrowing coverage rather than expanding it to match the intended user population.
D. Continue using the narrow evaluation set drawn from one region and one tenure band because the existing benchmark scores are already high on that subset.
B
A. Lead with the technical architecture diagram and the full component list before any other section.
B. Lead with detailed cost projections across the full multi-year horizon before the rationale section.
C. Present the same dense narrative throughout with no stakeholder differentiation in any section.
D. Lead with the architectural decision, then address each stakeholder's primary concerns directly.
D
A. Increase the model sampling temperature so that intermittent issues surface more frequently for analysis.
B. File a support ticket with vendor support before any local reproduction or evidence collection.
C. Reproduce the issue with a minimal reproduction case that isolates one variable at a time.
D. Roll back to the previous Claude Code version immediately to confirm whether the issue is version specific.
E. List the configured Model Context Protocol (MCP) servers and inspect server status to identify connection failures.
C,E
Average summarization time decreased from 47 minutes to 6 minutes per document.
Associates spend less time on summaries, but overall billable output has not measurably changed.
Infrastructure costs increased by 22% because redundant retry logic generated additional API calls.
Some summaries require attorney correction, adding an average of 8 minutes of review per document.
Which analysis correctly attributes each observation to the appropriate business-value pillar?
A. Observations 1 and 2 both indicate efficiency gains; Observation 3 is a solution-cost issue; Observation 4 is a performance-SLA issue.
B. Observation 1 is a transformation outcome; Observation 2 is an efficiency gain; Observation 3 is a performance-SLA degradation; Observation 4 is a solution-cost issue.
C. Observations 1 and 4 together indicate a net performance-SLA improvement; Observation 2 is a transformation gap; Observation 3 is a productivity drain from over-engineering.
D. Observation 1 indicates an efficiency gain; Observation 2 shows that productivity has not yet been realized; Observation 3 is a solution-cost issue; Observation 4 is an efficiency loss that partially offsets Observation 1.
D
A. Disable every MCP server in the configuration to isolate the issue, removing all tool access rather than confirming whether the new server is registered.
B. Switch the team to a different Claude product family unrelated to the existing workflow, abandoning the current configuration rather than diagnosing the registration issue.
C. Verify the MCP server is registered using the listing command, then reconnect the session if needed, since configuration changes typically require a restart to take effect.
D. Reinstall the developer's operating system from scratch, discarding all local configuration and tool state before attempting any targeted diagnostic steps.
C
A. Apply progressive tool discovery so a curated initial subset is exposed and additional tools are loaded on demand based on the task.
B. Use a separate model call to summarize all 60 tool definitions before each user turn.
C. Increase the maximum context length and load all 60 tool definitions on every request, accepting the higher token cost and latency as necessary for full capability.
D. Hard-code a fixed set of five tools per request to reduce token usage, regardless of whether those tools are relevant to the current task.
A
Which two guardrail responsibilities should remain at the application layer rather than the Skill? (Select two.)
Each correct answer presents part of the solution.
A. Log every generated summary to the firm's compliance audit trail for retention.
B. Verify the requesting user is authorized to generate investment summaries at all.
C. Format output sections according to the firm's standardized house style guidelines.
D. Apply the disclaimer template that the compliance team has standardized firm-wide.
E. Apply the prohibited-language list that the compliance team maintains and updates.
A,B
A. Enterprise-tier deployment with a signed Data Processing Addendum, defined data-retention configuration, redaction of personal data not needed for the task, and documented data-subject rights handling.
B. Disabling all data-retention configuration, redaction controls, and data-subject-rights handling to simplify the deployment.
C. Using a personal Claude account tier for processing EU personal data at scale, with no signed Data Processing Addendum and no documented data-subject-rights handling procedure.
D. Pasting full EU personal data into every prompt to “give Claude complete context” without considering purpose limitation, data minimization, or the organization's Data Processing Addendum obligations.
A
A. Trace spans for each agent step are exported to the shared distributed-tracing backend.
B. Latency and token usage on every span are emitted to the central metrics pipeline.
C. Tool-call payloads and outcomes are recorded with redaction applied to known sensitive fields.
D. Model identity and version on each turn are not recorded with the turn artifacts.
E. Request-scoped correlation identifiers do not propagate across agent and tool calls.
D,E
A. Feature delivery schedule, roadmap dependencies, and scope boundaries for the product manager.
B. Implementation timeline, component interfaces, and deployment sequence for the engineering team.
C. Threat model, control mappings, residual-risk acceptance criteria, and audit traceability.
D. Decision rationale, business outcomes, and high-level risk summary for executive review.
C
A. The team has a recurring specialized task, such as database schema review, that requires a focused system prompt, narrow tool permissions, and a specific model selection across many sessions.
B. The team has a one-time ad hoc question that will not recur and does not require a focused system prompt, narrow tool permissions, or dedicated model selection.
C. The team has no recurring specialized tasks and uses Claude Code only for isolated general-purpose work that does not justify a dedicated system prompt or tool scope.
D. The team wants every Claude Code interaction to use the same generic system prompt with no task-specific specialization, narrow tool permissions, or dedicated model selection.
A
A. A minor copy edit is requested in a customer-facing string within the existing UI, which can be handled as a localized content change without altering component responsibilities or contracts.
B. A dashboard alert threshold needs a small numerical adjustment to reduce false-positive noise, which can be handled as an operational configuration change without a new design cycle.
C. A runbook step requires a clarification edit to improve on-call guidance accuracy, which can be handled as a documentation update without changes to component responsibilities or core contracts.
D. The system's current architecture cannot meet the new requirements without changes to component responsibilities or core contracts.
D
A. Define the metrics and the slices the deployment will monitor across normal and adversarial traffic.
B. Tune the alert thresholds based on observed normal-state distributions to reduce false positives.
C. Define the service-level objectives (SLOs) and the error budgets the deployment will be held to.
D. Build the dashboards that surface metrics across slices at the cadence the team operates on.
E. Document the dashboards, alerts, and runbooks for the on-call rotation that will respond.
A,C
A. Document the integrated workflow with handoff criteria, permission boundaries, and on-call runbooks.
B. Identify the workflow steps where AI-assisted tooling adds value and where human authority must remain.
C. Negotiate the workflow change with affected teams and obtain formal sign-off from each manager.
D. Iterate the integrated workflow based on pilot findings before broader rollout to the team.
E. Configure the project-scope MCP servers, permissions, subagents, and persistent project context.
B,E