CCNP Collaboration 300-830 Reddit Questions

A REST PUT request that modifies a contact-service queue is an administrative write operation. Cisco's Webex Contact Center API model uses scopes to separate read-only access from configuration changes. The endpoint /organization/{orgid}/v2/contact-service-queue/{id} updates an existing queue object, so the integration must hold the organization-level administrative write scope. The read scopes, such as cjp:config_read or cjds:admin_org_read, are appropriate when an application only retrieves configuration data. They do not authorize mutation of queue configuration. The cjp:user scope is also not sufficient because queue configuration is a tenant or organization-level administrative resource, not a simple user-context operation. The scope cjds:admin_org_write is therefore the correct scope for a PUT operation on contact-service-queue. This matches the principle used throughout Cisco's API documentation: write methods require write-capable scopes, especially for configuration entities. Reference: Webex Contact Center Developer API Reference, Contact Service Queues; Webex Developer, Contact Center Service Apps.

A Webex bot conversation must preserve conversation context between incoming messages. If each incoming message starts the Webex Connect flow from the beginning, the flow is treating every webhook event as a new start event instead of waiting for the next message from the same user. The Receive node is the correct mechanism for continuing the flow after the initial webhook trigger. It should use a custom event that matches the user email, because the user identity is what links the next inbound message to the same conversation path. Matching the bot email would identify the bot endpoint, not the specific human conversation participant. Creating multiple webhooks for different steps would fragment the design and still would not preserve state cleanly. A Call Flow node is useful for modularizing logic but does not by itself wait for and correlate the user's next message. The Receive node with the user-email custom event keeps the conversation from restarting. Reference: Webex Connect Help, Receive Node and flow debugging; Webex Connect Webex Chat/Webex Engage documentation.

For PSTN calls arriving at Webex Contact Center, the safe media statement is that the supported voice codecs are G.711 mu-law and G.711 A-law. Cisco's Webex Contact Center telephony material emphasizes PSTN and Local Gateway interoperability through standard SIP media, and the exam objective expects knowledge of codec compatibility at the service edge. Opus is widely used in WebRTC and collaboration media contexts, but it is not natively supported for PSTN ingress into Webex Contact Center without appropriate interworking or transcoding in the overall design. SIP early media support also must not be assumed as fully supported in every Webex Contact Center call path. DTMF handling is important, but the option saying it can use out-of-band is not the most accurate description of the PSTN media requirement in this question. The codec restriction is the definitive media requirement and is why option B is correct. Reference: Cisco Help, Set up voice channels for Webex Contact Center; Webex Contact Center architecture and telephony documentation.

Webex Contact Center APIs use OAuth 2.0 for authentication and authorization. Cisco's developer documentation for Webex and Webex Contact Center describes integrations as the mechanism used to request permission and obtain access tokens for API calls, using the OAuth 2.0 authorization framework rather than static API keys or basic HTTP authentication. OAuth 2.0 gives the platform scoped access control, token issuance, and administrative consent behavior appropriate for enterprise automation. Mutual TLS may be used in specific transport-security or trunking contexts, but it is not the authorization specification for normal Webex Contact Center REST APIs. Basic HTTP authentication would require sharing credentials directly with the client and does not match the Webex developer model. API key authentication is also not the supported authorization pattern for these Contact Center APIs. The typo in the original option has been corrected to OAuth 2.0. Reference: Webex Developer, Integrations and Authorization; Webex Contact Center API documentation.