300-835 · Question #79
An organization is using Cisco Webex Meetings and wants to create a webhook to receive notifications when a meeting starts or ends. Which webhook event is used to configure this notification?
The correct answer is C. meeting.ended. meeting.ended is the correct Webex webhook event because it triggers a notification when a meeting session is terminated, which is the primary lifecycle event organizations configure to track meeting completion and drive downstream workflows (logging, recording access…
Question
Options
- Ameeting.created
- Bmeeting.participants
- Cmeeting.ended
- Dmeeting.started
How the community answered
(50 responses)- A4% (2)
- B8% (4)
- C86% (43)
- D2% (1)
Explanation
meeting.ended is the correct Webex webhook event because it triggers a notification when a meeting session is terminated, which is the primary lifecycle event organizations configure to track meeting completion and drive downstream workflows (logging, recording access, follow-up automation). This is a real, supported event in the Webex Meetings webhook API.
Why the distractors are wrong:
- A (
meeting.created) fires when a meeting is scheduled, not when it runs - it reflects calendar creation, not session activity. - B (
meeting.participants) is not a valid Webex webhook event type; participant changes use events likemeetingParticipants.inLobbyor similar scoped resources, not a generic "participants" event. - D (
meeting.started) is a plausible-sounding distractor, but it is not a valid standalone Webex webhook event in the waymeeting.endedis - the exam tests whether you know the actual event name, not just a logical-sounding one.
Memory tip: Think of the meeting lifecycle as a door - meeting.created is building the door, and meeting.ended is closing it. Exams love testing the "end" event because it's the trigger for real business logic like billing, reports, and notifications.
Topics
Community Discussion
No community discussion yet for this question.