mediumMultiple Choice
200-901 Practice Question: Is using the Cisco Meraki API to retrieve a list…
A network engineer is using the Cisco Meraki API to retrieve a list of SSIDs for a specific network. The API returns an HTTP 200 status but an empty array for the SSIDs. Which of the following is the most likely cause?
⚠ Common exam trap
Cisco often tests the misconception that an HTTP 200 always means data exists, but the trap here is that a successful API response can legitimately return an empty array when the resource has no configured items.
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
✓
The network exists but has no SSIDs configured.
An HTTP 200 status indicates the request was successfully processed by the Meraki API, meaning the API key, network ID, and request format were all valid. An empty array for SSIDs specifically means the network exists and the API queried it correctly, but no SSIDs have been configured on that network. This is the expected behavior when a network has no wireless profiles defined.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The network exists but has no SSIDs configured.
Why this is correct
HTTP 200 confirms the request succeeded and the network identifier is valid; an empty JSON array is a legitimate response, not an error. The SSID collection for that network simply contains no entries, so no configuration change or authentication fix is required.
- ✗
The network ID is incorrect.
Why it's wrong here
A wrong network ID returns HTTP 404 Not Found rather than 200 with an empty array, so the endpoint itself would fail before any SSID listing. It tempts because ID mistakes are common in Meraki API calls, and correcting the ID is right when the response indicates the network does not exist.
- ✗
The API key is invalid.
Why it's wrong here
An invalid API key returns HTTP 401 Unauthorized, not 200 with an empty array, so authentication cannot explain this response. It tempts because key problems are a frequent Meraki API issue, and rotating or regenerating keys is the right fix when calls are rejected outright.
- ✗
The request body is malformed.
Why it's wrong here
A GET request to list SSIDs carries no body, so a malformed body cannot cause an empty array; malformed bodies matter for POST/PUT payloads, where they trigger 400 errors. It tempts because request-body validation is a common API failure, but here the 200 status confirms the call itself succeeded.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.