Option A is correct because if one side of the ICM Logger fails, the other side can still receive historical data from both sides of the ICM Router.  However, the failed side will not be able to receive any data until it is restored 1 .

Option B is correct because the Peripheral Gateways (PGs) are connected to both sides of the ICM Router through the private LAN and the visible network.  If the private LAN fails, the PGs can use the visible network to communicate with the active ICM Router and determine which side is the master 2 .

Option D is correct because the ICM Router uses heartbeats to monitor the status of its duplex pair.  If one side does not receive a heartbeat from the other side within a specified time interval, it assumes that the other side has failed and initiates a failover process 3 .

Option C is incorrect because if one side of the ICM Logger fails, the impact of call processing is not limited to the corresponding side of the ICM Router.  The ICM Router can still process calls using the data from the surviving ICM Logger side 1 .

Option E is incorrect because there is some impact on call processing during an ICM Logger failure.  For example, some historical reports may not be available, some configuration changes may not be replicated, and some call data may be lost 4 .

Option F is incorrect because during an ICM Router failover, calls in progress in Cisco Unified Customer Voice Portal (CVP) are not disconnected.  The CVP uses the Survivable Remote Site Telephony (SRST) feature to maintain the calls until the failover is completed 5 .

References :

1 : Troubleshooting Cisco Contact Center Enterprise (CCET), page 2-4

2 : Troubleshooting Cisco Contact Center Enterprise (CCET), page 2-6

3 : Troubleshooting Cisco Contact Center Enterprise (CCET), page 2-8

4 : Troubleshooting Cisco Contact Center Enterprise (CCET), page 2-10

5 : Troubleshooting Cisco Contact Center Enterprise (CCET), page 2-12

The CLI command that manages the Java Keystore Certificate in Windows CCE servers is keytool. Keytool is a utility that is included in the Java Runtime Environment (JRE) and allows you to create, import, export, list, and delete certificates, keys, and keystores. A keystore is a repository of security certificates that can be used for SSL/TLS communication.  The Java Keystore Certificate is the default keystore that is used by the Java applications running on the Windows CCE servers, such as the Web Setup tool, the Diagnostic Framework Portico, and the Unified Intelligence Center 1 2 . To use keytool, you need to open a command prompt window and navigate to the JRE bin directory, which is typically located at C:\Program Files\Java\jre < version > \bin.  Then, you can use the keytool command with various options and parameters to perform the desired operations on the Java Keystore Certificate 3 4 .  References : Security Guide for Cisco Unified ICM/Contact Center Enterprise, Release 12.5 (1) and 12.5 (2) 1 , Implement CA Signed Certificates in a CCE 12.6 Solution 2 , SSL Certificate Installation - Java Based Web Servers - DigiCert 3 , Keytool - Oracle Help Center 4 .

The PCCE production deployment model on an ESXi server requires two validations: ensuring that the correct servers are on the correct sides and verifying that the correct RAM and CPU are being deployed. These validations are necessary to ensure that the PCCE components are configured properly and have sufficient resources to run smoothly. The other options are not relevant for the PCCE production deployment model on an ESXi server. Linux verification for containers is not applicable because PCCE does not use containers. The hypervisor provides enough power is not a validation step, but a prerequisite for the ESXi server.  The lab is deployed properly is not a validation for the production deployment model, but for the lab deployment model.  References : Virtualization for Cisco Packaged CCE Release 11.6(x) 1 , Deployment Type Info API 2 .

= UC on UCS Tested Reference Configuration (TRC) is a type of deployment option for Cisco Unified Communications applications on Cisco Unified Computing System (UCS) servers. TRC is defined as Configuration Based, which means that it specifies the exact hardware configuration, including server model, CPU, memory, disk, RAID settings, BIOS settings, and network adapters. TRC also requires VMware vSphere as the virtualization software, and does not support any other hypervisor. VMware vCenter is not required for TRC, but it is recommended for managing multiple ESXi hosts. TRC is different from Specs-based, which is defined as Rule Based, and allows more flexibility in choosing the hardware components, as long as they meet the minimum requirements and follow the rules defined by Cisco. Specs-based also supports other hypervisors besides VMware vSphere, such as Microsoft Hyper-V and KVM.  References  :=

Troubleshoot UC on UCS TRC, UC on UCS Specs-based, and 3rd-party Specs-based Deployments 1

Collaboration Virtualization Sizing 2

Unified Computing System Hardware 3

What to select - Cisco BE6000 or UC-on-UCS 4 5

An automated deferred sync job is a process that synchronizes the configuration data between the Unified CCE Administration and the CVP servers. An automated deferred sync job runs on the Principal AW machine, which is the primary Administration and Data Server (ADS) in the Packaged CCE deployment. The Principal AW machine initiates the sync job every 15 minutes by default, or whenever a configuration change is made in the Unified CCE Administration. The sync job sends the configuration data to the CVP servers using the REST API.  The sync job also updates the status of the CVP servers in the System and Device Sync page of the Unified CCE Administration 1 2 .  References :

Troubleshoot CVP on SPOG that Shows Out of Sync 1

Packaged CCE Administration 2

 If Cisco Unified ICM sends back a label of 91919191, the caller will hear  ringing .  This is because 91919191 is a special label that is used by Cisco Unified Customer Voice Portal (CVP) to play a ringtone to the caller while the call is being transferred to an agent or another destination 1 .  The ringtone is a WAV file that is stored on the media server and is configured on the CVP Operations Console and the VXML gateway 1 .  The label 91919191 is matched by a dial-peer on the VXML gateway that invokes a ringtone service and sends the ringback.wav file to the ingress voice gateway 2 .  The caller will hear the ringtone until the call is connected or disconnected 1 .

