050-720 · Question #340
What information do you need to set up an LDAP client? (Choose 4.)
The correct answer is A. LDAP version B. LDAP base DN C. Kind of encryption E. Address of the LDAP server. See the full explanation below for the reasoning.
Question
What information do you need to set up an LDAP client? (Choose 4.)
Options
- ALDAP version
- BLDAP base DN
- CKind of encryption
- DSynchronization frequency
- EAddress of the LDAP server
- FFile name of the LDAP database
How the community answered
(30 responses)- A77% (23)
- D7% (2)
- F17% (5)
Community Discussion
6The answer is A, B, C, and E. When you configure an LDAP client you need to know the server address so you can connect to it, the base DN so the client knows where in the directory tree to start its searches, the LDAP version because v2 and v3 have differences that break compatibility if mismatched, and the kind of encryption so you can set up TLS or leave it unencrypted depending on your environment. D is wrong because synchronization frequency is a server replication concern, not something a client needs to know to function. F is wrong because the database file is a server-side detail, the client never touches it directly and does not need to know its name. Saw a very similar question on my exam last month, the trick is remembering that the client only cares about how to reach the server and how to talk to it, not how the server stores its data.
Spin up an OpenLDAP container for five minutes and you will see exactly why you need the server address, the base DN, the LDAP version, and an encryption choice just to get a connection attempt off the ground, because without any one of those the client does not even know where to point or how to talk. Anyone here tried configuring ldap.conf manually and can say whether they found the version negotiation or the base DN harder to track down in an unfamiliar directory?
The stem says "LDAP client," so your first move is to eliminate anything that belongs on the server side, not the client side. F goes immediately because the database file lives on the server, the client never touches it. D goes next because sync frequency is a replication concern, not something a client needs to reach a directory. That leaves you with four options that describe exactly what a client needs to make a connection, which version to speak, where to point, how to secure the channel, and where in the directory tree to start looking, and those map cleanly to A, B, C, and E. I sat this one in a testing center a few years back and nearly second-guessed myself on D, thinking maybe some enterprise LDAP configs required the client to handle scheduled lookups. Reading the stem a second time saved me. "Set up an LDAP client" is asking about the minimum information to establish and authenticate a connection, not to manage ongoing data freshness. The moment I framed it as "what goes in the client config file," D had nowhere to live.
Solid walk-through, and worth flagging that base DN trips up nearly as many students as D does, because it sounds like a schema or structural setting that lives on the server, but the client needs it to anchor the search scope or every query comes back empty regardless of how cleanly the rest of the connection is configured.
Had D first, but a senior said sync is server side, clients just connect.
Sync frequency is server business, not client setup. Pick A, B, C, E.