200-901 Understanding and Using APIs Practice Question
A developer is using the Cisco Meraki Dashboard API to update the configuration of a wireless SSID. The API requires a PUT request to /networks/{networkId}/wireless/ssids/{number}. Which HTTP header is mandatory to include the API key for authentication?
⚠ Common exam trap
The trap here is assuming that all Cisco APIs use the same authentication header, when Meraki specifically uses a custom X-Cisco-Meraki-API-Key header.
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
✓
X-Cisco-Meraki-API-Key
The Meraki Dashboard API requires the API key to be sent in the X-Cisco-Meraki-API-Key header. This custom header is the only accepted method for authentication. Other headers like Authorization or X-Auth-Token are used by different Cisco APIs and will not work with Meraki. Content-Type is for the request body, not authentication.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Content-Type: application/json
Why it's wrong here
Content-Type specifies the format of the request body and is important for PUT requests with JSON payloads, but it is not used for authentication. The question asks for the mandatory header to include the API key. While Content-Type is often required, it does not carry the API key, so it alone would not authenticate the request.
- ✗
X-Auth-Token
Why it's wrong here
X-Auth-Token is used by other Cisco APIs such as Catalyst Center, but not by the Meraki Dashboard API. Meraki requires its own custom header. Using X-Auth-Token would not authenticate the request and would likely return an error indicating missing or invalid API key, preventing the SSID update.
- ✓
X-Cisco-Meraki-API-Key
Why this is correct
The Cisco Meraki Dashboard API uses a custom header named X-Cisco-Meraki-API-Key to authenticate requests. The API key generated in the Meraki Dashboard must be included in this header for all API calls. Without it, the server returns a 401 Unauthorized error. This header is specific to Meraki and is the correct way to authenticate.
- ✗
Authorization: Bearer <token>
Why it's wrong here
While many REST APIs use the Authorization header with a Bearer token, the Meraki Dashboard API does not. It requires the API key in a custom header. Using Authorization: Bearer would be incorrect and result in an authentication failure, as the Meraki API does not recognize this scheme for its dashboard API.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Cisco exam blueprint
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.