Cisco protects Webex Contact Center APIs with rate limiting per client ID so that one application cannot exhaust shared platform capacity. The current default limit represented in this question is 30 requests per second and 1800 requests per minute for a given client ID. Those two values are the same rate expressed at different time scales, and both are used by administrators and developers when sizing integration retry logic. The Webex developer guidance also stresses that clients must handle HTTP 429 responses and Retry-After behavior rather than assuming unlimited API throughput. The 300 requests per second and 1000 requests per minute options do not match the stated current Contact Center API limits. The 300 requests per minute figure appears in broader Webex REST API guidance for many APIs, but the question is asking specifically about the Webex Contact Center API limits in this context. Correct integrations should therefore throttle to 30 RPS and 1800 RPM unless Cisco grants or documents a different tenant-specific limit. Reference: Webex Developer, Webex Contact Center APIs; Webex Developer blog, Rate Limiting and the Webex API.

In Webex Contact Center, skill-based routing is built from two sides: the queue must express the skill requirement, and the agent must have the matching skill profile. Cisco's official routing and queueing documentation separates skill-based queues from non-skill queues and describes both skill criteria assigned directly to a queue and skill requirements assigned in a flow. Because the question specifically says the customer wants to use skill criteria assigned to queue functionality, the queue configuration must include the skill criteria. The agent side is handled through the skill profile assigned in the agent's settings; that profile carries the agent's skill values and proficiencies used by routing. Associating agents directly to the queue is a non-skill or agent-assignment model, and call distribution groups are for expanding team eligibility over time, not for defining agent skills. Assigning skill criteria to teams is also not the model Cisco documents. Reference: Cisco Help, Understand Routing and Queueing in Webex Contact Center; Create queues and configure routing patterns.

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.

Cisco's Recording Control activity gives caller consent precedence over tenant, queue, and recording schedule settings. In the documented precedence order, if user consent is set to Yes in the flow, the call is recorded regardless of the recording configuration at those other levels. If the user does not consent, the call is not recorded, also regardless of those other settings. If the Recording Control activity is not configured in the flow, the system falls back to the normal recording hierarchy: if any applicable tenant, queue, or schedule configuration is Yes, the call is recorded; if all are No, it is not. That is why option B is true and option C is false. Option D is also true because removing the flow activity returns control to queue-level or other configured recording policy. Option E is false because explicit Yes consent in the flow takes precedence over a recording schedule set to No. Reference: Cisco Help, Understand Routing and Queueing in Webex Contact Center; Build and manage flows with Flow Designer.

The Microsoft Dynamics 365 connector provides CRM integration from the Webex Contact Center agent experience and includes configuration that allows agent workflows and screen-pop behavior to be customized around Dynamics records. Cisco's Dynamics integration guide describes installing the CRM connector, configuring the channel provider, and customizing screen-pop and workflow behavior using parameters and variables. OAuth certificate-based authentication is also part of secure connector authorization patterns used in Cisco integration workflows where an application uses certificate/private-key material instead of a simple shared secret. Agent state syncing between platforms is not the defining connector characteristic in this option set; there are synchronization features involving Webex App or CRM presence, but the connector question is focused on Dynamics connector capabilities. TLS encryption is expected for HTTPS communications but is too generic to be a distinctive answer. Read-only/read-write is not the pair Cisco emphasizes for this connector question. Reference: Cisco Help, Integrate Webex Contact Center CRM Connector for Microsoft Dynamics 365; Configure custom connector for Webex Contact Center.

A supervisor's recording management role is operational quality management, not platform retention administration. Cisco documents supervisor recording workflows around locating and reviewing interactions, filtering recording lists based on criteria, and tagging recordings for later review or quality processes. Those tasks support team compliance and coaching without giving the supervisor destructive or tenant-wide policy authority. Retention policy management is a governance-level setting controlled by administrators or compliance roles, not ordinary supervisors. Permanently deleting recordings is similarly a high-risk compliance operation and would not be granted as a standard supervisor capability in a least-privilege model. Searching for agent interactions, filtering the list of recordings, and applying descriptive tags are the correct day-to-day recording management activities. They let the supervisor find relevant calls, classify them, and support quality monitoring while preserving administrative separation of duties. Reference: Cisco Help, Supervise your agents and teams; Webex Contact Center Data Sheet; Webex Contact Center Setup and Administration Guide.

Outdial calling in Webex Contact Center needs both a tenant or system caller-ID source and a desktop permission path that lets the agent place outbound calls. Cisco's Control Hub voice settings document the Default Outdial ANI field, which determines the default caller ID used for outdial behavior when a dial number is not otherwise mapped. Cisco's desktop profile documentation then controls whether an agent can actually use outdial from Agent Desktop. When Outdial is enabled on the desktop profile, the administrator selects the outdial entry point and, where applicable, the Outdial ANI list. Adding an agent to an outbound team is campaign-related and not a prerequisite for ordinary outdial. ANI in Flow Designer can influence call presentation in flows, but it is not the required administrative setup for agent outdial. A wrap-up reason for an outdial queue is useful for classification after a contact, not the base telephony enablement. Reference: Cisco Help, Set up voice settings for Webex Contact Center; Manage desktop profiles.

Agent Desktop connectivity depends on the Webex service domains and the Contact Center service domain being reachable over HTTPS. Cisco's security and network documentation for Webex Contact Center includes domain allow-listing so the browser desktop can load scripts, APIs, authentication paths, media-related services, and Contact Center application components. The official domain patterns include Webex domains such as *.wbx.com on port 443 and Contact Center service domains such as *.ciscoccservice.com on port 443. Blocking either can prevent the desktop from loading, authenticating, or communicating with Contact Center services. The ucce.com domain is associated with Unified Contact Center Enterprise naming, not Webex Contact Center Agent Desktop. The generic amazonaws.com domain may appear in some cloud service paths, but it is not one of the two direct required domain answers here. The wxcc.com option is also not the official service domain in the documented network requirement list. Reference: Cisco Help, Set up security for Webex Contact Center; System requirements for Webex Contact Center Desktop.