Which REST API authentication method is explicitly supported according to the material?

Which REST API authentication method is explicitly supported according to the material?

• A. Token-based authentication
• B. Basic authentication
• C. OAuth only
• D. No authentication required

Answer: (A)

Token-based authentication is the method described as supported for REST API access. In this approach, you obtain a token from an authentication service and include it with each API request, typically in the Authorization header as a bearer token. This lets the service verify identity securely without sending a username and password every time, and it supports token lifetimes and revocation for safer automation. Basic authentication would require sending credentials with every call, which the material doesn’t emphasize as the supported approach. OAuth is a standard option but the material highlights token-based access as the supported mechanism, not OAuth-only. No authentication would leave the API unprotected, which is incompatible with REST API security.

Token-based authentication is the method described as supported for REST API access. In this approach, you obtain a token from an authentication service and include it with each API request, typically in the Authorization header as a bearer token. This lets the service verify identity securely without sending a username and password every time, and it supports token lifetimes and revocation for safer automation. Basic authentication would require sending credentials with every call, which the material doesn’t emphasize as the supported approach. OAuth is a standard option but the material highlights token-based access as the supported mechanism, not OAuth-only. No authentication would leave the API unprotected, which is incompatible with REST API security.