Free Practice Questions for Cisco 500-444 Exam

 = In order to configure SAML SSO for PCCE, you need to create claim rules that specify the claims sent from ADFS to Cisco Identity Service as part of a successful SAML assertion. The claim rules define how to transform the incoming claims from the AD FS identity provider into the outgoing claims that are expected by the Cisco Identity Service relying party. The two claim rules that are required for PCCE are:

sAMAccountName - Logon names maintained for backward compatibility. This claim rule maps the sAMAccountName attribute from the AD FS identity provider to the uid attribute in the outgoing claim. The uid attribute is used to identify the authenticated user in the claim sent to the applications. The sAMAccountName attribute is the logon name used to support clients and servers from a previous version of Windows1.

E-Mail Address - For the Outgoing claim type. This claim rule maps the E-Mail-Addresses attribute from the AD FS identity provider to the mail attribute in the outgoing claim. The mail attribute is used to provide the email address of the authenticated user in the claim sent to the applications. The E-Mail-Addresses attribute is the primary email address of the user2.

The other options are not valid claim rules for PCCE. The user_principal option is not a valid attribute name in AD FS. The Unspecified option is not a valid claim type in AD FS. The uid option is not a valid attribute name in AD FS, but it is the outgoing claim type that is mapped from the sAMAccountName attribute.

References :=

AD FS 2.0 Setup for SAML SSO Configuration Example

Configure Single Sign-On with CUCM and AD FS 2.0

Checklist - Creating Claim Rules for a Claims Provider Trust

Notes on ADFS as SAML IdP for ISE User Portals

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

Remote sites are added using the Websetup tool, which is a web-based interface that allows administrators to configure and manage the Packaged Contact Center Enterprise (PCCE) deployment12. Websetup provides a wizard-like process that guides the user through the steps of adding a remote site, such as entering the site name, the PG hostnames or IP addresses, the PG client types, the Unified CM publisher and subscribers, the Finesse server, and the CVP servers1. Websetup also performs automated configuration tasks for the Unified CCE PG, the Unified CCE Rogger, and the CVP Reporting Server1.

Option A is incorrect because PG Setup is a tool that is used to configure the peripheral gateways (PGs) in the main site, not the remote sites3. Option B is incorrect because Initialization Wizard is a tool that is used to initialize the PCCE deployment, not to add remote sites4. Option C is incorrect because SPOG interface is a term that refers to the Single Pane of Glass interface, which is a web-based interface that provides a unified view of the PCCE system status, not a tool to add remote sites5.

References:

1: Cisco Packaged Contact Center Enterprise Administration and Configuration Guide Release 11.6 (1) - Manage Remote Sites [Cisco Packaged Contact Center Enterprise] - Cisco

2: Troubleshooting Cisco Contact Center Enterprise (CCET) course, Module 1: PCCE Overview

3: Cisco Packaged Contact Center Enterprise Administration and Configuration Guide Release 11.6 (1) - Configure Peripheral Gateways [Cisco Packaged Contact Center Enterprise] - Cisco

4: Cisco Packaged Contact Center Enterprise Administration and Configuration Guide Release 11.6 (1) - Initialize the Deployment [Cisco Packaged Contact Center Enterprise] - Cisco

CUBE is a Cisco IOS software feature that provides voice and video connectivity from IP phones to the PSTN or other IP networks. CUBE supports several advanced call control and mobility services, such as:

Element Grouping: This feature allows you to group multiple CUBE elements into a single logical entity and apply common configuration and dial plan across them. This simplifies the management and scalability of CUBE deployments.

Time of Day Routing: This feature allows you to route calls based on the time of day, day of week, or date. You can define time periods and time schedules and associate them with dial peers or voice translation rules. This enables you to implement different call routing policies for different time slots, such as business hours, after hours, holidays, etc.

Call Admission Control: This feature allows you to limit the number of concurrent calls on a CUBE element or a CUBE group based on the available bandwidth or the configured maximum number of calls. This prevents oversubscription of network resources and ensures the quality of service for voice and video calls.

References:

CUBE Configuration Guide

CUBE Element Grouping Configuration Guide

Time of Day Routing Configuration Guide

Call Admission Control Configuration Guide

 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 destination1. The ringtone is a WAV file that is stored on the media server and is configured on the CVP Operations Console and the VXML gateway1. 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 gateway2. The caller will hear the ringtone until the call is connected or disconnected1.

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

The 2K deployment model for Cisco Contact Center Enterprise (CCE) is a prepackaged solution that offers a simplified and scalable architecture for medium-sized contact centers. The 2K deployment model supports up to 2,000 active agents and up to 8,000 configured agents. An active agent is an agent who is logged in and ready to take calls. A configured agent is an agent who has a profile in the system, regardless of their login status. The 2K deployment model also supports up to 4,000 IVR ports, up to 120,000 BHCA, and up to 12,000 concurrent calls1.

References:

1: Cisco Packaged Contact Center Enterprise Solution Reference Network Design (SRND), page 2-3

 The deployment team is responsible for ensuring that servers designated for use by CCE VMs meet the requirements, including but not limited to Storage System Performance and IOPS (Input/Output Operations Per Second) Requirements. The deployment team is the group of engineers who install, configure, and test the CCE solution at the customer site. They must follow the design specifications and guidelines provided by the design team, and verify that the hardware and software components are compatible and meet the performance and capacity requirements. The deployment team must also ensure that the CCE VMs are deployed on the appropriate servers and have the correct network and storage configurations1. References: Troubleshooting Cisco Contact Center Enterprise (CCET) course outline2, Virtualization for Cisco Packaged CCE Release 11.6(x)1.

An enterprise-focused Session Border Controller (SBC) providing voice and video connectivity from the enterprise IP network to service provider SIP trunks is Cisco Unified Border Element (CUBE). CUBE is a Cisco IOS software application that acts as a network border element between two or more VoIP networks, providing interconnectivity, security, and transcoding1. CUBE can be deployed on Cisco Integrated Services Routers (ISRs), Cisco Aggregation Services Routers (ASRs), or Cisco Cloud Services Routers (CSRs) in the enterprise network edge1. CUBE enables enterprises to use SIP trunking services from service providers, as well as interconnect their on-premises or cloud-based unified communications systems with other SIP networks1. CUBE also supports various features such as call admission control, media flow-through or flow-around, quality of service, and media recording1.

CUCM, CVP, and DNIS are not valid options for this question. CUCM stands for Cisco Unified Communications Manager, which is a call processing system that provides call control, device management, and user administration for Cisco IP telephony and video solutions2. CVP stands for Cisco Unified Customer Voice Portal, which is an interactive voice response system that provides self-service and call routing applications for contact centers3. DNIS stands for Dialed Number Identification Service, which is a feature that identifies the number dialed by the caller and passes it to the destination device. None of these products or features act as an enterprise-focused SBC providing voice and video connectivity from the enterprise IP network to service provider SIP trunks.

References: Cisco Unified Border Element Configuration Guide1, Cisco Unified Communications Manager Overview2, Cisco Unified Customer Voice Portal Overview3, Dialed Number Identification Service

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.