nerdexam
Cisco

300-085 · Question #136

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

The correct answer is C. Cisco Unified Communication Manager needs to be integrated with the LDAP server through both D. Queries to the LDAP server can be offloaded by using UDS. E. EDI uses native Windows APIs to retrieve contact data from the directory service. When choosing between UDS and EDI for Jabber contact resolution, three key considerations are that CUCM LDAP integration is required for both, UDS offloads LDAP queries to CUCM, and EDI uses native Windows LDAP APIs.

Cisco Unified IM and Presence

Question

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

Options

  • ASSO cannot be used with UDS.
  • BWith EDI, Active Directory is the only LDAP server that can be used.
  • CCisco Unified Communication Manager needs to be integrated with the LDAP server through both
  • DQueries to the LDAP server can be offloaded by using UDS.
  • EEDI uses native Windows APIs to retrieve contact data from the directory service.
  • FEDI is thecontact source that is used for Cisco Expressway Mobile and Remote Access.

How the community answered

(26 responses)
  • A
    4% (1)
  • B
    8% (2)
  • C
    77% (20)
  • F
    12% (3)

Why each option

When choosing between UDS and EDI for Jabber contact resolution, three key considerations are that CUCM LDAP integration is required for both, UDS offloads LDAP queries to CUCM, and EDI uses native Windows LDAP APIs.

ASSO cannot be used with UDS.

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

BWith EDI, Active Directory is the only LDAP server that can be used.

EDI supports any LDAP-compliant directory server, not only Active Directory; it uses native Windows LDAP APIs which can connect to OpenLDAP and other directories.

CCisco Unified Communication Manager needs to be integrated with the LDAP server through bothCorrect

CUCM must be integrated with the LDAP server for both UDS and EDI deployments - UDS requires CUCM to sync with LDAP to serve directory data, and EDI also depends on CUCM LDAP configuration to function correctly in hybrid scenarios.

DQueries to the LDAP server can be offloaded by using UDS.Correct

With UDS, Jabber queries CUCM's User Data Service REST API rather than querying the LDAP directory directly, effectively offloading directory lookup load from the LDAP server to CUCM.

EEDI uses native Windows APIs to retrieve contact data from the directory service.Correct

EDI (Enhanced Directory Integration) leverages native Windows LDAP APIs to retrieve contact data directly from the directory service, which is why it requires a Windows OS and supports any LDAP-compliant directory, not just Active Directory.

FEDI is thecontact source that is used for Cisco Expressway Mobile and Remote Access.

UDS is the contact source used for Cisco Expressway Mobile and Remote Access (MRA), not EDI; EDI requires direct corporate network or VPN connectivity to the LDAP server.

Concept tested: Cisco Jabber UDS vs EDI contact resolution differences

Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/12_9/cjab_b_planning-guide-jabber-129/cjab_b_planning-guide-jabber-129_chapter_0110.html

Topics

#UDS#EDI#contact resolution#Jabber directory

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 300-085 Practice