mediumMultiple ChoiceObjective-mapped
200-901 Practice Question: A developer is using the Meraki Dashboard API to…
A developer is using the Meraki Dashboard API to programmatically change the SSID name of a wireless network. The developer successfully authenticates with an API key and sends a PUT request to /networks/{networkId}/wireless/ssids/{number} with a JSON body containing the updated name. The API returns a 200 OK response, but the SSID name does not change in the Meraki Dashboard. The developer double-checks the networkId and SSID number, and they are correct. The developer also confirms that the API key has full write access to the network. What additional step is most likely required?
⚠ Common exam trap
Many candidates mistakenly believe that a 200 OK response from a Meraki PUT request does not mean the configuration was applied and that a separate provisioning step or PATCH request is needed. In the Meraki Dashboard API, PUT updates the SSID immediately.
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
✓
Log out of the Meraki Dashboard and re-login to see the change.
The Meraki Dashboard API uses PUT to update SSID settings. A 200 OK response means the update was accepted and applied immediately; no separate provisioning call or PATCH request is required. If the SSID name still appears unchanged in the dashboard UI, the most likely remaining step is to refresh or log out and back in to display the already-applied update.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
After the PUT request, send a POST request to /networks/{networkId}/wireless/ssids/{number}/provision to apply the change.
Why it's wrong here
Meraki does not require a separate POST to /provision to apply SSID name changes; the PUT request itself applies the update.
- ✗
Use a PATCH request instead of PUT to update the SSID.
Why it's wrong here
The Meraki Dashboard API uses PUT, not PATCH, to update SSID settings.
- ✓
Log out of the Meraki Dashboard and re-login to see the change.
Why this is correct
If the API returned 200 OK, the dashboard UI is likely stale; logging out and back in can display the change that was already applied via PUT.
- ✗
Regenerate the API key and try again with the new key.
Why it's wrong here
A 200 OK response indicates the API key worked and the request was accepted; regenerating the key would not affect an already accepted update.
Go deeper
Related to this question
About these practice questions
This 200-901 question is part of Courseiva's 989-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.