nerdexam
Cisco

350-901 · Question #28

The task is to create a new collaboration space with a user and team leads on-demand via a Linux terminal command. Drag and drop the code snippets from the left onto the numbers on the right that…

This question tests knowledge of the Cisco Webex REST API, specifically how to programmatically create a collaboration space (room) and add members to it using curl commands in a Linux terminal. It is commonly assessed in Cisco DevNet Associate/Professional certification exams.

Using APIs

Question

The task is to create a new collaboration space with a user and team leads on-demand via a Linux terminal command. Drag and drop the code snippets from the left onto the numbers on the right that match the missing sections in the exhibit to complete the script. Not all code snippets are used. The specific exhibit (script/code with numbered placeholders <item 1> to <item 5>) for this drag-and-drop task is not provided in the current context. Available options for dragging (from the Answer Area on page 4): application/xml, application/json, name, userName, title, personEmail, /members, /memberships, /rooms, /spaces.

Exhibit

350-901 question #28 exhibit

Explanation

This question tests knowledge of the Cisco Webex REST API, specifically how to programmatically create a collaboration space (room) and add members to it using curl commands in a Linux terminal. It is commonly assessed in Cisco DevNet Associate/Professional certification exams.

Approach. The correct approach uses the Webex REST API with two sequential curl POST calls. First, POST to /rooms (the Webex API endpoint for creating spaces) with a JSON body containing the title field to name the new space, using Content-Type: application/json. Second, POST to /memberships (not /members) with personEmail to add each user or team lead to the newly created room by their email address. The placeholders map as follows: (1) /rooms - creates the space, (2) application/json - required Content-Type header, (3) title - JSON field for the space name, (4) /memberships - adds users to the space, (5) personEmail - identifies the invitee by email. Options like application/xml, userName, name, /spaces, and /members are distractors; Webex API uses JSON not XML, title not name for rooms, personEmail not userName, and /memberships not /members as the correct endpoint.

Concept tested. Cisco Webex REST API - creating rooms via POST /rooms and managing membership via POST /memberships using curl with JSON payloads (DevNet Associate exam objective: consume REST APIs in application development)

Reference. Cisco Webex REST API Developer Documentation: https://developer.webex.com/docs/api/v1/rooms and https://developer.webex.com/docs/api/v1/memberships

Topics

#API interaction#Cisco Webex API#Linux command line#JSON data format

Community Discussion

No community discussion yet for this question.

Full 350-901 Practice