A company that uses AD is migrating services from LDAP to secure LDAP. During the pilot phase, services are not connecting properly to secure LDAP. Block is an except of output from the…

Question

Options

• AThe clients may not trust idapt by default.
• BThe secure LDAP service is not started, so no connections can be made.
• CDanvills.com is under a DDoS-inator attack and cannot respond to OCSP requests.
• DSecure LDAP should be running on UDP rather than TCP.
• EThe company is using the wrong port. It should be using port 389 for secure LDAP.
• FSecure LDAP does not support wildcard certificates.
• GThe clients may not trust Chicago by default.

• A
  13% (8)
• B
  77% (47)
• D
  5% (3)
• F
  3% (2)
• G
  2% (1)

Explanation

Two issues are identified from the troubleshooting output. First (B), if the secure LDAP service is not running or has failed to start, no client connections can be established - this is the most fundamental explanation for connectivity failure. Second (E), the wrong port is being used; standard LDAP runs on TCP port 389, while Secure LDAP (LDAPS) runs on TCP port 636. Note: option E states 'it should be using port 389,' which appears to be a typo in the question - the correct port for LDAPS is 636, not 389. The underlying concept being tested is correct: a port mismatch between the client and server would prevent secure LDAP connections. The other options are distractors: OCSP/DDoS (C) and wildcard certificate support (F) are not indicated by the output, and LDAPS uses TCP not UDP (D).

No community discussion yet for this question.