nerdexam
Cisco

300-920 · Question #48

Drag and Drop Question Drag and drop the code onto the snippet to construct the JavaScript to create a new meeting with the Webex Meetings XML API. Options can be used more than once. Answer:

The correct answer is accessToke; sessionTicket; { 'method' : 'POST' }. Webex Meetings XML API - Creating a Meeting Context The Webex Meetings XML API requires authentication credentials and an HTTP method when making requests from JavaScript (typically via fetch or a request library). The code snippet has three blanks to fill in. --- Why This…

Meetings

Question

Drag and Drop Question Drag and drop the code onto the snippet to construct the JavaScript to create a new meeting with the Webex Meetings XML API. Options can be used more than once. Answer:

Exhibit

300-920 question #48 exhibit

Answer Area

Drag items

{ 'method' : 'POST' }accessTokesessionTicket{ 'method' : 'PUT' }

Correct arrangement

  • accessToke
  • sessionTicket
  • { 'method' : 'POST' }

Explanation

Webex Meetings XML API - Creating a Meeting

Context

The Webex Meetings XML API requires authentication credentials and an HTTP method when making requests from JavaScript (typically via fetch or a request library). The code snippet has three blanks to fill in.


Why This Arrangement

Position 1: accessToke (accessToken)

This is the OAuth access token used to authenticate the API caller. It must be provided as the primary credential - the API will reject the request outright without it. It comes first because it establishes who is making the call.

Note: accessToke is a typo in the question for accessToken.


Position 2: sessionTicket

A sessionTicket is a Webex-specific credential obtained from a prior authentication exchange. It acts as a secondary session identifier that scopes the request to a specific authenticated session. It follows the access token because it depends on an already-established auth context.


Position 3: { 'method': 'POST' }

POST is the correct HTTP verb for creating a new resource. Creating a new meeting = POST. This is standard REST/HTTP semantics.


Why Not { 'method': 'PUT' }?

PUT is for updating or replacing an existing resource. Using PUT here would be semantically wrong - it would imply you're overwriting a meeting that already exists, not creating a new one.


Common Mistakes

MistakeWhy It's Wrong
Using PUT instead of POSTPUT = update, POST = create
Swapping accessToken and sessionTicketAuth token must come first as the primary credential
Omitting sessionTicket entirelyWebex XML API often requires both for session-scoped operations

Topics

#Webex Meetings API#HTTP POST method#API authentication tokens#JavaScript

Community Discussion

No community discussion yet for this question.

Full 300-920 Practice