200-901 Understanding and Using APIs Practice Question
In the context of Cisco Webex APIs, which mechanism allows an application to receive real-time notifications when a message is created in a space?
⚠ Common exam trap
200-901 often tests the misconception that real-time notifications require polling or persistent connections, when Cisco Webex specifically uses registered webhooks with resource/event pairs to deliver event-driven callbacks.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Registering a webhook with the resource 'messages' and event 'created'
Cisco Webex APIs support webhooks, which are user-defined HTTP callbacks that the Webex cloud invokes when a specified event occurs. Registering a webhook with resource 'messages' and event 'created' causes Webex to POST a notification to your target URL whenever a new message is created in a space, enabling real-time, event-driven integration without polling. This is the standard mechanism for receiving real-time notifications in Webex.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enabling Server-Sent Events (SSE)
Why it's wrong here
Webex does not expose Server-Sent Events for space message events; its real-time notification mechanism is webhooks, where Cisco POSTs event payloads to your HTTPS endpoint. SSE is tempting because it is a genuine one-way push standard used by other streaming APIs.
- ✓
Registering a webhook with the resource 'messages' and event 'created'
Why this is correct
Registering a webhook targeting the 'messages' resource with the 'created' event makes Webex push an HTTP POST notification to your URL whenever a message is posted in a space, satisfying the stem's real-time notification requirement.
- ✗
Polling the /messages endpoint every second
Why it's wrong here
Polling is client-initiated and returns only on request, so notifications arrive with up to one second of latency and waste quota; Webex delivers message-created events through registered webhooks. It is tempting because polling needs no public callback URL, which suits restricted lab environments.
- ✗
Using a long-lived HTTP connection
Why it's wrong here
A long-lived HTTP connection alone carries no event subscription or delivery contract, so Webex never pushes message-created payloads over it; webhooks provide that registered callback. It is tempting because persistent connections underpin streaming transports such as WebSockets and SSE.
Go deeper
Related to this question
About these practice questions
This 200-901 question is part of Courseiva's 975-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Cisco exam blueprint
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.