117-301 · Question #108
Which of the following describes correct LDAP service definitions? (Choose THREE correct answers.)
The correct answer is A. LDAP was developed as a lightweight alternative to DAP. C. LDAP follows the X.500 directory standard. E. LDAP is optimized for searching information. See the full explanation below for the reasoning.
Question
Options
- ALDAP was developed as a lightweight alternative to DAP.
- BLDAPv6 is the latest stable version specified by RFCs.
- CLDAP follows the X.500 directory standard.
- DX.500 directories can run only over TCP/IP.
- ELDAP is optimized for searching information.
How the community answered
(38 responses)- A74% (28)
- B16% (6)
- D11% (4)
Community Discussion
9
Nina C.Jun 26, 2026The correct answers are A, C, and E. LDAP was literally built to be a lighter replacement for DAP (which ran over the heavier OSI stack), it maps to the X.500 directory model, and it is specifically designed to be read-heavy and fast at lookups rather than writes. B is a trap because LDAPv3 is the current stable version per the RFCs, not v6, and D is backwards because X.500 itself runs over OSI protocols, not TCP/IP, which is actually why LDAP was created in the first place to give TCP/IP access to that kind of directory.
Viktor S.Jun 27, 2026Nina nailed the core points, though worth spelling out for anyone still fuzzy on D: X.500 over OSI is not just a curiosity, it was the actual pain point that motivated the "Lightweight" part of the name, so if you understand that history the distractor basically writes itself.
Viktor S.Jun 26, 2026A, C, and E are the three you want, and if you know the history here you will never confuse them again. DAP ran over the full OSI stack and was a beast to implement, so engineers built LDAP to expose the same X.500 data model over plain TCP/IP without all that overhead, which is exactly what A and C are telling you. E is correct too because LDAP's design is intentionally lopsided toward reads, think authentication lookups and address book queries, not heavy write operations. B is flat wrong because LDAPv3 is the current standard from the RFC 4511 family and there is no v6, and D is the kind of backwards trap they love to set, since X.500 was originally OSI-based and LDAP was the solution for reaching it over TCP/IP, not the other way around.
Luis F.Jun 29, 2026Viktor nailed it, and if anyone wants to lock in E even harder, just remember that LDAP caches read results by design but writes have to propagate through the DIT, so the read optimization is baked into the architecture itself, not just a usage pattern.
Grace U.Jun 23, 2026A, C, and E are the ones to mark here, and the reasoning ties together nicely once you see the thread. LDAP was literally designed to trim down the original DAP so it could work over TCP/IP without dragging along the full OSI stack, which is exactly what makes A true and what makes D wrong at the same time, because X.500 was built for OSI, not TCP/IP exclusively. LDAP inherits the X.500 hierarchical directory model, so C follows naturally from A. And if you remember that "directory" in this context means something you look things up in rather than write to constantly, E makes sense on its own, since LDAP is tuned for reads and searches far more than for writes. B trips up a lot of people but LDAPv3 is the current stable version from the RFCs, and there is no v6.
Nina C.Jun 24, 2026B tripping people up makes sense because "v3" sounds old compared to how other protocols version, but yeah, LDAPv3 has been current since RFC 4511 in 2006 and nothing after it replaced it.
Ingrid P.Jun 26, 2026Almost picked B, then my LDAPv3 card fired and corrected me.
Luis F.Jun 10, 2026Saw this exact one and almost picked B, but LDAPv6 is made up. A, C, E locked it.
Ingrid P.Jun 10, 2026Good catch on LDAPv6, and if you want to lock in A, C, E for good make a card that specifically tests whether you can distinguish the real directory protocols from the plausible-sounding fakes, because that is the exact recall gap this question exploits.