Question 690
At Harbor Logistics, a distribution operations team is improving shipment exception triage during cross-channel acceptance testing (SF-A19-01). The administrator observes that a spoken customer request needs a human handoff but the voice implementation has only text fallback. Any fix must ensure that shipment changes remain attributable and reversible. Which continuing control best prevents this issue from recurring?
Explanation
Correct Answer
The preventive control directly addresses repeat failures: Test interruptions, escalation and transcription errors; require the check in the next release review at Harbor Logistics (SF-A19-01). It complements the corrective action, configure the supported voice route and escalation path with context retention, and protects the explicit condition that shipment changes remain attributable and reversible.
Incorrect Answers
This safeguard, “Test cross-workspace access and installation governance; review it with audit evidence from regression testing”, reduces a different source-defined risk: Internal employees expect the company agent in Slack but the connector exposes an unrelated public service agent. The correction must ensure that quoted amounts use authorized account and price-book records. That risk depends on: Channel connections must preserve the intended audience and authorization context. The recurring problem here is a spoken customer request needs a human handoff but the voice implementation has only text fallback. The correction must ensure that shipment changes remain attributable and reversible. The originally selected control “Test interruptions, escalation and transcription errors; review it with a documented exception process” is more specific because voice channel delivery has modality and escalation requirements beyond text-only configuration.
This safeguard, “Test channel-specific retries, identity and approval boundaries; review it and retest after dependent metadata changes”, reduces a different source-defined risk: A team assumes an asynchronous support email flow has the same state and latency as an interactive web chat. The correction must ensure that billing adjustments require verified eligibility. That risk depends on: Channel context changes how an agent receives messages and maintains interaction. The recurring problem here is a spoken customer request needs a human handoff but the voice implementation has only text fallback. The correction must ensure that shipment changes remain attributable and reversible. The originally selected control “Test interruptions, escalation and transcription errors; review it with a documented exception process” is more specific because voice channel delivery has modality and escalation requirements beyond text-only configuration.
This safeguard, “Test eligibility boundaries and explanatory wording independently; review it as part of periodic access and quality reviews”, reduces a different source-defined risk: The agent must enforce a refund eligibility rule but still explain decisions conversationally. The correction must ensure that donor details cannot be revealed across accounts. That risk depends on: Hybrid reasoning combines fixed business logic with flexible language generation. The recurring problem here is a spoken customer request needs a human handoff but the voice implementation has only text fallback. The correction must ensure that shipment changes remain attributable and reversible. The originally selected control “Test interruptions, escalation and transcription errors; review it with a documented exception process” is more specific because voice channel delivery has modality and escalation requirements beyond text-only configuration.