nerdexam
Cisco

300-920 · Question #4

Which list of API calls must be made to provision 50 new Webex Room devices for an organization?

The correct answer is A. POST to /places with `displayName', POST the returned `placeId' to /devices/. Option A reflects the correct two-step provisioning workflow: first create a logical "place" (the room location) by POSTing to /places with a displayName, then register the device to that location by POSTing the returned placeId to /devices/. This is the standard Webex API…

Devices

Question

Which list of API calls must be made to provision 50 new Webex Room devices for an organization?

Options

  • APOST to /places with displayName', POST the returned placeId' to /devices/
  • BPOST displayName' to /places, POST the returned placeId' to /devices/activationCode
  • CPOST to /licenses, POST the returned licneseId' and a specified displayName' to /devices
  • DPOST to /licenses, POST displayName' to /places, POST licensed' and placeId' to /devices

How the community answered

(19 responses)
  • A
    79% (15)
  • B
    16% (3)
  • C
    5% (1)

Explanation

Option A reflects the correct two-step provisioning workflow: first create a logical "place" (the room location) by POSTing to /places with a displayName, then register the device to that location by POSTing the returned placeId to /devices/. This is the standard Webex API pattern - the place must exist before a device can be tied to it.

Option B fails because it uses /devices/activationCode rather than /devices/ - activation codes are for a different flow (user-driven device activation), not programmatic provisioning. Option C is wrong because license assignment is handled separately (or automatically via organization settings) and is not a required step in the device provisioning sequence; also, it skips the /places step entirely. Option D is similarly wrong for including /licenses as a prerequisite step and then passing an incorrect licensed parameter to /devices, which doesn't match the actual API schema.

Memory tip: Think "Place before Device, id carries the link" - you always create the Place first, grab the placeId from the response, and carry it into the Devices call. If an answer skips /places or swaps in /activationCode or /licenses, it's wrong.

Topics

#Room Device Provisioning#Places API#Devices API#API sequencing

Community Discussion

No community discussion yet for this question.

Full 300-920 Practice