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.

References:

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 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. References = [Cisco Unified Call Studio User Guide Release 12.5(1)], page 48

The number of roles that are available to be assigned to a CUIC user is seven. They are: Administrator, Report Designer, Report Definition Designer, Value List Collection Designer, Dashboard Designer, User Group Manager, and User. References = [Cisco Unified Intelligence Center User Guide Release 12.5(1)], page 9

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. References = [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

C CCE Managed Transfer is supported in PCCE Deployments, as it allows the agent to transfer a call to another agent or skill group within the same PCCE system using the Finesse desktop. E SIP Refer is supported in PCCE Deployments, as it allows the agent to transfer a call to an external destination using the SIP Refer method. References = [Cisco Unified Contact Center Enterprise Features Guide, Release 12.5(1)], page 43; [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 101

drfSchedule.xml is one of the XML files that will be backed up when the Disaster Recovery System performs a cluster-level backup, as it contains the information about the backup schedules. E drfSystem.xml is another XML file that will be backed up when the Disaster Recovery System performs a cluster-level backup, as it contains the information about the system components and their dependencies. References = [Cisco Unified Contact Center Enterprise Installation and Upgrade Guide, Release 12.5(1)], page 37

A One of the descriptions of permissions for a CUIC user or administrator is that the initial and default super user is the System Application User who is configured during installation has permission to do everything, including creating additional super users, as it provides full access to all CUIC features and functions. D Another description of permissions for a CUIC user or administrator is that all of the administrative tasks of the Cisco Unified Intelligence Center solution can be administered from within OAMP, as it provides a web-based interface for managing system settings, cluster configuration, control center, and tools. References = [Cisco Unified Intelligence Center User Guide Release 12.5(1)], page 9; [Cisco Unified Intelligence Center Installation and Upgrade Guide Release 12.5(1)], page 11

A One of the ways Finesse gadgets are deployed is that supporting gadgets must be accessible by both the Agent PC and the Finesse Server, as this ensures that the gadget can be loaded and rendered properly on both sides. D Another way Finesse gadgets are deployed is that Finesse Administration changes require a new login or Reset Layout in order to access changes, as this refreshes the Finesse desktop and applies the new gadget configuration. References = [Cisco Finesse Developer Guide Release 12.5(1)], page 10; [Cisco Finesse Administration Guide Release 12.5(1)], page 13

C One of the requirements for MTP configuration in Mobile Agent is that CTI ports use out of band DTMF, and SIP trunks use RFC2833 in-band DTMF, as this allows CVP to receive and process DTMF signals from different sources. D Another requirement for MTP configuration in Mobile Agent is thatMTP resource is required to convert mobile agent out of band and CVP in-band signaling, as this enables CVP to communicate with mobile agent phones using different protocols. References = [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 95; [Cisco Unified Contact Center Enterprise Features Guide, Release 12.5(1)], page 28

When an explicit or implicit Send to VRU node is encountered, a default Label is returned to CVP. This Label, along with a unique correlation ID, is delivered to CVP. The CVP delivers this string via SIP invite to the Virtual Voice Browser (VVB). At this point, the VVB will ask the ICM script for instruction, such as which VXML application to execute. D When an explicit or implicit Send to VRU node is encountered, a default Label is returned to CVP. This Label, along with a unique correlation ID, is delivered to CVP. The CVP delivers this string via SIP invite to the Virtual Voice Browser (VVB).At this point, the comprehensive VVB script will initiate an RTP session between the Ingress Gateway and an allocated VVB, which will play prompts and collect digits from the caller. References = [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 11; [Cisco Unified Contact Center Enterprise Features Guide, Release 12.5(1)], page 16

The maximum bytes (Data + Variable name) per payload in a PCCE deployment is 2500 bytes. This is the limit imposed by the SIP protocol for the User to User Information (UUI) field that carries the ECC variables. References = [Cisco Unified Contact Center Enterprise Features Guide, Release 12.5(1)], page 23

B One of the destination patterns in the ingress gateway pointing to the number a customer dials considering the SIP comprehensive call flow is pointing to CVP IP address, as this allows CVP to receive and process incoming calls from the ingress gateway. C Another destination pattern in the ingress gateway pointing to the number a customer dials considering the SIP comprehensive call flow is pointing to IOS q/ws loopback address, as this allows CVP to send calls back to the ingress gateway for queuing and self-service. References = [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 Deploymentin 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. References = [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 101