300-830 Sample Questions Answers

Agent break behavior is an agent-state activity, so the correct Analyzer repository is Agent Activity Record. Cisco's Analyzer documentation explains that Analyzer repositories separate session-level and activity-level data for customers and agents. A break is not a customer contact segment and not a call session metric; it is a state transition or activity performed by the agent. Agent Activity Record is the repository that captures detailed agent activity state events, idle codes, availability changes, and similar state-driven information. Customer Session Record summarizes the end-to-end customer session. Customer Activity Record captures customer/contact activities such as call segments and handling details. Agent Session Record summarizes an agent's signed-in session, but it does not provide the granular count of times an agent entered a break state. For counting how many times an agent went on a break, the report needs the activity-level state records, not the session summary. Reference: Cisco Help, Cisco Webex Contact Center Analyzer User Guide; Webex Contact Center Analyzer Stock Reports.

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.

The least privileged role that satisfies both capabilities is Supervisor. The user must participate in telephone campaigns and must also speak to an agent without the customer hearing, which is supervisor whisper coaching. Standard and Premium Agent roles can handle assigned interactions based on license capabilities, but they do not provide supervisory monitoring, whisper coaching, barge-in, or team oversight controls. An Administrator role would provide much broader configuration authority than needed, violating the least-privilege requirement. Cisco's Contact Center licensing and role model separates agent capabilities from supervisor capabilities; Premium Agent adds additional digital and reporting capabilities, while Supervisor adds monitoring and assistance functions. Whisper coaching is specifically a supervisor call-monitoring function, not a standard agent function. Because the scenario does not require tenant configuration, user provisioning, routing setup, or recording policy administration, Administrator is excessive. Supervisor is the minimal role that gives the monitoring feature while also supporting campaign participation. Reference: Cisco Help, Manage access in Webex Contact Center; Webex Contact Center Data Sheet.

Webex Connect provides two relevant troubleshooting tools for failed transactions: Debug Console and Export Logs. Cisco's Webex Connect Debug Console documentation states that it displays transaction details and historical logs for API, flow, and rule executions, including status, timestamps, service name, transaction source, and errors. That makes it the interactive tool for investigating a specific failure path. Export Logs is the bulk-download mechanism for inbound and outbound transaction logs across channels and can cover the last seven days or more depending on log availability and tenant configuration. Reports are useful for aggregated channel performance and trends, but not for pulling all failed transactions from a specific service with enough technical detail. Watchtower is not the primary transaction log export mechanism in the option set. Templates are reusable message or channel assets, not troubleshooting tools. For a seven-day failure investigation, Debug Console plus Export Logs is the correct pair. Reference: Webex Connect Help, Debug Console; Webex Connect Help, Export Logs.

Option B is the only system profile that aligns with the Webex Contact Center Desktop WebRTC requirements shown in the exhibit. Cisco's desktop system requirements identify supported browsers and agent device models for calling, including Webex Calling desktop/app computer audio and WebRTC handling from Agent Desktop. A practical WebRTC station must have sufficient bandwidth, a supported operating system and browser, and browser settings that do not block required desktop behavior. Option A is weak because the 384 Kbps bandwidth value is below the practical WebRTC threshold shown by the comparison choices. Option C explicitly disables JavaScript, which prevents the browser-based desktop and WebRTC interaction logic from functioning properly. Option D uses a virtual desktop infrastructure condition, which is not the straightforward supported physical workstation profile presented by the question. Option B provides Windows 11, Chrome, physical host type, adequate bandwidth, a medium security level, and disabled pop-up blocking, making it the compliant choice. Reference: Cisco Help, System requirements for Webex Contact Center Desktop; Set up voice channels for Webex Contact Center.

