A hospital's service desk wants a ticket opened whenever an assurance condition becomes true. Which handoff matches that request?
Select an answer to reveal the explanation.
Short Explanation
If the loading dock asked for a paper slip, handing them a radio channel does not fill the request. You open an ITSM ticket when the hospital's service desk asked for a ticket at the moment the condition is true. A polling API, an OpenTelemetry stream, or an alert-threshold page serves a team that asked for something else.
Full Explanation
The receiving team asked for a ticket when the assurance condition is true, which is an ITSM handoff into the hospital service desk. The integration should open that ticket so the desk can track, assign, and close the work in the system it already uses. A polling API lets some other tool pull data. The service desk did not ask to watch a dashboard or to poll, so an API leaves the requested ticket uncreated. OpenTelemetry streams metrics or traces into a pipeline that can chart the condition. That stream is valuable for a metrics team, and it is not the ticket the desk requested. An alert-threshold page notifies on-call when a condition is crossed. A page is not a ticket, and stopping at the page leaves the service desk without the record it asked to own. Choose the handoff by the consumer's request rather than by which integration is easiest to turn on. Exam caveat: API, alert threshold, OpenTelemetry, and ITSM are different deliveries, and only the ticket matches this desk. Operational check: fire a known test condition and confirm a ticket arrives in the hospital service desk queue.