350-201 Question 271
Single answerYou are tasked with securing API access for a Cisco SecureX integration. The security requirement is to use a mechanism that does not require embedding user credentials into the request but still allows revocation of access without affecting other API clients. Which authentication mechanism should you use?
- A
Basic Authentication
- B
Custom Token
- C
API Key
- D
OAuth 2.0
Show answer and explanation
Correct answer: B
Explanation
Custom Token authentication is the most appropriate mechanism in this scenario because it provides a secure, unique token for each client that can be easily revoked without affecting other clients. Basic Authentication and API Key mechanisms do not meet the security requirements due to their static nature and potential for embedding sensitive information, while OAuth 2.0 is beyond the scope of the stated requirements.
- A. Incorrect.
Basic Authentication requires embedding user credentials (username and password) in the request headers, which is less secure and does not meet the requirement of avoiding embedding user credentials.
- B. Correct.
Custom Token authentication provides a unique token that can be generated and revoked independently for each API client, meeting the security requirements specified in the scenario.
- C. Incorrect.
API Key authentication often involves embedding a static key into requests, but it lacks mechanisms for token revocation per client, which does not fully meet the requirement in this scenario.
- D. Incorrect.
OAuth 2.0 is a robust authentication framework but was not specified as a requirement or option in this scenario, making it unrelated to the solution.