Quick Answer
The correct answer is API key in HTTP header and HTTP Basic Authentication, as these are the two most common authentication methods used when interacting with Cisco APIs. HTTP Basic Authentication works by sending a base64-encoded username:password string in the Authorization header, while API keys are passed in a custom HTTP header like X-Cisco-Meraki-API-Key for Meraki or similar headers for Cisco DNA Center. On the Cisco DevNet Associate 200-901 exam, this topic tests your understanding of stateless, simple authentication mechanisms that many Cisco platforms support. A common trap is confusing API keys with OAuth tokens or assuming all Cisco APIs require complex flows—remember that for basic REST interactions, these two methods are often sufficient. Memory tip: think "Base64 for Basic, Header for Key" to recall that HTTP Basic uses the Authorization header with encoded credentials, while API keys ride in a custom header name.
This 200-901 practice question tests your understanding of cisco platforms and development. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
Which TWO are common authentication methods used when interacting with Cisco APIs?
Client certificate exchange
Why wrong: Not commonly used with Cisco APIs.
HTTP Basic Authentication
Used with RESTCONF over HTTPS.
API key in HTTP header
Common in Meraki and Webex APIs.
LDAP bind credentials
Why wrong: LDAP is for directory services, not typical for API auth.
SNMPv3 authentication
Why wrong: SNMP is separate from REST API auth.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
HTTP Basic Authentication
HTTP Basic Authentication (option B) is a common method for authenticating to Cisco APIs, where the client sends a base64-encoded username:password string in the Authorization header. API keys in HTTP headers (option C) are also widely used, especially with REST APIs like Cisco DNA Center or Meraki, where the key is passed in a custom header (e.g., 'X-Cisco-Meraki-API-Key'). Both are simple, stateless mechanisms supported by many Cisco platforms.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Client certificate exchange
Why it's wrong here
Not commonly used with Cisco APIs.
HTTP Basic Authentication
Why this is correct
Used with RESTCONF over HTTPS.
Related concept
Read the scenario before looking for a memorised answer.
API key in HTTP header
Why this is correct
Common in Meraki and Webex APIs.
Related concept
Read the scenario before looking for a memorised answer.
LDAP bind credentials
Why it's wrong here
LDAP is for directory services, not typical for API auth.
SNMPv3 authentication
Common exam traps
Cisco often tests the distinction between authentication methods used for API access versus those used for network device management (like SNMPv3 or LDAP), leading candidates to confuse management-plane authentication with API-level authentication.
Detailed technical explanation
HTTP Basic Authentication sends credentials in plaintext (base64 is not encryption), so it should always be used over HTTPS to avoid interception. API keys are often generated per user or application and can be revoked independently, providing granular access control. Cisco's DevNet sandboxes and production APIs (e.g., Webex Teams, DNA Center) frequently use API keys in headers, while older or simpler APIs may still rely on Basic Auth, but both are stateless and do not require session management.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Cisco Platforms and Development — study guide chapter
Learn the concepts, then practise the questions
Cisco Platforms and Development 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise 200-901 questions linked to Software Development and Design.
Practise 200-901 questions linked to Understanding and Using APIs.
Practise 200-901 questions linked to Cisco Platforms and Development.
Practise 200-901 questions linked to Application Deployment and Security.
Practise 200-901 questions linked to Infrastructure and Automation.
Practise 200-901 questions linked to Network Fundamentals.
Practise 200-901 questions linked to 200-901 fundamentals.
Practise 200-901 questions linked to 200-901 scenario.
Practise 200-901 questions linked to 200-901 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Cisco Platforms and Development — This question tests Cisco Platforms and Development — Read the scenario before looking for a memorised answer..
The correct answer is: HTTP Basic Authentication — HTTP Basic Authentication (option B) is a common method for authenticating to Cisco APIs, where the client sends a base64-encoded username:password string in the Authorization header. API keys in HTTP headers (option C) are also widely used, especially with REST APIs like Cisco DNA Center or Meraki, where the key is passed in a custom header (e.g., 'X-Cisco-Meraki-API-Key'). Both are simple, stateless mechanisms supported by many Cisco platforms.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 11, 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.