When you send credentials with a request, which header is described as carrying authentication information in the material?

When you send credentials with a request, which header is described as carrying authentication information in the material?

• A. Authentication
• B. Authorization
• C. Cookie
• D. X-API-Key

Answer: (A)

When credentials are sent with a request, the header responsible for delivering that proof of identity is described as carrying authentication information. This header’s purpose is to convey the data that proves who the client is, so the server can verify identity and determine what the client is allowed to do. In practice, many systems use a header named for the action of proving identity, and the value (such as a token or encoded credentials) is what the server checks to authenticate the user. While other headers like Authorization (the standard in many implementations), Cookie (for session state), or X-API-Key (for API keys) can also carry credentials, the material identifies the header in question specifically as the one that carries authentication information, making it the best match for this scenario.

When credentials are sent with a request, the header responsible for delivering that proof of identity is described as carrying authentication information. This header’s purpose is to convey the data that proves who the client is, so the server can verify identity and determine what the client is allowed to do. In practice, many systems use a header named for the action of proving identity, and the value (such as a token or encoded credentials) is what the server checks to authenticate the user. While other headers like Authorization (the standard in many implementations), Cookie (for session state), or X-API-Key (for API keys) can also carry credentials, the material identifies the header in question specifically as the one that carries authentication information, making it the best match for this scenario.