500-444 Exam Dumps : Cisco Contact Center Enterprise Implementation and Troubleshooting

 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.

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 certificates1.

• 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 maintain2.
• 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 with2.

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 Portico123.

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 IPsec1.
• 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 certificates2.
• 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 data2.

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

 = 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