200-901 Cisco Platforms and Development Practice Question

A developer wants to retrieve the current user's Webex profile information. Which API endpoint should be called?

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

✓

GET /v1/people/me

The /v1/people/me endpoint returns details about the authenticated user.

Answer analysis

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

✗
GET /v1/people
Why it's wrong here
GET /v1/people returns a directory listing of people, not the authenticated user's own profile; the correct endpoint is GET /v1/people/me. It is tempting because it is the people resource, and would suit an admin searching or listing users across the organisation.
✓
GET /v1/people/me
Why this is correct
GET /v1/people/me returns the authenticated user's own profile, resolving the caller's identity from the OAuth token rather than requiring an explicit person ID. This satisfies the stem's requirement to retrieve the current user's Webex profile information without knowing or supplying their identifier in advance.
✗
GET /v1/memberships/me
Why it's wrong here
GET /v1/memberships/me returns the current user's room membership records, not profile attributes such as display name or email. It is tempting because Webex memberships do expose a "me" alias for the authenticated user, and this endpoint is the right call when listing which spaces that user belongs to.
✗
GET /v1/rooms/me
Why it's wrong here
The rooms resource returns room (space) records, so /rooms/me does not expose profile attributes such as display name or email. GET /v1/people/me returns the authenticated user's profile. Rooms would be correct when retrieving details of a specific Webex space.

Go deeper