300-835 · Question #14
Which two scenarios could be automated by combining the Webex Meetings XML API with other API-enabled systems? (Choose two.)
The correct answer is A. scheduling new-hire orientation meetings as part of an HR system workflow E. muting users in a Webex meeting when their Cisco Jabber presence status transitions to Away. Combining the Webex Meetings XML API with other API-enabled systems is the key framing here. Option A is correct because an HR platform (e.g., Workday, SAP) can fire an API call to the Webex Meetings XML API as part of its onboarding workflow, scheduling orientation meetings…
Question
Exhibit
Options
- Ascheduling new-hire orientation meetings as part of an HR system workflow
- Btriggering Webex meeting recording when the host disconnect from the meeting.
- Cautomatically launching the weekly Webex scrum meeting on Mondays at 9 AM
- Dreassigning an employee's scheduled Webex meeting to their manager then they leave the company
- Emuting users in a Webex meeting when their Cisco Jabber presence status transitions to Away
How the community answered
(23 responses)- A65% (15)
- B22% (5)
- C9% (2)
- D4% (1)
Explanation
Combining the Webex Meetings XML API with other API-enabled systems is the key framing here. Option A is correct because an HR platform (e.g., Workday, SAP) can fire an API call to the Webex Meetings XML API as part of its onboarding workflow, scheduling orientation meetings automatically - a true two-system integration. Option E is correct because Cisco Jabber exposes a presence API that can detect an "Away" status transition and then invoke the Webex XML API to mute that participant, again bridging two separate API-capable systems.
B is wrong because the XML API is request/response-based - it cannot listen for host-disconnect events and self-trigger; that would require an event-driven webhook mechanism the XML API doesn't natively provide. C is wrong because recurring scheduled meetings are a built-in Webex feature (set once inside Webex) and don't require combining with a separate external system. D is wrong because the Webex Meetings XML API doesn't support transferring meeting host ownership from one user to another, so this scenario is technically unsupported regardless of integration.
Memory tip: Think "cross-system handshake." The correct answers each name a separate, real system (HR platform, Jabber) whose API hands off to Webex. If the scenario lives entirely inside Webex (C, B) or asks Webex to do something it can't do (D), it's a distractor.
Topics
Community Discussion
No community discussion yet for this question.