References : Configuration Guide for Cisco Unified Customer Voice Portal, Release 11.6(1) - Unified ICM Configuration [Cisco Unified Customer Voice Portal] - Cisco 1 , Distributed Voice and VXML Gateway Design with CVP SIP - Cisco Community 2

The Active and Configured CUIC Users for the 2K deployment model are 200 and 800 respectively. This means that the CUIC server can support up to 200 concurrent users and up to 800 configured users. A concurrent user is a user who is logged in to CUIC and actively using the application. A configured user is a user who has an account in CUIC, regardless of whether they are logged in or not. The 2K deployment model is one of the UCCE deployment types that defines the maximum number of agents, supervisors, and reporting users that can be supported by the system.  The 2K deployment model can support up to 2000 agents, 200 supervisors, and 200 CUIC concurrent users 1 2 .  References :

Cisco Unified Contact Center Enterprise Installation and Upgrade Guide, Release 12.5 (1) and 12.5 (2) - CLI Commands during Installation and Upgrade  2

Cisco 500-444 Quiz 1 Topic 8 Questions 1-5  1

To build VXML applications, you need to use the Call Studio development platform. Call Studio is an Eclipse-based graphical tool that allows you to create, edit, debug, and test voice applications that run on the VXML Server. Call Studio provides a drag-and-drop interface to design the call flow logic, define the prompts and grammars, and configure the application settings.  Call Studio also supports custom elements, Java code, and web services integration to extend the functionality of the voice applications 1 2 .  References : Cisco Unified Customer Voice Portal Getting Started Guide, Release 12.5(1) 1 , Cisco Unified Customer Voice Portal Developer Guide, Release 12.5(1) 2 .

Security certificates are used to ensure that browser communication is secure by authenticating clients and servers on the web.  There are two ways to deploy security certificates in CCE: Certificate Authority (CA) signed certificates and self-signed certificates 1 .

CA signed certificates are certificates that are issued by a trusted third-party entity, such as VeriSign or Thawte, that validates the identity of the certificate owner.  CA signed certificates are more secure and reliable than self-signed certificates, but they also require more time and money to obtain and maintain 2 .

Self-signed certificates are certificates that are generated and signed by the certificate owner, without involving any third-party entity.  Self-signed certificates are easier and cheaper to create and deploy, but they are less secure and trustworthy than CA signed certificates, as they can be easily forged or tampered with 2 .

CCE supports both CA signed certificates and self-signed certificates for securing the communication between different components, such as AW, CVP, Finesse, ECE, etc.  However, some components may require additional steps or configurations to use CA signed certificates, such as importing the CA certificate into the AW machines, changing the Java truststore password, or binding the CA signed certificate in the Diagnostic Portico 1 2 3 .

The other options are not valid ways to deploy security certificates in CCE:

Security Authority (SA) is not a term related to security certificates, but rather a role that is assigned to a user or a group in CCE to grant them access to certain security features, such as encryption, auditing, or IPsec 1 .

3rd party signed certificates are not a distinct category of security certificates, but rather a synonym for CA signed certificates, as they both involve a third-party entity that signs the certificates 2 .

Digitally signed certificates are not a specific type of security certificates, but rather a general characteristic of all security certificates, as they all use digital signatures to verify the authenticity and integrity of the certificate data 2 .

References :

1 : Security Guide for Cisco Unified ICM/Contact Center Enterprise, Release 12.6(1) - Certificate Management for Secured Connections  2 : Packaged CCE Migration Guide, Release 12.0 - Manage Security Certificates  4 : Computer forensics certifications - Infosec Resources  3 : Implement CA Signed Certificates in a CCE Solution - Cisco

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/finesse/finesse_1151/Admin/guide/CFIN_BK_C0CD262D_00_cisco-finesse-administration-guide-1151/CFIN_BK_C0CD262D_00_cisco-finesse-administration-guide-1151_chapter_01001.pdf

Cisco Finesse primary and secondary servers accept both self-signed certificates and certificate authority certificates when HTTPS protocol is used to access the administration console or agent desktop in Cisco Finesse. A self-signed certificate is a certificate that is generated by the server itself and is not verified by a trusted third-party. A certificate authority certificate is a certificate that is issued by a trusted third-party vendor and is used to establish a secure connection between the server and the client. Cisco Finesse supports both types of certificates for HTTPS connections, but recommends using certificate authority certificates for better security and compatibility. Domain validation certificates, digital certificates, and root certificates are not valid options for this question. A domain validation certificate is a type of certificate authority certificate that only verifies the ownership of the domain name, but not the identity of the organization. A digital certificate is a general term that refers to any certificate that uses public key cryptography to authenticate the identity of the sender and the integrity of the data.  A root certificate is a certificate that is used to validate other certificates in a chain of trust, but it is not directly used for HTTPS connections.  References : Cisco Finesse Administration Guide, Release 12.6 (2) - Getting Started [Cisco Finesse] - Cisco 1 , Solved: Finesse Certificate Issue - Cisco Community 2 , Cisco Finesse Administration Guide Release 11.6(1) 3 , Cisco Finesse Administration Guide, Release 12.0 (1) 4 , Cisco Finesse Administration Guide, Release 12.6 (1) 5

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/finesse/finesse_1151/Admin/guide/CFIN_BK_C0CD262D_00_cisco-finesse-administration-guide-1151/CFIN_BK_C0CD262D_00_cisco-finesse-administration-guide-1151_chapter_01001.pdf