There are two types of upgrades available for CCE: Common Ground and Standard. A Common Ground upgrade is a type of upgrade that allows you to upgrade from one major release to another major release without having to rebuild your configuration. A Common Ground upgrade preserves your existing configuration and data, and applies the new features and enhancements of the new release. A Common Ground upgrade is supported for certain releases and deployment models, and requires a specific upgrade path. A Standard upgrade is a type of upgrade that allows you to upgrade from one minor release to another minor release within the same major release. A Standard upgrade also preserves your existing configuration and data, and applies the bug fixes and minor enhancements of the new release. A Standard upgrade is supported for all releases and deployment models, and does not require a specific upgrade path12. References:

• Cisco Unified Contact Center Enterprise Installation and Upgrade Guide, Release 12.6 (1) - Upgrade Overview2
• Cisco Unified Contact Center Enterprise Installation and Upgrade Guide, Release 12.5 (1) and 12.5 (2) - Upgrade Overview3

Answer: D

The PCCE wizard uses the Service Account login for logins to access the appropriate server and enable interfaces, databases, and protocols. The Service Account login is an existing Active Directory user in the same domain as the Packaged CCE servers. This account is added to the Service group during the initialization of the Packaged CCE deployment type. The Service Account login has the required permissions to access the SQL Server, the Organizational Units, and the Security Groups for the Packaged CCE components.

References:

• Cisco Packaged Contact Center Enterprise Administration and Configuration Guide, Release 12.6 (1) - Initialize the Packaged CCE 2000 Agents Deployment Type1
• Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide, Release 12.0 (1) - Configure PCCE Local Authorization2

Microapps are small applications that run on the CVP server and provide interactive voice response (IVR) functionality. They can play prompts, collect digits, perform database lookups, and transfer calls. Microapps are defined and configured using PCCE Web Administration Manager (S.P.O.G) under the Call Settings -> IVR Settings -> Network VRU Scripts menu. Here, you can create, modify, or delete network VRU scripts that reference the microapps and specify the parameters for each microapp. You can also associate the network VRU scripts with call types and dialed numbers to invoke them in the call flow12. References: Troubleshooting Cisco Contact Center Enterprise (CCET) course outline1, Contact Center Enterprise Troubleshooting and Configuration document2.

Answer: B

The sync job that runs every 10 minutes to bring back the OUT_OF_SYNC machine to the IN_SYNC state is the Automated differential sync job. This sync job compares the configuration of the Packaged CCE components on the primary and secondary nodes and applies the changes to the secondary node if there is any difference. The Automated differential sync job is enabled by default and runs every 10 minutes. It can also be triggered manually from the SPOG UI12.

References:

• Cisco Packaged Contact Center Enterprise Administration and Configuration Guide, Release 12.0 (1) - Synchronize the Configuration1
• Troubleshoot CVP on SPOG that Shows Out of Sync - Cisco3

A SIP proxy server is a component of a SIP network that handles the setup and termination of calls between SIP devices. It also performs functions such as registration, authorization, network access control, and network security. Some of the functions of a SIP proxy server are:

• Centralizes dial plans: A SIP proxy server can centralize the dial plans for a SIP network, meaning that it can translate and route calls based on a unified set of rules and policies. This simplifies the administration and management of the SIP network and ensures consistent call routing across different devices and locations.
• Helps to centralize the administration and call control: A SIP proxy server can also help to centralize the administration and call control of a SIP network, meaning that it can provide a single point of contact and configuration for all the SIP devices and endpoints. This reduces the complexity and overhead of maintaining multiple SIP servers and devices and allows for easier monitoring and troubleshooting of the SIP network.

References:

• 1: What Is a SIP Proxy? How Does a SIP Server Work? - Nextiva
• 2: What is a SIP Proxy Server and How Does It Work? - ULTATEL Blog
• 3: What is SIP proxy? | Webopedia
• 4: Definition of SIP proxy | PCMag
• 5: All About SIP Proxy: What is a SIP Server? | TelNet Worldwide

= 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 Deployments1
• Collaboration Virtualization Sizing2
• Unified Computing System Hardware3
• What to select - Cisco BE6000 or UC-on-UCS45

The service that must be restarted after modifying the Java Keystore on the CVP servers is the Cisco CVP WebServicesManager. The Cisco CVP WebServicesManager is a service that provides web services for the CVP components, such as the Operations Console, the Reporting Server, and the Call Server. The Java Keystore is a file that stores the certificates and keys for secure communication between the CVP components and other systems. If the Java Keystore is modified, the Cisco CVP WebServicesManager service must be restarted to apply the changes and ensure the proper functioning of the web services12.

References:

• Configure Secure Java Management Extensions (JMX) Communication on CVP3
• User Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 11.5 (1) - Rest_Client Integration2