200-901 Understanding and Using APIs Practice Question
An application needs to receive real-time notifications when a new message is posted in a Webex space. Which Webex API feature should be used?
⚠ Common exam trap
Cisco often tests the distinction between push-based (webhooks) and pull-based (polling) mechanisms, and candidates may mistakenly assume WebSocket or SSE are available because they are common real-time technologies, but Webex specifically relies on webhooks for event-driven notifications.
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
✓
Create a webhook that triggers on 'messages' events
Webex uses webhooks to push real-time event notifications to an external server. By creating a webhook that triggers on 'messages' events, the application receives an HTTP POST request whenever a new message is posted in the specified space, eliminating the need for polling or persistent connections.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Establish a WebSocket connection to the Webex API
Why it's wrong here
Webex does not expose a WebSocket endpoint for receiving message events; its real-time delivery mechanism is webhooks, which push HTTP callbacks to a registered target URL. WebSockets are tempting because they suit real-time streaming generally, but here they would require the application to poll or maintain an unsupported connection.
- ✓
Create a webhook that triggers on 'messages' events
Why this is correct
Webhooks push event data to your HTTPS endpoint the moment a message is created, satisfying the real-time notification requirement without polling. Subscribing to the 'messages' resource delivers the posted message payload directly, whereas periodic GET requests to the messages API would introduce latency and unnecessary API calls.
- ✗
Use Server-Sent Events (SSE) from the Webex API
Why it's wrong here
Webex does not provide a Server-Sent Events endpoint; real-time message notifications arrive via webhooks, where Webex POSTs event payloads to a subscriber URL. SSE is tempting because it delivers server-pushed events over HTTP, but the Webex API implements webhooks instead, so no SSE stream exists to consume.
- ✗
Poll the messages endpoint every second
Why it's wrong here
Polling every second cannot deliver real-time notifications and risks rate-limit throttling; Webex webhooks push event data to a registered URL as messages are posted. Polling suits scheduled batch reconciliation where near-instant delivery is unnecessary and the endpoint tolerates repeated reads.
Go deeper
Related to this question
About these practice questions
One of 975 original 200-901 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.