A company wants to adopt Webex Teams as a messaging platform and use REST APIs to automate the creation of teams and rooms. Which sequence of REST API requests is needed to create and populate a new…

Question

Options

• APOST /teams, POST /memberships, POST /rooms
• BPOST /teams, POST /people, POST /rooms
• CPOST /teams, POST /team/memberships, POST /rooms
• DPOST /teams, POST /team/memberships, POST /rooms, POST /memberships

• A
  5% (2)
• B
  80% (32)
• C
  13% (5)
• D
  3% (1)

Explanation

Important note: The stated correct answer (B) appears to be incorrect based on Webex Teams REST API behavior. This looks like a Cisco DevNet exam question where D is the accurate answer.

POST /people creates or invites a user to the organization - it does not add them to a team or room. To "create and populate" both a team and a room, you need four calls: POST /teams to create the team, POST /team/memberships to add members to that team, POST /rooms to create the room scoped to that team, and POST /memberships to add members to the room specifically.

Why the distractors fail:

• A uses POST /memberships (room membership) but skips POST /team/memberships - the team itself never gets populated.
• B uses POST /people, which creates users in the org, not membership in a team - it populates neither the team nor the room.
• C adds team membership but skips adding members to the room, so the room is created but not populated.

Memory tip: Think of the two containers (team, room) each needing their own membership call - team first via /team/memberships, room second via /memberships. The full flow is: create team → fill team → create room → fill room (D).

If your study material lists B as correct, I'd recommend verifying against the Cisco DevNet documentation or an updated source - this may be a typo or error in the answer key.

No community discussion yet for this question.