Cisco 500-443 Practice Test - Questions Answers, Page 5

The first step for CCE to dynamically allocate a label is an agent needs to log in, as this triggers the Agent PG to send a label request message to the Router. The Router then assigns a label from the available pool and sends it back to the Agent PG. Reference = [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 13

According to the Scripting and Media Routing Guide for Cisco Unified ICM/Contact Center Enterprise, Release 12.5 (1) and 12.5 (2), dynamic labels are expressions that the CallRouter processes in real time, converting an expression into a character string that is then returned to the routing client as a label1. Dynamic labels are useful for routing calls to agents based on their current location, availability, or skill level. For CCE to dynamically allocate a label, an agent needs to log in and register with the system, so that the CallRouter can access the agent's information and use it in the dynamic label expression1. The other options are not correct, because they are not related to dynamic label allocation. The WB ermine service is a web service that provides access to the configuration data of the system2. The Dialer is a component that enables outbound dialing campaigns3. The CVP Call service is a service that handles call control and voice processing for calls that use Unified CVP3.

Reference:

1: Cisco Packaged Contact Center Enterprise Features Guide, Release 12.0 (1)

2: Cisco Packaged Contact Center Enterprise Administration and Configuration Guide, Release 12.0 (1)

3: Scripting and Media Routing Guide for Cisco Unified ICM/Contact Center Enterprise, Release 12.5 (1) and 12.5 (2) - Dynamic Labels

B Agent PG/CTIServer is one of the components that help notify the CCE Router about the new status of an agent when it turns Ready, as it sends a Peripheral Monitor Message (PMM) with agent state information to the Router. E Finesse is another component that help notify the CCE Router about the new status of an agent when it turns Ready, as it sends an HTTP request with agent state information to the CTIServer. Reference = [Cisco Unified Contact Center Enterprise Solution Reference Network

Design (SRND), Release 12.5(1)], page 10; [Cisco Finesse Administration Guide Release 12.5(1)], page 11

B Agent Supervisor is one of the default roles assigned to a supervisor imported from CCE DB, as it allows the supervisor to view and manage agents and teams in Finesse. E Dashboard Designer is another default role assigned to a supervisor imported from CCE DB, as it allows the supervisor to create and edit dashboards in CUIC. Reference = [Cisco Finesse Administration Guide Release 12.5(1)], page 13; [Cisco Unified Intelligence Center User Guide Release 12.5(1)], page 9 According to the Cisco Unified Intelligence Center User Guide, Release 12.6 (1), a supervisor imported from CCE DB is assigned two default roles: Agent Supervisor and Dashboard Designer1. The Agent Supervisor role allows the user to view reports related to agents, teams, and skill groups1. The Dashboard Designer role allows the user to create and edit dashboards that display reports in a graphical format1. The other options are not correct, because they are not default roles assigned to a supervisor imported from CCE DB. The Value List Collection Designer role allows the user to create and edit value list collections that define the values for report filters2. The Report Designer role allows the user to create and edit custom reports using the Report Definition Editor3. The Report Definition Designer role allows the user to create and edit report definitions that specify the data sources, fields, filters, and layouts for reports4.

Reference:

1: Cisco Unified Intelligence Center User Guide, Release 12.6 (1) - User Roles

2: Cisco Unified Intelligence Center User Guide, Release 12.6 (1) - Value List Collections

3: Cisco Unified Intelligence Center User Guide, Release 12.6 (1) - Report Designer

4: Cisco Unified Intelligence Center User Guide, Release 12.6 (1) - Report Definition Designer

According to the Cisco Unified Call Studio User Guide, Release 12.5 (1) and 12.5 (2), there are two types of elements in the Call Studio application that can collect caller response: Menu Element and Digits Element1. The Menu Element captures a single digit from the caller and maps it to a menu option2. The Digits Element captures a string of numerical digits from the caller and stores it in an element data variable3. The other options are not correct, because they are either not elements in the Call Studio application or do not collect caller response as described. There is no Digital tone element or Digits element that captures a single digit in the Call Studio application.

Reference:

1: Cisco Unified Call Studio User Guide, Release 12.5 (1) and 12.5 (2) - Elements

2: Cisco Unified Call Studio User Guide, Release 12.5 (1) and 12.5 (2) - Menu Element

3: Cisco Unified Call Studio User Guide, Release 12.5 (1) and 12.5 (2) - Digits Element

A Account Type is one of the usages for Call Studio Database lookup, as it allows the application to retrieve information about the caller's account from a database and provide different treatments based on the account type. D Claim Number is another usage for Call Studio Database lookup, as it allows the application to validate the claim number entered by the caller against a database and provide confirmation or error messages accordingly. Reference = [Cisco Unified Call Studio User Guide Release 12.5(1)], page 47

A JNDI name (include the jdbc/ portion) is one of the ways a Database Action Element is configured in the Call Studio application, as it specifies the name of the data source that is configured in the VVB to access the database. C SQL Query is another way a Database Action Element is configured in the Call Studio application, as it defines the SQL statement that is executed on the database to perform an operation or retrieve data. Reference = [Cisco Unified Call Studio User Guide Release 12.5(1)], page 48

B The RTP is connected to the Ingress Gateway at different stages of the call, but only when the call is connected to an agent phone. This is because CVP uses a comprehensive call flow model that transfers the call from the VVB to the agent phone and establishes an RTP session between the Ingress Gateway and the agent phone. Reference = [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 11

A distinction between Packaged CCE and Unified CCE, specifically regarding call transfers, is that transfers that require Service Provider interaction via the NIC are supported by a PCCE Deployment in a 2K deployment model only. This means that PCCE can only support pre-routing call flows with NIC in a limited scale, while UCCE can support pre-routing call flows with NIC in any deployment model. Reference = [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 101