✅ Option C (Correct) Reasoning: Agents must have skills assigned to them to indicate their capabilities for skill-based routing.✅ Option D (Correct) Reasoning: Queues must have skill criteria associated with them to define the requirements for handling incoming contacts, enabling the routing engine to match skills.❌ Why the other choices are incorrect:

Option A is incorrect: Associating agents directly with queues is traditional routing; skill-based routing requires defining and matching skills.

Option B is incorrect: Assigning call distribution groups to queues is a grouping mechanism, but doesn’t implement skill matching based on criteria.

Option E is incorrect: Skill criteria are primarily assigned to individual agents and queues, not directly to agent teams or call distribution groups for the purpose of skill-based routing.

✅ Option E (Correct) Reasoning: Enabling Outdial on an agent’s desktop profile is essential. This grants agents the permission and interface option to initiate outbound calls from their Webex Contact Center desktop application. Without this, the agent cannot make outdial calls.✅ Option B (Correct) Reasoning: A default outdial Automatic Number Identification (ANI) configured at the tenant level ensures that a valid caller ID is presented for all agent-initiated outdial calls. This is a fundamental requirement for successful call completion and proper caller identification, unless overridden at a more granular level.❌ Why the other choices are incorrect:

Option A is incorrect: Adding an agent to an "outbound team" is specific to outbound campaigns. While agents in campaigns make outdial calls, a general outdial capability does not require this specific team assignment.

Option C is incorrect: Configuring ANI in Flow Designer is primarily for specific outbound campaign flows or callback scenarios, not a general requirement for basic agent-initiated outdial telephony. Tenant-level ANI (Option B) is more fundamental.

Option D is incorrect: Assigning a wrap-up reason to an outdial queue is for post-call categorization and reporting, not for enabling the core functionality of outdial telephony itself.

✅ Option A (Correct) Reasoning: The Bridged Transfer node allows the contact center to maintain control of the call while it is connected to an external service. This ensures the call can be returned to the original flow, meeting the requirement of retaining control and enabling a return.❌ Why the other choices are incorrect:

Option B is incorrect: The HTTP Request node is used for data exchange with external web services, not for transferring or managing call flow to an external IVR service.

Option C is incorrect: The Blind Transfer node completely hands off the call to the destination, meaning the initiating system loses control and cannot easily return the call to the original flow.

Option D is incorrect: The GoTo node is used for navigating to a different step or section within the same call flow, not for transferring a call to an external service.

Requirement: After 180 seconds, agents from other sites must be able to take the call.

This requirement describes a timed overflow scenario where a call is offered to a secondary group of agents if it’s not answered by the primary group within a specific timeframe.

• Step 1: Create agent-based teams.
  Reasoning: Before calls can be routed to agents, those agents must be organized into teams. This foundational step is required to create both the primary team and the overflow team of agents from ‘other sites’.
• Step 2: Add Call Distribution Group that uses the remaining agents’ team after the specified delay.
  Reasoning: A voice queue can have multiple Call Distribution Groups processed sequentially. To create an overflow, a second group is added for the ‘remaining agents’ team’ with a delay of 180 seconds. This ensures the call is offered to the secondary team only after the initial time has elapsed.

Requirement: Only agents with a language ranking of >= 5 can take the call.

This requirement describes skill-based routing, ensuring calls are directed only to agents who possess a specific skill at a minimum proficiency level.

• Step 1: Create a skill profile and set the Type to Proficiency in the Skill Definition settings.
  Reasoning: The first step in using skills is to define them within a Skill Profile. Creating a ‘language’ skill and setting its type to ‘Proficiency’ establishes the 1-10 ranking scale needed to evaluate the ‘>= 5’ condition.
• Step 2: Define skill requirements for the queue activity where the caller’s spoken language is >= 5.
  Reasoning: Within the call flow, the ‘Queue Contact’ activity is configured with skill requirements. This action instructs the system to search for an available agent who has been assigned the ‘language’ skill with a proficiency level of 5 or higher.

✅ Option C (Correct) Reasoning: Setting the Webex Contact Center Redirection on No Answer (RONA) timer to a duration shorter than the agent’s Webex Calling voicemail ring count ensures that an unanswered contact center call is requeued before voicemail can intercept it. For direct calls, RONA is not applicable, so they will ring until the agent’s voicemail picks up.❌ Why the other choices are incorrect:

Option A is incorrect: If the RONA timer is longer than the voicemail ring count, unanswered contact center calls would route to voicemail instead of being requeued, failing a primary requirement.

Option B is incorrect: Configuring multiple lines on agent endpoints does not inherently manage the specific timing conflict between RONA and voicemail for unanswered calls.

Option D is incorrect: Disabling the voicemail setting would prevent direct unanswered calls from rolling to voicemail, failing a stated requirement.

✅ Option A (Correct) Reasoning: Certificate-based trunks (also known as non-registered or trusted trunks) use mTLS for authentication and encryption. They are suitable for direct SIP connections where registration is not required, such as to an ITSP or another trusted gateway.✅ Option B (Correct) Reasoning: Registration-based trunks (or SIP registered trunks) involve the Local Gateway registering as a SIP client with the Webex Calling platform. This model is commonly used for integration with on-premises CUCM or other SIP PBXs, providing extension mobility and feature integration.❌ Why the other choices are incorrect:

Option C is incorrect: While DNS is fundamental to SIP resolution, "DNS-based trunks" is not a distinct trunking model type in Webex Calling Local Gateway.

Option D is incorrect: PSTN refers to the Public Switched Telephone Network, which is a destination for calls, not a trunking model type. Both certificate-based and registration-based trunks can connect to the PSTN.

