Cisco Platforms and Development →mediumMultiple Select

200-901 Cisco Platforms and Development Practice Question

A developer is building a Python application that uses the Cisco Webex Teams REST API to manage memberships. The application must add a person to a space and later list the members of that space. Which two HTTP methods and endpoints should the application use? (Choose two.)

⚠ Common exam trap

The trap here is using the rooms endpoint to manage members, when membership creation and listing actually belong to the memberships resource.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

POST https://webexapis.com/v1/memberships with a JSON body containing roomId and personEmail

Webex Teams exposes membership management through the memberships resource. Creating a membership uses POST with roomId and personEmail in the body, while listing members uses GET with the roomId query parameter. The rooms resource is for space metadata, and PUT is for updating an existing membership, so neither fits the required add-and-list workflow.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
POST https://webexapis.com/v1/memberships with a JSON body containing roomId and personEmail
Why this is correct
The memberships resource is the correct endpoint for adding a person to a space. A POST request with roomId and personEmail in the JSON body creates the membership, and the API returns the new membership object including its ID. This matches the requirement to add a person to a space programmatically.
✓
GET https://webexapis.com/v1/memberships?roomId={roomId}
Why this is correct
Listing members of a space is done by issuing a GET to the memberships resource with the roomId query parameter. The response contains an array of membership objects with personEmail, personId, and other details. This is the documented way to retrieve the members of a specific space.
✗
POST https://webexapis.com/v1/rooms with a JSON body containing title and personEmail
Why it's wrong here
Posting to rooms creates a new space and can optionally include the first member, but it does not add a person to an existing space. Since the scenario requires adding a member to an existing space identified by roomId, this endpoint is incorrect. The memberships resource is the proper target for that operation.
✗
PUT https://webexapis.com/v1/memberships with a JSON body containing roomId and personEmail
Why it's wrong here
PUT is used to update an existing membership, for example to change whether a person is a moderator. It is not the method for creating a new membership, because the API requires POST for creation. Sending PUT with roomId and personEmail would not add the person and would likely return an error or update the wrong resource.
✗
GET https://webexapis.com/v1/rooms?roomId={roomId}
Why it's wrong here
The rooms resource returns information about the space itself, such as its title and type, not the list of members. Passing roomId as a query parameter to rooms is not how membership listing works; the memberships resource must be used instead. This call would not return the people in the space.

Go deeper

200-901 Cisco Platforms and Development Practice Question

Why each option matters

Option-by-option breakdown

Related to this question