300-830 Exam Dumps : Implementing Cisco Collaboration Cloud Customer ExperienceCLCCEv1.0

WebRTC voice in Webex Contact Center is exposed to agents through the Desktop telephony option. Cisco's desktop profile documentation lists voice channel options, including Agent DN, Extension, and Desktop. The Desktop option allows the agent to sign in through the browser and use the Agent Desktop as the voice device rather than entering an external directory number or extension. Cisco's voice channel setup documentation also describes WebRTC-capable agents selecting Desktop under their telephony option so calls are routed to the Agent Desktop device. Browser is not a desktop profile voice option; it describes the client environment. Extension and Agent DN are traditional station credentials and would make the agent use a phone or configured number instead of browser-based WebRTC. Therefore, to enable agents to make and receive calls using WebRTC, the administrator must configure the Desktop option in the desktop profile. Reference: Cisco Help, Manage desktop profiles; Set up voice channels for Webex Contact Center.

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.

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.