What happens if a meeting is in progress when a DelMeeting request is sent in the Webex Meetings XML API?

Question

Options

• AThe meeting host is notified and prompted to allow the meeting to be deleted.
• BThe DelMeeting request drops all call-in users and deletes the meeting.
• CThe DelMeeting request waits until the meeting is completed and then deletes the meeting.
• DThe DelMeeting request results in an error.

• A
  88% (29)
• B
  3% (1)
• C
  6% (2)
• D
  3% (1)

Explanation

Option A is correct because the Webex Meetings XML API is designed to protect active sessions - when a DelMeeting request targets an in-progress meeting, the API triggers a notification to the host, who must explicitly confirm the deletion before it proceeds. This safeguard prevents accidental loss of an ongoing session.

Why the distractors are wrong:

• B is incorrect because the API does not forcibly drop active participants without host authorization; that would be a destructive action without consent.
• C is incorrect because the API does not silently queue or defer the delete request - it responds immediately by prompting the host, not by waiting passively.
• D is incorrect because the request does not fail outright with an error; it succeeds in reaching the API but requires host approval before any action is taken.

Memory tip: Think of the host as a "gatekeeper" - the API always checks with the host before touching a live meeting. If you remember that Webex protects active meetings through host confirmation (not silent failures, queuing, or forced drops), you'll reliably pick the right answer.

No community discussion yet for this question.