Drag and Drop Question Drag and drop the components to create the authentication header used for the Webex Teams API. Not all options are used. Answer:

Question

Exhibit

Answer Area

Explanation

The question requires assembling an HTTP Authorization header for Webex Teams API, which uses OAuth 2.0 Bearer tokens, by dragging the correct components into the specified format: Authorization: Bearer <access_token>.

Approach. The correct interaction is to drag 'Authorization' into the first box, 'Bearer' into the second box, and 'BH782kjh-2jkhmnb3rlkjnj3lkjnm3klj3' into the third box. This constructs the standard HTTP Authorization header for Webex Teams API, which utilizes OAuth 2.0 Bearer token authentication. The correct format for a Bearer token header is 'Authorization: Bearer <access_token>', where 'BH782kjh-2jkhmnb3rlkjnj3lkjnm3klj3' represents the actual access token provided in the options.

Common mistakes.

• common_mistake. A common mistake is using 'Authentication' instead of 'Authorization' for the header field name, which is incorrect as 'Authorization' is the standard HTTP header for credentials. Another mistake would be to use 'Basic' as the authentication scheme, or 'admin:Password12345!' as the credential, as these relate to Basic authentication, which uses Base64 encoded username:password, not Bearer token authentication used by Webex Teams API. Using 'Token' instead of the specific token string 'BH782kjh-2jkhmnb3rlkjnj3lkjnm3klj3' would also be incorrect because the question asks to 'create' the header, implying with the actual token value provided, not a generic placeholder like 'Token' which was shown in the template but not meant to be used when a specific token is available.

Concept tested. HTTP Authorization header structure, specifically OAuth 2.0 Bearer token authentication, and its distinction from other authentication schemes like Basic authentication.

No community discussion yet for this question.