mediumMultiple Choice
200-901 Practice Question: A developer is using the Cisco Webex Teams API to…
A developer is using the Cisco Webex Teams API to create a room and add members. The API returns a 400 error. What is the most likely cause?
⚠ Common exam trap
Cisco often tests the distinction between HTTP 4xx status codes, leading candidates to confuse authentication errors (401) with client-side request errors (400) when the actual issue is missing or malformed data.
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
✓
Missing required fields
A 400 Bad Request error from the Cisco Webex Teams API indicates that the server cannot process the request due to a client-side error, most commonly missing required fields in the request body. When creating a room, the API requires a 'title' field; omitting it or sending an empty value triggers a 400 response. This is distinct from authentication or network issues, which produce different HTTP status codes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Invalid access token
Why it's wrong here
A 400 signals a malformed request body or invalid field, whereas an invalid token yields 401 Unauthorized. The token is tempting because authentication failures are common, and a 401 would indeed point here, but the stem's status code rules it out.
- ✓
Missing required fields
Why this is correct
A 400 response signals a malformed or semantically invalid request body, typically because mandatory attributes such as the room title were omitted. The Webex Teams API validates payloads before processing, so missing required fields is the most likely cause of the stem's error.
- ✗
Network connectivity issue
Why it's wrong here
Connectivity failures surface as timeouts or connection errors, never as an HTTP 400 from the server. It tempts because network faults are frequent, and a timeout or DNS failure would indeed be the culprit, but a returned status code proves the request reached Webex.
- ✗
Room name already exists
Why it's wrong here
Webex permits duplicate room titles, so a repeated name returns 200, not 400. The option tempts because unique-name constraints are common in other APIs, and a 409 Conflict would fit a genuine uniqueness rule, but Webex enforces none.
Go deeper
Related to this question
About these practice questions
This 200-901 question is part of Courseiva's 975-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.