Question 690
A team assumes a generic SaaS subscription is sufficient to transmit PHI without checking contractual and security terms. What is the most direct remediation?
- Assess privacy risks and lawful processing grounds early
- Implement accountable access, deletion, and retention processes
- Validate FedRAMP authorization against exact service boundaries
- Check HIPAA business associate and safeguard requirements
- Minimize personal data and specify retention purpose
Explanation
Correct Answer
D:Confirm the specific service and contract support relevant HIPAA obligations, including any required business associate agreement and safeguards; compliance verification must match the actual product configuration and agreement; verify the repair using approved contracting, access controls, and PHI data-flow verification for the selected service path.
Incorrect Answers
A:Technical model accuracy does not establish permission to process sensitive personal information; involve privacy counsel to assess applicable lawful bases, transparency, rights, and whether a data-protection impact assessment is required before release; that control is assessed by completion of required privacy assessment and recorded resolution of high risks before go-live; the incident instead requires approved contracting, access controls, and PHI data-flow verification for the selected service path.
B:Deleting the original row does not automatically erase embeddings, caches, or observability copies; map data copies, implement lifecycle deletion where required, and retain audit evidence of the authorized request and its completion; that control is assessed by deletion-request completion across all inventoried repositories within policy deadlines; the incident instead requires approved contracting, access controls, and PHI data-flow verification for the selected service path.
C:A general government-cloud label or vendor marketing statement is not equivalent to FedRAMP authorization; verify the specific service, region, impact level, boundary, and agency authorization requirements with security officials before selection; that control is assessed by documented authorization-boundary mapping for every service handling regulated data; the incident instead requires approved contracting, access controls, and PHI data-flow verification for the selected service path.
E:Broad encryption does not justify collecting more personal data than the task needs; limit processing to necessary authorized fields, define a lawful purpose and retention controls, and document relevant privacy obligations; that control is assessed by sensitive-field inclusion rate in prompts and retention-policy compliance; the incident instead requires approved contracting, access controls, and PHI data-flow verification for the selected service path.
Question 691
Two separately operated business agents exchange signed work artifacts without borrowing each other's credentials. Which end-to-end test would establish that cross-agent collaboration preserves independent authorization?
- Measured cross-client contract compatibility and unauthorized-action denial for the same MCP service
- Reproducible build results with denied commands outside the approved allowlist
- Search coverage, tool cost, and provenance checks with no application-owned execution endpoint
- Event-to-index update delay and duplicate-event idempotency under replay
- Successful authenticated task exchange with each agent retaining its own permission checks
- Integration error rate and p95 latency on the fixed status-check path
Explanation
Correct Answer
E:Boundary tests verify interoperability without merging authorities; measure successful authenticated task exchange with each agent retaining its own permission checks at the release gate; an agent-to-agent contract can exchange bounded tasks and outputs while preserving local autonomy, identity, and authority of each specialist system.
Incorrect Answers
A:Testing both interoperability and permission enforcement captures the two essential concerns; a maintained MCP server can standardize discoverable tool and resource contracts while each client still enforces authentication and trust; this tests cross-client contract compatibility and unauthorized-action denial for the same MCP service; the actual release condition is successful authenticated task exchange with each agent retaining its own permission checks.
B:Execution tests check both the developer outcome and the sandbox boundary; a bounded CLI execution environment can reuse standard developer tools with explicit directory and command permissions; this tests reproducible build results with denied commands outside the approved allowlist; the actual release condition is successful authenticated task exchange with each agent retaining its own permission checks.
C:Managed execution should reduce infrastructure burden without weakening answer grounding; a supported server-executed tool can offload execution to the provider while the application retains usage, privacy, and result-validation responsibilities; this tests search coverage, tool cost, and provenance checks with no application-owned execution endpoint; the actual release condition is successful authenticated task exchange with each agent retaining its own permission checks.
D:Event-driven tests verify timely updates without wasteful polling loops; an authenticated event or webhook integration can trigger bounded processing only when upstream state changes; this tests event-to-index update delay and duplicate-event idempotency under replay; the actual release condition is successful authenticated task exchange with each agent retaining its own permission checks.
F:A stable-contract benchmark confirms that extra orchestration is unnecessary; a direct typed API client is appropriate when the interface, arguments, and control flow are known and stable; this tests integration error rate and p95 latency on the fixed status-check path; the actual release condition is successful authenticated task exchange with each agent retaining its own permission checks.
Question 692
A transcript summarizer is deployed with a deliberately restricted tool inventory. Red-team inputs mention financial updates and destructive operations that are unrelated to summarization. Which result proves that tool exposure is properly minimized?
- Measured single correct connector selection and consistent ticket states across repeated requests
- Zero mutation permissions for report-only identities across tool contract checks
- Changes rejected when requested tool scopes exceed the approved task manifest
- Absence of privileged tool calls before the confirmed transaction stage
- Unauthorized tool availability and invocation count in hostile transcript tests
Explanation
Correct Answer
E:Capability inventory and adversarial execution tests verify that unnecessary actions are unreachable; measure unauthorized tool availability and invocation count in hostile transcript tests at the release gate; give the agent a least-capability tool set mapped to the exact tasks it may perform, reducing accidental and adversarial action paths.
Incorrect Answers
A:Removing ambiguity should reduce routing variance without reducing supported tasks; consolidate overlapping operations behind a maintained interface and retire obsolete tool definitions after migration testing; this tests single correct connector selection and consistent ticket states across repeated requests; the actual release condition is unauthorized tool availability and invocation count in hostile transcript tests.
B:Permission tests reveal whether supposedly analytical agents can cause side effects; expose narrowly scoped read-only capabilities and gate changes through separate authenticated write paths with explicit approvals; this tests zero mutation permissions for report-only identities across tool contract checks; the actual release condition is unauthorized tool availability and invocation count in hostile transcript tests.
C:Policy-based manifest validation detects excessive authority before runtime exposure; maintain owner-approved manifests with risk classification, contract checks, permission reviews, and change-control gates; this tests changes rejected when requested tool scopes exceed the approved task manifest; the actual release condition is unauthorized tool availability and invocation count in hostile transcript tests.
D:Stage-bound tests prove that tool exposure follows authorization and intent; reveal high-impact tools only within a confirmed, authorized transaction stage; maintain server-side gating independently of model choice; this tests absence of privileged tool calls before the confirmed transaction stage; the actual release condition is unauthorized tool availability and invocation count in hostile transcript tests.
Question 693
A Claude-driven developer service fails intermittently after a tool integration update. What action best fits the business and technical boundary?
- Safely reproduce incidents using sanitized inputs
- Produce incident learning actions with accountable follow-up
- Roll back to a known-good tool and prompt release
- Reproduce incidents using correlated logs and configuration versions
Explanation
Correct Answer
D:Collect privacy-safe traces, request IDs, environment details, and exact configuration revisions to establish a reproducible failure case; reproducibility is a prerequisite for a trustworthy fix; evaluate the design with reproduction rate of sampled incidents from stored sanitized diagnostic metadata.
Incorrect Answers
A:Build redacted, access-controlled replay fixtures preserving relevant syntax and error conditions without unnecessary secrets or personal data; raw transcript reuse can expose confidential inputs and violate data-handling policies; this alternative would measure bug reproduction on sanitized fixtures with no sensitive token disclosure; it does not establish reproduction rate of sampled incidents from stored sanitized diagnostic metadata for the described use case.
B:Run blameless root-cause analysis, link corrective actions to owners, and add regression or operational safeguards before closing the incident; restarting the service restores availability but does not reduce the recurrence probability; this alternative would measure recurrence rate of the diagnosed failure and completion of preventive actions; it does not establish reproduction rate of sampled incidents from stored sanitized diagnostic metadata for the described use case.
C:Maintain versioned releases and documented rollback steps for hooks, prompts, model routes, and connector configuration; repeated untracked hotfixes can compound an outage and obscure the initial trigger; this alternative would measure time to restore normal operation using an approved previous release; it does not establish reproduction rate of sampled incidents from stored sanitized diagnostic metadata for the described use case.
Question 694
The same faulty recommendation persists because nobody categorizes or learns from reviewer interventions. What design correction resolves the reported failure?
- Give reviewers only necessary sensitive information
- Adopt risk-based sampling for low-impact decisions
- Escalate binding legal interpretations to qualified reviewers
- Capture reviewer overrides as structured improvement signals
Explanation
Correct Answer
D:Record correction reasons, provenance, and case labels under retention rules to support evaluation and process redesign; structured override trends reveal whether feedback improves the system over time; verify the repair using recurrence rate of categorized, previously corrected error types.
Incorrect Answers
A:Human oversight is not permission to expand access to unrelated personal information; minimize, redact, and scope information in review interfaces according to purpose and authorized reviewer role; that control is assessed by unauthorized field exposure and successful review accuracy after data minimization; the incident instead requires recurrence rate of categorized, previously corrected error types.
B:Universal manual review may be disproportionate when actions are reversible and errors are easily detected; combine automated checks with representative human sampling and exception-based review scaled to risk; that control is assessed by defect-detection rate and reviewer workload under a risk-tiered sampling policy; the incident instead requires recurrence rate of categorized, previously corrected error types.
C:A high model confidence estimate cannot replace delegated legal decision authority; define escalation thresholds and route consequential interpretations to qualified legal or compliance owners with source context; that control is assessed by correct escalation of ambiguous legal cases with reviewer attribution; the incident instead requires recurrence rate of categorized, previously corrected error types.
Question 695
A slow answer is logged only as 'model latency' although the delay occurred in the inventory API. Which change should the architect recommend first?
- Correlate model, retrieval, and tool spans in distributed traces
- Raise alerts on unexpected high-impact tool activity
- Separate retrieval, provider, and tool latency budgets
- Segment reliability metrics by tenant and workload
- Log structured tool outcomes without exposing sensitive payloads
Explanation
Correct Answer
A:End-to-end traces with consistent request and span identifiers identify which service and step consumed time; distributed spans expose ownership boundaries across the whole execution path; verify the repair using trace completeness and correct bottleneck attribution on instrumented fault injections.
Incorrect Answers
B:General chat satisfaction metrics are too delayed and indirect to detect dangerous mutation spikes; monitor write volume, denials, unusual resource patterns, and action-specific thresholds with fast containment routing; that control is assessed by time to detect and stop a simulated unauthorized bulk-write burst; the incident instead requires trace completeness and correct bottleneck attribution on instrumented fault injections.
C:Optimizing generation tokens cannot repair a slow connector that dominates the critical path; instrument per-stage timing and compare each segment against its allocated latency budget before changing model configuration; that control is assessed by stage-specific p95 deltas identifying injected bottlenecks; the incident instead requires trace completeness and correct bottleneck attribution on instrumented fault injections.
D:Overall averages can hide concentrated failures without meaningful dimensional analysis; break down latency, errors, and tool success by permission-safe tenant and workload dimensions with cardinality controls; that control is assessed by detection time for an injected single-tenant degradation; the incident instead requires trace completeness and correct bottleneck attribution on instrumented fault injections.
E:Full payload capture may help debugging but expands sensitive-data exposure and retention obligations; record tool type, status, duration, correlation IDs, and carefully redacted diagnostic fields under controlled retention; that control is assessed by error diagnosability with seeded sensitive fields absent from collected logs; the incident instead requires trace completeness and correct bottleneck attribution on instrumented fault injections.
Question 696
A coding copilot can fetch one API contract on demand rather than preloading dozens of unrelated specifications. Which release result would establish accurate endpoint usage with less documentation overhead?
- Correct endpoint contract use with lower documentation-token overhead
- Irrelevant tool exposure per intent with no loss of required task completion
- Cache-read tokens and total context cost while changing selected tool subsets
- Intent-classification accuracy before any tool disclosure or call
Explanation
Correct Answer
A:Targeted documentation fetches should improve focus without losing necessary details; measure correct endpoint contract use with lower documentation-token overhead at the release gate; discover resource summaries first and fetch the specific authoritative documentation section at the point of need.
Incorrect Answers
B:Exposure and completion metrics together reveal whether dynamic loading is too aggressive; select a bounded task-specific capability group after intent routing with conservative fallback for ambiguous requests; this tests irrelevant tool exposure per intent with no loss of required task completion; the actual release condition is correct endpoint contract use with lower documentation-token overhead.
C:The combined test reveals interaction between discovery strategy and prompt-prefix economics; isolate stable instructions from changing discovery payloads and measure cache behavior when tool inventories vary; this tests cache-read tokens and total context cost while changing selected tool subsets; the actual release condition is correct endpoint contract use with lower documentation-token overhead.
D:Phase separation verifies that the assistant understands the task before acting; separate goal interpretation and policy decisions from a downstream staged capability-discovery step; this tests intent-classification accuracy before any tool disclosure or call; the actual release condition is correct endpoint contract use with lower documentation-token overhead.
Question 697
A grant-writing service needs a second pass to check whether claims match source evidence before submission. What is the most targeted architecture choice?
- Delegate only specialized subtasks that add measurable value
- Version the handoff artifacts between agents
- Run independent specialists in parallel with a merge contract
- Separate independent critique from generation
Explanation
Correct Answer
D:A distinct verifier with a rubric and evidence access can challenge unsupported assertions before an external document is released; targeted seeded errors test whether critique catches defects rather than merely rewriting prose; evaluate the design with verified claim support rate after independent critique on seeded unsupported drafts.
Incorrect Answers
A:Introduce a specialist only when its independent expertise, tool scope, or parallelism beats a simpler call on representative evaluations; more agents by themselves do not provide additional knowledge, authority, or better outcomes; this alternative would measure marginal quality improvement per added specialist against its incremental cost and latency; it does not establish verified claim support rate after independent critique on seeded unsupported drafts for the described use case.
B:Immutable, versioned handoff artifacts and typed schemas prevent one agent from consuming ambiguous or mismatched intermediate state; artifact versioning governs exchange correctness, not whether the underlying market facts were researched accurately; this alternative would measure zero stale-artifact merges across concurrent revision and retry scenarios; it does not establish verified claim support rate after independent critique on seeded unsupported drafts for the described use case.
C:Parallel fan-out followed by deterministic aggregation can shorten wall-clock time if each branch has its own contract and errors are handled; parallel fan-out is unsafe when tasks mutate the same state or depend on each other's evolving outputs; this alternative would measure p95 end-to-end latency and deterministic merge completeness under one-branch failures; it does not establish verified claim support rate after independent critique on seeded unsupported drafts for the described use case.
Question 698
The team celebrates more draft completions while actual case closures stagnate. How should the design be corrected?
- Convert response-time expectations into a percentile SLO
- Design a degraded mode that protects the value proposition
- Measure productivity after correction and escalation
- Use a control group to establish incremental business impact
Explanation
Correct Answer
C:Measure net time saved after review, appeals, and escalations, segmented by complexity, before claiming productivity; net throughput reflects business output rather than the volume of AI text produced; verify the repair using end-to-end completed cases per paid work-hour with rework and appeal volumes.
Incorrect Answers
A:A percentile SLO does not alone reveal whether the answers are factually correct; define a p95 or p99 target against real end-to-end requests, including retrieval and tools, rather than reporting an average model time; that control is assessed by end-to-end p95 latency and error rate against the agreed service objective; the incident instead requires end-to-end completed cases per paid work-hour with rework and appeal volumes.
B:High answer accuracy in normal mode says little about process continuity during dependency failures; separate critical deterministic operations from AI enhancement and provide explicit fallback and manual paths when model service is unavailable; that control is assessed by successful completion of critical workflows during injected model outages; the incident instead requires end-to-end completed cases per paid work-hour with rework and appeal volumes.
D:Before-after counts without a credible comparison group may misattribute unrelated changes to the model; use matched baselines, controlled rollout, or appropriate difference-in-differences analysis to isolate contribution under plausible confounders; that control is assessed by incremental resolution lift compared with a comparable non-assisted cohort; the incident instead requires end-to-end completed cases per paid work-hour with rework and appeal volumes.
Question 699
A company changes an employee assistant's approval rules without telling affected users, leading to confusion during the release. A purchasing manager also needs periodic evidence of productivity gains and risk trends, not just token consumption. Which TWO lifecycle practices address change awareness and decision-ready performance reporting? Choose TWO.
- Communicate release behavior changes before rollout
- Clarify shared responsibility for the service boundary
- Establish a documented escalation path for service incidents
- Set observability and reporting expectations with stakeholders
- Route user feedback into a triaged, owned backlog
Explanation
Correct Answers
A:Define release notes, behavior-change notices, affected audiences, and support channels proportional to the deployment's impact; communication quality is reflected in predictable adoption and fewer avoidable surprises; its corresponding workstream should be validated by affected-user awareness and support-ticket volume following staged changes.
D:Agree on outcome-aligned service reports, cadence, escalation thresholds, and audiences during solution definition; reporting completeness lets stakeholders govern the system using relevant evidence; its corresponding workstream should be validated by delivery of agreed business and risk indicators on schedule with decision-ready interpretation.
Incorrect Answers
B:Define provider, platform, application, security, and business-owner responsibilities in an explicit operating model; a vendor SLA typically does not assign responsibility for every custom integration and decision rule; its natural acceptance measure is ownership coverage for failures across model, application, data, and tool layers, which does not satisfy the separate workstreams being assessed.
C:Define incident severity, on-call ownership, manual fallback authority, and customer communication triggers; generic 'contact support' guidance lacks accountable timing and action for critical failures; its natural acceptance measure is time to appropriate escalation and fallback activation during drills, which does not satisfy the separate workstreams being assessed.
E:Classify feedback by severity and root-cause type, assign owners, link trace IDs, and feed validated cases into regression tests; unstructured rating totals cannot by themselves direct a safe corrective action; its natural acceptance measure is time from actionable feedback to triage, owner assignment, and verified fix, which does not satisfy the separate workstreams being assessed.
Question 700
An engineering-analysis assistant executes hours of staged report generation and can lose workers mid-run. What is the most targeted architecture choice?
- Divide work along independently verifiable artifacts
- Define input and output contracts for each subtask
- Checkpoint long-running work for replay and recovery
- Parallelize only truly independent branches
Explanation
Correct Answer
C:Durable checkpoints record validated intermediate artifacts and resume at safe boundaries with idempotent side effects; replay testing verifies the precise recovery behavior the pipeline requires; evaluate the design with successful recovery after injected worker failures without duplicated writes or stages.
Incorrect Answers
A:Separate stages with typed artifacts allow validation and targeted reruns at meaningful boundaries; artifact decomposition controls work structure but does not set the organization-wide release SLA; this alternative would measure stage-specific defect localization and repair without redoing previously validated stages; it does not establish successful recovery after injected worker failures without duplicated writes or stages for the described use case.
B:Typed versioned contracts and compatibility tests let stages evolve while preserving their callers' assumptions; contracts define allowed shapes and semantics but cannot ensure a source is truthful; this alternative would measure contract test pass rate for independently upgraded stages and invalid payload rejection; it does not establish successful recovery after injected worker failures without duplicated writes or stages for the described use case.
D:Isolate independent tasks, retain separate results, then join only when required dependencies have completed; parallelizing dependent mutations without isolation can increase errors even if raw processing is faster; this alternative would measure correct merged clause counts across repeated parallel execution races; it does not establish successful recovery after injected worker failures without duplicated writes or stages for the described use case.