While working with the Webex API, on an application that uses end-to-end encryption, a webhook has been received. What must be considered to read the message?
A.
Webhook information cannot be used to read the message because of end-to-end encryption. The API key is needed to decrypt the message.
B.
Webhook returns the full unencrypted message. Only the body is needed to query the API.
C.
Webhook returns a hashed version of the message that must be unhashed with the API key.
D.
Webhook returns message identification. To query, the API is needed for that message to get the decrypted information.
D : room messages are considered sensitive information and since Webex initiated the request to your backend, it did not have your Access Token with which to decrypt the message. In order to get the sensitive information, your app needs to use the resource id to fetch the full resource. Using the above messages example, your app could fetch the complete message object along with the text by doing an authenticated (via your Bearer Token) GET request to /messages/{id}
https://developer.webex.com/docs/api/guides/webhooks
Using the Data Property
The webhook's data property contains the JSON representation of the resource event that triggered the webhook. For example, if you created a webhook that triggers when messages are created (i.e. posted into a room), then the data property will contain the JSON representation for a message resource, as specified in the Messages API documentation. Likewise, if you created a webhook that triggers when telephony_calls are created (i.e. a call is originated or received), then the data property will contain the JSON representation for a telephony_calls resource, as specified in the Call-Control API documentation.
If the webhook's resource event contains sensitive data, the data property will only contain “metadata” about the event. See "Handling Sensitive Data" below for more information about how to retrieve the entire resource.
Handling Sensitive Data
Webex encrypts sensitive room content such as titles and message text using keys only available to the members of that room. This means that not even the Webex operations team can read your messages, making it one of the most secure communications platforms on the planet. This level of security has a subtle impact on webhooks.
You'll notice in the above message webhook example that the text property is missing. That's because room messages are considered sensitive information and since Webex initiated the request to your backend, it did not have your Access Token with which to decrypt the message. In order to get the sensitive information, your app needs to use the resource id to fetch the full resource. Using the above messages example, your app could fetch the complete message object along with the text by doing an authenticated (via your Bearer Token) GET request to /messages/{id} as shown below:
This section is not available anymore. Please use the main Exam Page.350-901 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
tswinn
Highly Voted 1 year, 7 months agokristotof
Highly Voted 1 year, 5 months agoQuiShong
Most Recent 10 months, 2 weeks agoferock
11 months, 3 weeks agoferock
11 months, 3 weeks ago__al__
1 year agozzrdxakpbkiswhvsyu
1 year, 6 months ago