easyMultiple Select
200-901 Practice Question: Which TWO are common authentication methods used…
Which TWO are common authentication methods used when interacting with Cisco APIs?
⚠ Common exam trap
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.
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
✓
HTTP Basic Authentication
HTTP Basic Authentication (B) is a common method for Cisco APIs, where the client sends a Base64-encoded username and password in the Authorization header, often used with Cisco DNA Center, Meraki, and other REST APIs. API key in HTTP header (C) is also widely used, for example Cisco Meraki uses an X-Cisco-Meraki-API-Key header, and Cisco Intersight uses API keys for authentication. Client certificate exchange (A) is not typically classified as a common authentication method for Cisco APIs, though it can be used for mutual TLS in some contexts. LDAP bind credentials (D) are used for directory authentication, not directly for Cisco API authentication. SNMPv3 authentication (E) is for network management via SNMP, not for Cisco API interactions.
Answer analysis
Option-by-option breakdown
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
HTTP Basic Authentication sends a base64-encoded username and password in the request header, satisfying the stem's requirement for a common Cisco API authentication method. It is natively supported by RESTCONF and REST APIs on Catalyst and DNA Center platforms, though it must run over HTTPS to protect credentials.
- ✓
API key in HTTP header
Why this is correct
Placing an API key in an HTTP header lets the client authenticate each REST call without transmitting a username and password, meeting the stem's requirement for a common Cisco API authentication method. Cisco Meraki and Webex APIs use this header-based key scheme for programmatic access.
- ✗
LDAP bind credentials
Why it's wrong here
LDAP bind credentials verify a directory user, not an API caller; Cisco APIs expect tokens, basic credentials, or certificates rather than a directory bind. It is tempting because LDAP is a familiar authentication protocol, and it would be correct for authenticating users to directory-backed applications and services.
- ✗
SNMPv3 authentication
Why it's wrong here
SNMPv3 authentication secures network management polling and traps, not API request authentication, so it cannot validate an API client's identity. It is tempting because SNMPv3 does provide real authentication, and it would be correct for monitoring Cisco devices rather than calling their REST or RPC APIs.
Go deeper
Related to this question
About these practice questions
One of 975 original 200-901 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.