Question 230
A design authority for field-service coordination has established this requirement: employees connect personal enterprise resources through an integration. Which intervention should be prioritized?
- Introduce OAuth consent and delegated scopes
- Introduce Short-lived scoped service credentials
- Introduce Per-user delegated authorization
- Introduce Tenant-bound retrieval filtering
Explanation
Correct Answer
A:The mechanism is specific: the integration can obtain user consent for minimum scopes and handle revocation. A credible implementation requires supported authorization flow and secure token storage, while its acceptance test monitors revoked-token access denial and scope mismatch rate. The alternative approaches leave the risk that administrator-wide credentials bypass user-controlled consent semantics.
Incorrect Answers
B:When unattended background jobs need limited read access to a narrow dataset, the integration can issue narrowly scoped renewable credentials for the job identity; that does not provide the capability actually needed: the integration can obtain user consent for minimum scopes and handle revocation.
C:When a shared integration must reflect each employee's actual record rights, the integration can enforce each call using the requesting user's authorized scope; the alternative cannot replace this key requirement: the integration can obtain user consent for minimum scopes and handle revocation.
D:When one vector index holds embeddings for several client organizations, the integration can apply tenant and document ACL filters before results reach the model; whereas the field-service coordination case must guard against the outcome that administrator-wide credentials bypass user-controlled consent semantics.
Question 231
An insurance processing pilot has enabled Acceptance criteria negotiation. Because open-ended satisfaction language cannot determine release readiness, the release board wants evidence of effectiveness, not just a favorable demonstration. Which metric most directly tests the proposed control?
- Audit source coverage and freshness pass rate on sampled queries
- Audit agreed priority scores and expected benefits for shortlisted uses
- Audit baseline handoff count and exception cycle time
- Audit approved acceptance conditions with measurable targets
Explanation
Correct Answer
D:The release should evaluate approved acceptance conditions with measurable targets rather than equate successful calls with real outcomes. The control works on the premise that the delivery team can turn goals into testable task-specific, risk-sensitive success criteria; the proposed measure can expose the risk that open-ended satisfaction language cannot determine release readiness.
Incorrect Answers
A:The alternative indicator checks whether the delivery team can validate quality, permissions, update cadence and ownership before promising RAG results when discovery assumes reliable source records that are fragmented or stale; however, that proxy would not demonstrate approved acceptance conditions with measurable targets for the selected intervention.
B:The alternative indicator checks whether the delivery team can jointly rank candidates by value, feasibility, harm and data readiness when teams propose many attractive pilots without common selection criteria; but the acceptance gate must instead inspect approved acceptance conditions with measurable targets to detect the targeted failure.
C:When automation is proposed without mapping present handoffs, failure paths and the delivery team can chart the existing input-to-outcome process and exception volumes; by contrast, the insurance processing release needs evidence from approved acceptance conditions with measurable targets.
Question 232
The insurance processing deployment uses Defense-in-depth incident response, but executive reports currently count only successful model responses. The residual concern is that a single classifier cannot handle every emergent attack pattern. Which acceptance measure would reveal real progress?
- Measure attack containment time and residual failure severity
- Measure cross-tenant fairness and quota bypass incident counts
- Measure disallowed action attempts stopped at the executor
- Measure prompt-injection success rate against controlled attack fixtures
Explanation
Correct Answer
A:An appropriate gate measures attack containment time and residual failure severity. It tests the mechanism in which the control layer can combine prevention, detection, containment and audited recovery, rather than a cosmetic demonstration. That distinction matters because a single classifier cannot handle every emergent attack pattern.
Incorrect Answers
B:The proposed measure would suit a setting where one customer can monopolize shared model capacity through abusive retries, since the control layer can enforce bounded usage budgets and anomaly controls per tenant; by contrast, the insurance processing release needs evidence from attack containment time and residual failure severity.
C:When assistants propose privileged write operations in customer systems, the control layer can require server-side authorization and business-policy checks before each side effect; however, that proxy would not demonstrate attack containment time and residual failure severity for the selected intervention.
D:The proposed measure would suit a setting where user-submitted attachments can contain instructions to steal private data, since the control layer can classify untrusted inputs and prevent them from acquiring instruction authority; but the acceptance gate must instead inspect attack containment time and residual failure severity to detect the targeted failure.
Question 233
A legal intake application will accept loosely formatted tool parameters without enforcing its input contract. Which defect becomes more likely as these inputs pass into action execution?
- The danger that accepting plausible-looking prose can break consumers or misroute cases
- The danger that sending raw records expands exposure without helping classification
- The danger that a network timeout can trigger repeated external state changes
- The danger that unvalidated inputs propagate ambiguity into generated actions
Explanation
Correct Answer
D:The loss of the control permits the situation where unvalidated inputs propagate ambiguity into generated actions. Its governing mechanism is that schema checks and normalization reject malformed inputs before they enter the model context; without an equivalent mechanism, a favorable demonstration cannot establish safety or quality.
Incorrect Answers
A:If downstream software requires machine-readable dispositions with fixed enums, accepting plausible-looking prose can break consumers or misroute cases; but this is not the immediate loss associated with omitting Validated input contract: unvalidated inputs propagate ambiguity into generated actions.
B:If raw customer messages contain identifiers irrelevant to classification, sending raw records expands exposure without helping classification; however, the named safeguard addresses the distinct hazard that unvalidated inputs propagate ambiguity into generated actions.
C:When a retrying agent sometimes creates the same support task twice, a network timeout can trigger repeated external state changes; whereas removing Validated input contract primarily exposes the risk that unvalidated inputs propagate ambiguity into generated actions.
Question 234
A supply-chain planning team is advancing OAuth consent and delegated scopes beyond its proof of concept. Engineers expect that the integration can obtain user consent for minimum scopes and handle revocation. What evidence of setup readiness should be required first?
- Establish propagated identity and resource-level access policy
- Establish identity provider integration and secret rotation process
- Establish authoritative tenant IDs and indexing ACL metadata
- Establish signing keys and bounded timestamp tolerance
- Establish supported authorization flow and secure token storage
Explanation
Correct Answer
E:Before deployment the team must confirm supported authorization flow and secure token storage. Without that preparation, the claim that the integration can obtain user consent for minimum scopes and handle revocation may remain unenforceable; the related exposure is that administrator-wide credentials bypass user-controlled consent semantics. The acceptance indicator is revoked-token access denial and scope mismatch rate.
Incorrect Answers
A:This prerequisite supports a method used when a shared integration must reflect each employee's actual record rights, because the integration can enforce each call using the requesting user's authorized scope; for this release, the team must first verify supported authorization flow and secure token storage.
B:The setup is useful to enable the alternative's behavior where the integration can issue narrowly scoped renewable credentials for the job identity and unattended background jobs need limited read access to a narrow dataset; however, the named intervention needs supported authorization flow and secure token storage before its protection can be enforced.
C:Where one vector index holds embeddings for several client organizations, the integration can apply tenant and document ACL filters before results reach the model; but the production dependency for OAuth consent and delegated scopes is supported authorization flow and secure token storage.
D:The setup is useful to enable the alternative's behavior where the integration can verify message authenticity, timestamp and replay protection before accepting commands and an upstream application posts actions to a model-driven workflow; for this release, the team must first verify supported authorization flow and secure token storage.
Question 235
A cost-cutting proposal for financial operations eliminates Stratified production-like test set. Which undesirable consequence would become most credible after that change?
- The possibility that a single fixed example cannot expose brittle prompt sensitivity
- The possibility that manual spot checks miss parser-breaking regressions
- The possibility that a high average score can mask catastrophic minority failures
- The possibility that static snapshots fail to reveal stale-index behavior
- The possibility that normal benign examples do not exercise trust boundaries
Explanation
Correct Answer
C:The risk is not a generic model inconvenience: a high average score can mask catastrophic minority failures. The proposed safeguard changes that boundary because the evaluation process can stratify by task type, risk, language and source complexity, and the release would need privacy-cleared examples and a sampling design plus subgroup coverage and performance against known strata to show the risk remains contained.
Incorrect Answers
A:The competing hazard is that a single fixed example cannot expose brittle prompt sensitivity in a workload where answers should not change when irrelevant formatting or names change; whereas removing Stratified production-like test set primarily exposes the risk that a high average score can mask catastrophic minority failures.
B:If downstream software expects exact structured fields and allowed enum values, manual spot checks miss parser-breaking regressions; but this is not the immediate loss associated with omitting Stratified production-like test set: a high average score can mask catastrophic minority failures.
D:The competing hazard is that static snapshots fail to reveal stale-index behavior in a workload where policy retrieval quality looks good using documents from the test period; whereas removing Stratified production-like test set primarily exposes the risk that a high average score can mask catastrophic minority failures.
E:The other exposure arises when a tool agent ingests external documents that can contain hostile instructions: normal benign examples do not exercise trust boundaries. Omitting the requested control instead leaves the more immediate risk that a high average score can mask catastrophic minority failures; but this is not the immediate loss associated with omitting Stratified production-like test set: a high average score can mask catastrophic minority failures.
Question 236
A telecommunications support team is selecting the next improvement for its AI service; retrieved customer text contains hostile instructions to override policy. What design choice has the strongest direct justification?
- Deploy Task-specific few-example template
- Deploy Parameterized prompt template
- Deploy Explicit schema and refusal conditions
- Deploy Role and instruction separation
Explanation
Correct Answer
D:This control changes the relevant system boundary: the model configuration can place durable task rules in trusted instruction channels and treat retrieved text as data. The team should establish trust-boundary review and prompt-injection fixtures before enabling it, then evaluate instruction-following accuracy under injected-document tests so that promoting document content into authority enables prompt injection is not hidden by fluent outputs.
Incorrect Answers
A:If a document tagger confuses closely related exception labels, the model configuration can demonstrate boundary cases with labeled examples near the instruction; whereas the telecommunications support case must guard against the outcome that promoting document content into authority enables prompt injection.
B:For a workload where hundreds of forms share the same logic with varying account details, the model configuration can keep stable instructions versioned and inject only validated task variables; the missing operational behavior is specific: the model configuration can place durable task rules in trusted instruction channels and treat retrieved text as data.
C:If the caller needs a machine-readable response even when evidence is insufficient, the model configuration can define output fields and abstention behavior for unanswerable inputs; the current decision instead depends on a specific capability: the model configuration can place durable task rules in trusted instruction channels and treat retrieved text as data.
Question 237
A program architect at manufacturing quality has endorsed Shared MCP connector governance. The proposed technical effect is that the engineering workflow can register reviewed MCP servers with clear ownership and allowed scopes. Which implementation condition is necessary to realize that effect?
- Prepare versioned setup scripts and build reproducibility checks
- Prepare central connector catalog and credential lifecycle
- Prepare team permission policy and escalation route
- Prepare isolated identities and explicit workspace inventory
Explanation
Correct Answer
B:Readiness depends on central connector catalog and credential lifecycle, not just a design approval. That condition supports the mechanism in which the engineering workflow can register reviewed MCP servers with clear ownership and allowed scopes. Without it, ad hoc personal connectors produce inconsistent and insecure access; monitoring approved connector use and access-policy compliance helps verify the deployed result.
Incorrect Answers
A:For the separate challenge where agent-assisted fixes work on one laptop but fail in CI, the engineering workflow can pin dependencies, tooling and environment assumptions across contributors; for this release, the team must first verify central connector catalog and credential lifecycle.
C:The setup is useful to enable the alternative's behavior where the engineering workflow can configure approved actions and deny risky operations by default and coding agents request shell access beyond the repository task; but the production dependency for Shared MCP connector governance is central connector catalog and credential lifecycle.
D:For the separate challenge where confidential projects share agent context and local tool access inadvertently, the engineering workflow can isolate project roots, secrets and tool permissions by approved workspace; for this release, the team must first verify central connector catalog and credential lifecycle.
Question 238
A contract administration engineering team is designing a Claude-supported workflow because raw customer messages contain identifiers irrelevant to classification. Which architectural decision most directly meets that requirement?
- Introduce Typed output validation and repair route
- Introduce Idempotent action boundary
- Introduce Audit-correlated processing stages
- Introduce Preprocessing and sensitive-field minimization
Explanation
Correct Answer
D:The intervention acts on the system behavior directly: preprocessing redacts unnecessary fields while preserving task-bearing content. Before rollout, verify agreed field-necessity rules and masking tests. The relevant success test is identifier leakage rate on representative test records; otherwise sending raw records expands exposure without helping classification.
Incorrect Answers
A:When downstream software requires machine-readable dispositions with fixed enums, the architecture can validate generated payloads against a contract and route failures to repair or review; it does not ensure the required behavior: preprocessing redacts unnecessary fields while preserving task-bearing content.
B:For a workload where a retrying agent sometimes creates the same support task twice, idempotency keys and deduplication protect side-effecting writes across retries; whereas the contract administration case must guard against the outcome that sending raw records expands exposure without helping classification.
C:When compliance teams cannot reconstruct which tool outputs informed a recommendation, stage-level correlation links input versions, retrieval results, model calls and final decisions; the alternative leaves the central requirement unproven: preprocessing redacts unnecessary fields while preserving task-bearing content.
Question 239
The energy operations staging review finds that open-ended satisfaction language cannot determine release readiness. Which design intervention is the most appropriate corrective action?
- Enforce Stakeholder and decision-rights mapping
- Enforce Use-case prioritization workshop
- Enforce Workflow observation interviews
- Enforce Acceptance criteria negotiation
Explanation
Correct Answer
D:The engineering fix changes the mechanism rather than the presentation: the delivery team can turn goals into testable task-specific, risk-sensitive success criteria. It requires baseline metrics and defined evaluation sample; a regression test should examine approved acceptance conditions with measurable targets in cases where open-ended satisfaction language cannot determine release readiness.
Incorrect Answers
A:When unclear authority causes late redesign and unowned risk decisions, the delivery team can define accountable decision owners and consultation rights early; but this remedy operates on another boundary, not the case where open-ended satisfaction language cannot determine release readiness.
B:Where teams propose many attractive pilots without common selection criteria, the delivery team can jointly rank candidates by value, feasibility, harm and data readiness; whereas the energy operations defect follows the path in which open-ended satisfaction language cannot determine release readiness.
C:Although the alternative reduces the risk that executive summaries alone omit edge cases that determine project success because the delivery team can observe actual exception handling and frontline work before mapping automation; yet it would not correct the observed weakness: open-ended satisfaction language cannot determine release readiness.
Question 240
An independent assessment of a manufacturing quality Claude system reports that a single classifier cannot handle every emergent attack pattern. Which change best closes the exposed control gap?
- Apply Ingress content classification
- Apply Defense-in-depth incident response
- Apply High-risk human approval gate
- Apply Tool-execution policy gate
Explanation
Correct Answer
B:The reported failure calls for the control under which the control layer can combine prevention, detection, containment and audited recovery. A prompt-only reminder or unrelated metric would not address the risk that a single classifier cannot handle every emergent attack pattern. Evidence of resolution requires layered controls and assigned incident owners and an improvement in attack containment time and residual failure severity.
Incorrect Answers
A:Where user-submitted attachments can contain instructions to steal private data, the control layer can classify untrusted inputs and prevent them from acquiring instruction authority; whereas the manufacturing quality defect follows the path in which a single classifier cannot handle every emergent attack pattern.
C:Although the alternative reduces the risk that after-the-fact logs cannot reverse a completed sensitive transfer because the control layer can stop before execution and require authorized human confirmation; but this remedy operates on another boundary, not the case where a single classifier cannot handle every emergent attack pattern.
D:When model self-restraint cannot guarantee that a bad action is blocked, the control layer can require server-side authorization and business-policy checks before each side effect; whereas the manufacturing quality defect follows the path in which a single classifier cannot handle every emergent attack pattern.