A company that wants to deploy Cisco Jabber is deciding whether to use UDS or EDI for contact resolution. Which two pieces of information should the company consider? (Choose two.)

For Cisco Expressway Mobile and Remote Access deployments, UDS is the recommended contact source because EDI requires direct access to the internal directory, which is typically unavailable from outside the corporate network.

CUCM must be integrated with the LDAP server for both UDS and EDI to function - UDS relies on CUCM's synchronized LDAP data, while EDI queries the directory directly, so proper LDAP integration on CUCM is a shared prerequisite for both contact resolution methods.

SSO can be used with UDS; there is no technical restriction preventing Single Sign-On from being configured alongside UDS-based contact resolution in Cisco Jabber.

EDI can work with other LDAP-compliant directory servers beyond Active Directory; it is not restricted exclusively to Active Directory, though AD is the most common deployment.

EDI (Enhanced Directory Integration) uses native Windows LDAP APIs to directly query the directory service for contact resolution, making it platform-dependent and requiring network connectivity from the Jabber client to the internal directory server.