- A
Provide username and password in the Authorization header with Basic auth
Why wrong: Basic auth is not supported; API keys are used.
- B
Use OAuth2 client credentials grant and pass a bearer token
Why wrong: Meraki does not support OAuth2; it uses API keys.
- C
Include an API key in the X-Cisco-Meraki-API-Key header
Meraki API uses a static API key in the request header for authentication.
- D
Generate a JSON Web Token (JWT) signed with a shared secret
Why wrong: Meraki does not use JWT; the API key is a simple string.
200-901 Infrastructure and Automation Practice Question
This 200-901 practice question tests your understanding of infrastructure and automation. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An organization wants to automate the deployment of wireless configurations across multiple Meraki networks using the Meraki Dashboard API. What authentication method should the developer use in the API requests?
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
Include an API key in the X-Cisco-Meraki-API-Key header
The Meraki Dashboard API uses a simple API key for authentication, not OAuth2 or JWT. The key must be included in the `X-Cisco-Meraki-API-Key` header of every request. This is the only supported method for authenticating with the Meraki API, as documented by Cisco Meraki.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Provide username and password in the Authorization header with Basic auth
Why it's wrong here
Basic auth is not supported; API keys are used.
- ✗
Use OAuth2 client credentials grant and pass a bearer token
Why it's wrong here
Meraki does not support OAuth2; it uses API keys.
- ✓
Include an API key in the X-Cisco-Meraki-API-Key header
Why this is correct
Meraki API uses a static API key in the request header for authentication.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Generate a JSON Web Token (JWT) signed with a shared secret
Why it's wrong here
Meraki does not use JWT; the API key is a simple string.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that all REST APIs use OAuth2 or Basic Auth, but the Meraki API specifically uses a custom header-based API key, which candidates may overlook in favor of more common authentication methods.
Detailed technical explanation
How to think about this question
The Meraki API key is a static, pre-generated token tied to a Meraki dashboard administrator account. It is passed in the `X-Cisco-Meraki-API-Key` header, and the API validates it against the organization's permissions. Unlike OAuth2, there is no token refresh or expiration, so the key must be kept secure and rotated manually if compromised. This design simplifies automation but requires careful key management.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A junior network technician can log in to a core router but cannot reach the enable prompt or configuration mode. The AAA server is authenticating the login — but the authorisation policy only grants privilege level 1, not 15. Authentication (who you are) is working; authorisation (what you can do) is not.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Infrastructure and Automation — study guide chapter
Learn the concepts, then practise the questions
- →
Infrastructure and Automation practice questions
Targeted practice on this topic area only
- →
All 200-901 questions
505 questions across all exam domains
- →
Cisco DevNet Associate 200-901 study guide
Full concept coverage aligned to exam objectives
- →
200-901 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related 200-901 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Software Development and Design practice questions
Practise 200-901 questions linked to Software Development and Design.
Understanding and Using APIs practice questions
Practise 200-901 questions linked to Understanding and Using APIs.
Cisco Platforms and Development practice questions
Practise 200-901 questions linked to Cisco Platforms and Development.
Application Deployment and Security practice questions
Practise 200-901 questions linked to Application Deployment and Security.
Infrastructure and Automation practice questions
Practise 200-901 questions linked to Infrastructure and Automation.
Network Fundamentals practice questions
Practise 200-901 questions linked to Network Fundamentals.
200-901 fundamentals practice questions
Practise 200-901 questions linked to 200-901 fundamentals.
200-901 scenario practice questions
Practise 200-901 questions linked to 200-901 scenario.
200-901 troubleshooting practice questions
Practise 200-901 questions linked to 200-901 troubleshooting.
Practice this exam
Start a free 200-901 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this 200-901 question test?
Infrastructure and Automation — This question tests Infrastructure and Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Include an API key in the X-Cisco-Meraki-API-Key header — The Meraki Dashboard API uses a simple API key for authentication, not OAuth2 or JWT. The key must be included in the `X-Cisco-Meraki-API-Key` header of every request. This is the only supported method for authenticating with the Meraki API, as documented by Cisco Meraki.
What should I do if I get this 200-901 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.