The failure occurs after the standard Live Chat workflow template is deployed and the widget can be started, so the website widget itself is not the main issue. The Resolve node response in the exhibit points to a missing or invalid Live Chat domain value used by the workflow. Cisco's Webex Connect live chat and create conversation documentation identifies Livechat Website Domain as a value stored under custom variables and used when resolving or creating live chat conversations. The standard template depends on that workflow custom variable being populated with the valid domain where the Live Chat widget is embedded. Changing media type and media channel on the Resolve node would not fix a missing domain variable in the deployed template. The option using chat Domain is close but not the named workflow custom variable indicated by the template. Setting the Workflow Custom Variable LiveChat Domain to a valid value resolves the failure. Reference: Webex Connect Help, Livechat; Create conversation - WxEngage standalone; Resolve Conversation - WXCC.

Queue ranking is the feature designed for this exact business rule. Cisco's Webex Contact Center team configuration documentation allows administrators to rank queues for a team by media type, with lower numerical rank having higher priority. Cisco's routing documentation explains that ranked queues take precedence over queues without the same priority and that queue ranking can be used across media types. In the scenario, Sales must always be handled before Accounting, even when an Accounting call has waited longer. This is not a normal first-in-first-out queue rule; it is a cross-queue prioritization requirement. Configuring capacity-based queues would change the queue operating model but would not impose Sales-before-Accounting precedence. Asking agents to ignore Accounting calls is not a system configuration and would produce inconsistent reporting and service levels. A Sales-only skill profile would prevent Accounting handling rather than defer it until Sales is empty. Queue ranking is the controlled team-based mechanism that satisfies the requirement. Reference: Cisco Help, Manage teams in Webex Contact Center; Understand Routing and Queueing in Webex Contact Center.

A chat digital channel handled by Webex Contact Center agents needs a channel object of type Chat and an asset assigned to that channel. Cisco's digital channel setup model uses assets to represent external channel identities, such as a web chat asset, email asset, SMS asset, or social asset. The channel then connects that asset to Webex Contact Center routing so the conversation can be created, queued, and delivered to agents. Assigning a phone number is relevant to voice or SMS-style channel designs, not to a Web Chat asset. Creating an Email channel or Social Channel would build the wrong media type and would not make a chat widget route as chat. The two required steps therefore match the platform object model: create a channel with Chat as the channel type and assign the appropriate asset to that channel. Once that is done, flows and Queue Task nodes can route the chat to Webex Contact Center agents. Reference: Cisco Help, Set up digital channels in Webex Contact Center; Webex Connect Help, Livechat.

Screen recording with call audio in Webex Contact Center is a quality-management capability, not a generic flow or Webex Connect capability. Cisco positions Webex Workforce Optimization as the suite for quality management, workforce management, and related supervisor quality workflows. Screen recording requires the WFO quality management components and the proper Quality Management entitlement or license. Custom connectors to conversation intelligence platforms may export or analyze conversation data, but they do not create the native supervisor screen-recording capability. Webex Connect is the CPaaS/digital-channel automation platform and is not used to capture agent desktop screens with call audio. Calabrio ONE is historically associated with workforce optimization, but the Cisco answer pattern for current Webex Contact Center setup is Webex WFO plus the Quality Management license. That combination gives supervisors the recording and evaluation layer needed to review agent application usage and process compliance. Reference: Cisco Help, Webex Contact Center Setup and Administration Guide; Webex Contact Center Data Sheet.

A Scheduled Callback activity must know when the callback should occur and the timezone in which that schedule should be interpreted. Cisco's callback scheduling API and Webex Connect scheduling behavior use normalized date/time inputs so a callback is created at the expected customer time. The date format in the answer set is YYYY-MM-DD, which is the standard year-month-day format used by modern APIs and scheduling fields. The timezone is required because the same date and time can represent different UTC instants depending on the caller's or business's region. Customer name and phone ANI may be useful data in a broader callback workflow, but they are not the two key values asked here for configuring the Scheduled Callback node successfully. The YYYY-DD-MM format is not the accepted ordering and would create ambiguous or invalid schedules. The correct pair is therefore schedule date in YYYY-MM-DD format and schedule timezone. Reference: Webex Developer, Callback Schedule API; Webex Connect Help, Event Scheduler and scheduled flow activities.

