300-920 Practice Questions

This script uses the jsxapi library to send a command to a Cisco collaboration device.

1. const xapi = require('jsxapi'); imports the necessary library.
2. xapi.command(...) is the correct method in the jsxapi library to execute a command, such as an HttpClient Get.
3. The .command method returns a JavaScript Promise. The .catch() function is the standard way to handle errors or rejections in a Promise chain.
4. Finally, printHttp(...) is the function call that executes the defined script logic.

Cisco DevNet & jsxapi GitHub Repository (Official Vendor Documentation): The official jsxapi documentation demonstrates the standard usage pattern.

Connecting: The README.md shows the proper way to import and initialize the library is const xapi = require('jsxapi');. (URL: https://github.com/cisco-js/jsxapi, Section: "Usage")

Executing Commands: The documentation explicitly states that to send a command, you use the xapi.command(path, params) method, which returns a promise. (URL: https://github.com/cisco-js/jsxapi, Section: "API > xapi.command(path, params)")

Promise Handling: The examples show the use of .then() for success and .catch() for handling errors, which is the standard for JavaScript Promises. (URL: https://github.com/cisco-js/jsxapi, Section: "API > xapi.command(path, params)")

This JavaScript code uses the Webex SDK to perform three sequential actions chained together with promises.

1. First, webex.rooms.create() is called to create a new Webex space named 'Q3 Budget Planning'.
2. The promise then resolves, passing the new room object as x. webex.memberships.create() is called to add a person to that room, using x.id to specify the roomId.
3. Finally, after the membership is created, webex.messages.create() is called to post a message into the same room. The roomId for this action is retrieved from the membership object y created in the previous step.

Webex JS SDK - Rooms: The official SDK documentation shows that webex.rooms.create({title: '...'}) is the correct method for creating a new space.

Source: Webex for Developers, SDK API Documentation

URL: https://webex.github.io/webex-js-sdk/api/#webexroomscreate

Webex JS SDK - Memberships: The documentation confirms that webex.memberships.create({roomId: '...', personEmail: '...'}) is used to add a user to a room.

Source: Webex for Developers, SDK API Documentation

URL: https://webex.github.io/webex-js-sdk/api/#webexmembershipscreate

Webex JS SDK - Messages: The webex.messages.create({roomId: '...', text: '...'}) method is documented as the standard way to post a message to a room.

Source: Webex for Developers, SDK API Documentation

URL: https://webex.github.io/webex-js-sdk/api/#webexmessagescreate

This sequence represents the logical flow for initiating a call with screen sharing using the Webex Browser JS SDK's Meetings API.

1. webex.meetings.create(destination): This is the first step. It creates a meeting object, which acts as the container for all information and media related to the call.
2. meeting.addMedia(mediaOptions): Before connecting, the local media streams (audio, video, and the initial screen share) must be prepared and added to the meeting object. This method handles that preparation.
3. meeting.getMediaStreams(): After the meeting is connected (via the meeting.join() method, which is implicitly assumed to occur after step 2), this method is used to retrieve the local and remote media stream objects, typically for rendering them in HTML <video> elements.
4. meeting.updateShare(shareOptions): This method is used during an active meeting to change the screen sharing source, for example, switching from one application window to another. It logically follows the initial setup and stream rendering.

The methods webex.call() and call.getMediaStreams() belong to a different, simpler API within the SDK that is not typically used for calls involving advanced media control like screen sharing.

Cisco Webex for Developers Official Documentation, Browser SDK Guide: The official guide outlines the process for making calls and managing media.

Making an Outgoing Call: The documentation shows that the process begins with webex.meetings.create(), followed by adding media, and then joining.

URL: https://developer.webex.com/docs/sdk-browser#making-an-outgoing-call

Screen Sharing: This section details the use of meeting.addMedia() to add a screen share stream before joining and meeting.updateShare() to modify the stream during the call.

URL: https://developer.webex.com/docs/sdk-browser#screen-sharing

The Webex API utilizes the OAuth 2.0 framework, which employs Bearer tokens for authentication. The standard for presenting a Bearer token in an API request is to use the Authorization HTTP header. The value of this header is constructed with the scheme name, Bearer, followed by a space and the access token itself.

The term Authentication is a general concept, but Authorization is the specific IETF-defined header name (RFC 7235). The Basic scheme is a different method that uses a Base64-encoded username:password string, which is not applicable here as a long-form token is provided.

Cisco Webex for Developers Documentation: The official documentation specifies the use of Bearer tokens for API calls. "To make an API call, you will need an access token. This token is passed with every API call in an HTTP header: Authorization: Bearer ."

Source: Cisco Webex for Developers, "Authentication"

URL: https://developer.webex.com/docs/api/getting-started#authentication

Internet Engineering Task Force (IETF) RFC 6750: This document defines the Bearer Token Usage for OAuth 2.0. Section 2.1 explicitly details the "Authorization Request Header Field" method as the primary way to transmit the token.

Source: IETF RFC 6750, "The OAuth 2.0 Authorization Framework: Bearer Token Usage," Section 2.1

URL: https://tools.ietf.org/html/rfc6750#section-2.1

Internet Engineering Task Force (IETF) RFC 7235: This standard defines the Authorization header field for HTTP/1.1, establishing it as the correct header for carrying authentication credentials.

Source: IETF RFC 7235, "Hypertext Transfer Protocol (HTTP/1.1): Authentication," Section 4.2

URL: https://tools.ietf.org/html/rfc7235#section-4.2

The logic for the answer remains the same but applied to all three locations.

1. HTTP Method: To create a new resource (a meeting, in this case), the standard and required HTTP method is POST. The http.request function in Node.js takes an options object to specify this.
2. Authentication Tag: The Webex XML API uses a <securityContext> element for authentication. The correct XML tag for a temporary authentication token is <sessionTicket>.
3. XML Syntax: Basic XML syntax requires that every opening tag (e.g., <sessionTicket>) has a corresponding closing tag (</sessionTicket>). Therefore, the same sessionTicket string must be used for both the opening and closing tags.

Cisco Webex Meetings XML API Reference Guide: This official vendor documentation specifies the required elements for API requests.

HTTP Method: The "XML API Basics" > "Sending a Request" section states that all XML API requests must be sent as an HTTP POST request.

Authentication: The "Security" > "Security Elements in Header" section details the element and explicitly lists as the element for the session ticket. (Direct URL: Webex XML API Documentation)

This XML request uses the Webex Meetings XML API to modify a user's settings.

• The <header> section identifies the requester. The <webExID> inside the <securityContext> must be the administrator performing the action, which is janedoe. Authentication is provided via a <sessionTicket>.
• The <body> section defines the operation. The bodyContent element's xsi:type attribute specifies the API call being made, which is SetUser for updating user information. The <webExID> inside the body identifies the target user whose settings are being changed, which is johndoe. The nested <personalMeetingRoom> element specifies the exact attribute (the hostPIN) to be updated.

Cisco Webex Meetings XML API Reference Guide: The official documentation for the SetUser operation details the required XML structure. It specifies that the administrator's webExID and sessionTicket are placed in the of the header, while the target user's webExID is placed in the body. It also confirms SetUser as the correct service type for modifying a user's PMR PIN. (See "Chapter 22: SetUser" in relevant API version guides).

IEEE Xplore Digital Library: Research papers on SOAP-based web service security, such as "Security in Web Services: A Survey," discuss the common pattern of using a header block for security context (authentication and authorization) and a body block for the message payload (the specific operation and its parameters). This aligns with the structure shown, separating Jane's credentials (header) from the action on John's account (body). (e.g., DOI: 10.1109/ICWS.2003.1214899).

sessionTicket: The <securityContext> element requires authentication. The value provided (AAABb6...) is a long, base64-encoded string characteristic of a session ticket obtained via a previous handshake, rather than a plaintext <password>.

meetingPassword: Within the <accessControl> element of a CreateMeeting request, the element used to define the password for the meeting is specified as <meetingPassword>.

1/13/2020 16:00:00: The Webex XML API requires date/time values in the specific format MM/DD/YYYY HH:MM:SS. The option "Jan 24..." is not a valid format for this XML schema.

text/xml: The DOMParser().parseFromString() method requires a MIME type argument. Since the Webex service being called is the XMLService and returns XML data, 'text/xml' is the correct MIME type to parse the response string into an XML Document.

result: The standard response to a Webex XML API request (such as CreateMeeting) includes a <header> containing a <response> block. The immediate success or failure status is located in the <result> element (e.g., <result>SUCCESS</result>).

Cisco DevNet (Official Documentation): Webex XML API Reference Guide. This documentation defines the schema for (listing sessionTicket as a valid child), (listing and ), and the required date format MM/DD/YYYY HH:MM:SS.

Mozilla Developer Network (MDN) Web Docs: DOMParser.parseFromString(). Confirming that the mimeType parameter must be a supported XML type like 'text/xml' or 'application/xml' for XML content, not JSON.

Cisco DevNet (Official Documentation): XML API Release Notes. Details the response structure where the outcome of a transaction is indicated by the tag within the response header.

The goal is to send a message to a specific room using the Webex Browser SDK. According to the official SDK documentation, the webex.messages object contains the methods for interacting with message resources. The create() method is used to post a new message to a room. This method accepts a message object as its argument, which must specify the destination room via the roomId property and the message content via the text (for plain text) or markdown property. The code snippet correctly retrieves the room.id and provides the string 'Hello World!' as the content.

Source: Webex for Developers - SDK Documentation

Details: The webex.messages.create() method is documented as the standard procedure for sending a message. The documentation specifies the required parameters for the message object, including roomId and text.

URL: https://developer.webex.com/docs/sdk-browser#webex-messages-create

Section: webex.messages.create(message)

A Webex Webhook only supplies minimal data (messageId, personEmail, roomId).

The bot must:

1. Ignore events it generated itself (data.personEmail === botEmail).

2. Use the Webex JS SDK messages.get(data.id) call to retrieve the full message.

3. Test whether the retrieved message.mentionedPeople array contains the bot’s own personId (webex.people.get('me')).

4. If mentioned, print message.text.

Option B performs these exact four steps with the Webex Node.js SDK; none of the other snippets both fetch the full message and verify the mention correctly.

1. Cisco DevNet – Webex Webhooks Guide

“Example Notification Payload” & note on limited fields (resource messages)

2023. https://developer.webex.com/docs/api/guides/webhooks

2. Cisco DevNet – Messages API

“GET /messages/{messageId}” Node example

2023. https://developer.webex.com/docs/api/v1/messages/get-message-details

3. Cisco Sample Code “webex-node-bot-example”

app.js lines 60-73: retrieving message

checking mentionedPeople

printing text. https://github.com/webex/webex-node-bot-example

(Approved sources: official Cisco Webex developer documentation and Cisco GitHub sample code.)

The Webex Compliance Events API notifies a compliance officer when content is created, updated, or deleted. The documented request pattern is:

GET /v1/events?resource=messages [&type=…].

Therefore the URI fragment that must replace line 20 so the code receives notices about non-compliant messages is “events?resource=messages”.

1. Cisco Webex for Developers – “Compliance Events”

section “List Events”

example: GET /v1/events?resource=messages&type=deleted (https://developer.webex.com/docs/compliance-events)

2. Cisco Webex for Developers – “Compliance Messages”

example: GET /v1/compliance/messages (https://developer.webex.com/docs/compliance-messages)