Cisco Updated 300-830 Exam Questions and Answers by dakota

The Exclusive multimedia profile type is used when an agent must handle only one interaction at a time. Cisco's multimedia-profile model controls how many simultaneous contacts an agent can receive and how different media types are blended. A blended profile can allow multiple channels, and a blended real-time profile is designed for voice plus real-time digital interactions under concurrency rules. Voice Only would restrict agents to voice and would not satisfy a team that handles voice, email, and chat. The scenario is not asking to remove digital channels; it says a few agents cannot focus on multiple interactions. Exclusive solves that by allowing the agent to work one contact regardless of channel, preventing simultaneous assignments that could reduce quality or agent performance. This is a tenant and desktop-experience configuration decision, not a queue routing problem. The agent can still be eligible for the configured channels, but the desktop capacity model keeps workload to one active interaction. Reference: Cisco Help, Webex Contact Center Setup and Administration Guide; Manage desktop profiles.

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.

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.