The requirements point to tenant-wide recording with the least custom design. Cisco's Webex Contact Center voice settings include a global call recording setting that records all inbound and outdial calls when enabled. That setting is administered centrally, which matches the requirement that only administrators configure recording and that recordings apply to the entire company. Flow-based recording is more flexible, especially when consent or conditional recording decisions are required, but it is custom logic and not the simplest global policy. Queue-level configuration is useful when different business lines need different recording behavior, but this scenario explicitly says all inbound calls across the company. Scheduled recording is suitable when recording depends on a time window, queue, team, site, or agent scope. Since the company wants all inbound calls recorded and wants to avoid custom configurations, global configuration is the cleanest Cisco-supported method. Reference: Cisco Help, Set up voice settings for Webex Contact Center; Manage call recording schedules.

The Queue Task node is the Webex Connect node that routes a digital interaction to Webex Contact Center for distribution. Cisco's Webex Connect documentation states that Queue Task calls the Webex CC Queue Task API to queue the contact at Webex Contact Center. In an email digital-channel flow, the channel receives or creates the conversation in Webex Connect, but a live-agent handoff requires creating or queueing a task so Webex Contact Center can apply routing, queue selection, skills, and agent assignment. A Screen Pop node provides information to an agent desktop after routing has occurred; it does not queue the email. Create Conversation creates the conversation object but does not distribute the work to a contact center agent. Add Participant is used to add a participant to a conversation, not to place the email interaction into the contact center routing engine. Therefore, Queue Task is the required node for contact distribution. Reference: Webex Connect Help, Queue Task - WXCC; Webex CC Task Integration Nodes and Node Authorizations.

In Flow Designer, a Play Message activity must have a valid prompt source. Cisco documents that Flow Designer can play prerecorded audio files or text-to-speech prompts and that TTS content must be configured correctly for Cisco Cloud Text-to-Speech. The exhibit indicates a simple flow that should play a message and then disconnect. If callers hear nothing and the call immediately drops, the most direct cause is that the message node has no valid TTS message configured or the TTS value is invalid. A codec mismatch would typically affect media negotiation more broadly, not only the absence of configured prompt text. A missing audio file would apply if the node used an audio file, but the answer choice points to TTS configuration. Cisco Cloud Text-to-Speech being unavailable would be a service-side outage, which is less consistent with a designer-created flow issue. The local misconfiguration is the invalid or missing TTS message. Reference: Cisco Help, Build and manage flows with Flow Designer; Text-to-Speech in Webex Contact Center.

The Resolve Conversation node is a Webex CC Task/Engage integration node that depends on valid node authorization in Webex Connect. Cisco's Webex Connect documentation states that client applications such as Webex Connect must provide a valid access token to use Cisco Webex Contact Center and Webex Engage APIs, and that the token is generated from the configured node runtime authorization. If the Resolve Conversation node fails because it cannot call the Webex Contact Center integration properly, the administrator must authorize the Webex CC Task integration in Webex Connect with valid credentials. Changing the administrator password does not directly authorize the node runtime. Agent credentials are irrelevant because the flow node is running as an integration, not as an agent desktop session. A connector under Webex Contact Center integrations may be needed for some external API use cases, but the failing node shown is part of the pre-built Webex Connect/WxCC task authorization path. Reference: Webex Connect Help, Webex CC Task Integration Nodes and Node Authorizations; Resolve Conversation - WXCC.

To verify which contact sessions were recorded, the manager needs a contact-session report, not a team or site inventory report. Cisco's Analyzer stock reports include CSR reports that are based on Customer Session Record data. The CSR Report - Yesterday is a stock historical report suitable for reviewing completed customer sessions and whether those sessions include recording-related indicators. Team Contact Details and Site Contact Details can be useful for operational breakdowns by team or site, but the question asks which contact sessions were recorded, which aligns with the customer session record. A Usage Report is generally used for consumption or system usage and is not the direct stock report for contact session recording verification. The exam wording points to the standard Analyzer repository/reporting structure: CSR summarizes the end-to-end customer interaction and is the right source when validating recorded contact sessions. Reference: Cisco Help, Webex Contact Center Analyzer User Guide; Webex Contact Center Analyzer Stock Reports.