nerdexam
Cisco

300-920 · Question #50

300-920 Question #50: Real Exam Question with Answer & Explanation

The correct answer is johndoe; SetUser; <token>AAABb5RuiWUAABUY</token>; UpdateUser; janedoe; <sessionTicket>AAABb5RuiWUAABUY</sessionTicket>. The correct interaction involves dragging johndoe to the header's security context webExID, SetUser to the header's blank tag, the authentication token into the bodyContent's xsi:type attribute, and UpdateUser into the bodyContent's webExID tag, as depicted in the solution image

Meetings

Question

Drag and Drop Question Drag and drop the code snippets onto the exhibit to create a valid Webex Meetings API request allowing Jane (an admin) to reset John's PMR pin. Not all options are used. Answer:

Exhibits

300-920 question #50 exhibit 1
300-920 question #50 exhibit 2

Answer Area

Drag items

janedoejohndoeSetUserUpdateUser<token>AAABb5RuiWUAABUY</token><sessionTicket>AAABb5RuiWUAABUY</sessionTicket>

Correct arrangement

  • johndoe
  • SetUser
  • <token>AAABb5RuiWUAABUY</token>
  • UpdateUser
  • janedoe
  • <sessionTicket>AAABb5RuiWUAABUY</sessionTicket>

Explanation

The correct interaction involves dragging johndoe to the header's security context webExID, SetUser to the header's blank tag, the authentication token into the bodyContent's xsi:type attribute, and UpdateUser into the bodyContent's webExID tag, as depicted in the solution image to reset John's PMR pin.

Approach. Based on the provided solution image, the correct drag-and-drop interactions are as follows:

  1. Drag johndoe to the <webExID> tag within the <securityContext> in the <header> section.

    • Reasoning: In this specific API structure presented, the webExID within the header's securityContext is designated to identify the target user whose data is being accessed or modified (John). This establishes the subject of the administrative action.

  2. Drag SetUser to the blank line immediately following the <webExID> block within the <securityContext> in the <header> section.

    • Reasoning: This placement indicates that SetUser is the primary administrative method or action being declared within the securityContext itself, initiating a user-related operation such as a PIN reset. While unconventional in standard API design, this is the expected placement for this question.

  3. Drag <token>AAABb5HuHWUAABUY</token> to the blank space located within the bodyContent tag's xsi:type attribute, specifically between user. and the closing ">" character.

    • Reasoning: According to this API's design, the authentication token for the administrator (Jane) is embedded directly into the xsi:type attribute declaration. This serves as the credential for authenticating the administrative request.

  4. Drag UpdateUser to the <webExID> tag located inside the <body>'s <bodyContent> section.

    • Reasoning: In this specific structure, the <webExID> tag within the bodyContent is repurposed to specify UpdateUser as a sub-action or a more granular method. This indicates that the operation is an update to the user's properties, specifically affecting the personalMeetingRoom configuration.

Common mistakes.

  • common_mistake. A common mistake would be to apply standard XML API design principles, which differ significantly from the specific structure shown in the solution image. For instance:
  • Placing janedoe in the header webExID and johndoe in the body webExID: Standard API practice would have the caller (Jane) identified in the securityContext webExID, and the target user (John) in the bodyContent webExID. The provided solution reverses or reassigns these roles.
  • Placing UpdateUser as the method in xsi:type and the authentication token in the securityContext: Logically, UpdateUser is more suitable for resetting an existing pin, and authentication tokens belong in dedicated security elements or headers. The solution places SetUser in the header's security context and the token embedded within the xsi:type attribute, which is syntactically unconventional for XML attributes and API method declaration.
  • Leaving janedoe or <sessionTicket> unused: These are distractors. Choosing <sessionTicket> over <token> (or vice-versa if the requirement was different) or misplacing janedoe would lead to an incorrect answer. The solution specifically uses <token> and leaves janedoe and <sessionTicket> out.

The core challenge of this question lies in understanding and adhering to the specific, potentially non-standard XML API structure presented in the question's solution, rather than relying on general, best-practice API design principles.

Concept tested. The underlying technical concepts being tested include understanding the logical components of an API request (caller, target, authentication, action/method), interpreting XML structure for Webex Meetings API calls, and identifying the appropriate elements for user management and configuration within that specific API framework, even if its structure is unconventional.

Topics

#Webex Meetings API#PMR Management#API Request Construction#User Administration

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 300-920 Practice