Option E is incorrect: "Enterprise trunks" is a general term and not a specific technical trunking model defined within Webex Calling Local Gateway architecture.

✅ Option A (Correct) Reasoning: Configuring queue ranking, or priority, in Webex Contact Center ensures that calls from a higher-priority queue (e.g., Sales) are routed to agents before calls from a lower-priority queue (e.g., Accounting), regardless of their arrival time. This directly fulfills the requirement to prioritize Sales calls.
❌ Why the other choices are incorrect:

Option B is incorrect: Capacity-based queues manage how many calls an agent can handle concurrently from different queues, not the fundamental prioritization of calls between distinct queues. It doesn’t override queue priority.

Option C is incorrect: Asking agents to ignore calls is a manual, unreliable operational directive, not a system configuration for automated call distribution.

Option D is incorrect: Selecting a Skill Profile with only Sales skills defines which calls an agent can handle, but it doesn’t configure the priority of calls within the queue system itself.

✅ Option A (Correct) Reasoning: A reorder tone and call drop in a BYO PSTN environment suggest an issue with the SIP trunk or call routing at the customer’s network edge. The Session Border Controller (SBC) manages PSTN connectivity and the SIP trunk to Webex Contact Center, making its status review critical for diagnosing ingress call failures.❌ Why the other choices are incorrect:

Option B is incorrect: Verifying WCC channels is relevant for internal WCC capacity but not for diagnosing a call failure indicated by a reorder tone before the call enters WCC.

Option C is incorrect: The Webex Contact Center Analyzer or call logs primarily show calls that successfully reach the WCC platform. Calls failing at the SBC ingress with a reorder tone may not appear.

Option D is incorrect: Webex Contact Center Queues configuration impacts call routing within WCC, not the initial PSTN ingress failure indicated by a reorder tone and immediate call drop.

✅ Option D (Correct) Reasoning: The screenshot of the ‘WelcomeMessage’ activity settings shows that the ‘Text-to-Speech Message’ field is empty, and no audio files have been added. This means there is no content configured for the ‘Play Message’ activity to play, causing callers to hear nothing. Even though ‘Enable Text-to-Speech’ is off, the fundamental issue is the absence of any message content.
❌ Why the other choices are incorrect:

Option A is incorrect: A codec mismatch typically causes one-way audio or call setup issues, but the primary problem shown is a lack of configured message content for the ‘Play Message’ activity itself.

Option B is incorrect: The ‘Enable Text-to-Speech’ toggle is explicitly OFF in the settings. Therefore, the availability of the Cisco Cloud Text-to-Speech engine is irrelevant, as the system isn’t even configured to use it.

Option C is incorrect: The screenshot does not show any audio files added to the ‘Play Message’ activity. If no audio file was ever added, it cannot be considered ‘missing’ in the sense of being lost; rather, it was never configured.

✅ Option D (Correct) Reasoning: To enable Webex Contact Center agents to use WebRTC for calls, an Agent DN (Directory Number) must be configured on their Desktop profile. This DN is the unique identifier their softphone registers with, allowing the agent to make and receive calls. Without a configured Agent DN, the WebRTC softphone cannot function for call handling.

❌ Why the other choices are incorrect:

Option A is incorrect: "Desktop" is too broad and does not refer to a specific configuration item required for WebRTC functionality. The question asks for a specific configuration on the Desktop profile.

Option B is incorrect: While WebRTC operates within a browser, configuring "Browser" is not a setting within the Webex Contact Center Desktop profile to enable call functionality. Browser settings are external to the agent profile.

Option C is incorrect: "Extension" is a general term. While an Agent DN is a type of extension, "Agent DN" is the precise and correct terminology used in Webex Contact Center for the number assigned to an agent for call routing and softphone registration.

✅ Option B (Correct) Reasoning: For an agent to receive calls in Webex Contact Center, their softphone (Agent Desktop) must be registered and active, enabling communication with the contact center system.✅ Option E (Correct) Reasoning: Queues in Webex Contact Center rely on skills-based routing. Calls are assigned specific skill requirements, and agents with matching skills are offered these calls from the queue.❌ Why the other choices are incorrect:

Option A is incorrect: While agents belong to teams for organizational purposes, the primary mechanism for matching inbound calls to the most suitable agent from a queue is through skills, not directly teams.

Option C is incorrect: Interactive Voice Response (IVR) using the Flow Designer (formerly Script Editor) is used for call handling and self-service before a call is typically routed to an agent. It’s not the direct mechanism for routing from a queue to an agent.

Option D is incorrect: DNIS (Dialed Number Identification Service) entries in Flow Designer define the entry point for an inbound call into a specific flow. They initiate the call process but don’t directly handle the routing of the call from a queue to an available agent.

✅ Option B (Correct) Reasoning: WebRTC (Web Real-Time Communication) for the Cisco Webex Contact Center agent desktop requires a computer with a compatible web browser and a headset. This setup enables direct audio communication through the browser, eliminating the need for physical IP phones or dedicated softphone applications. Option B depicts a workstation with a headset, signifying this browser-based approach.❌ Why the other choices are incorrect:

Option A is incorrect: This option likely represents a traditional physical IP phone, which is not used as the agent phone device when WebRTC is enabled. WebRTC bypasses the need for such hardware.

Option C is incorrect: This option likely depicts a mobile device. While some Webex Contact Center functionalities might be available on mobile, the primary ‘agent phone device’ for the Webex Contact Center desktop, leveraging WebRTC, is typically a desktop/laptop browser with a headset.

Option D is incorrect: This option likely shows a softphone application that is not browser-based WebRTC. WebRTC integrates communication directly into the web browser.