117-301 · Question #136
What schema files are required to make LDAP compatible to NIS? (Choose TWO correct answers.)
The correct answer is B. cosine.schema C. nis.schema. See the full explanation below for the reasoning.
Question
Options
- Amisc.schema
- Bcosine.schema
- Cnis.schema
- Dinetorgperson.schema
How the community answered
(23 responses)- A9% (2)
- B74% (17)
- D17% (4)
Community Discussion
9
Nina C.Jun 27, 2026The answer is B and C, cosine.schema and nis.schema. The nis.schema file is the obvious one because it defines the actual NIS object classes and attributes, things like posixAccount and posixGroup that map directly to what NIS uses for passwd and group entries. But nis.schema does not stand alone, it depends on cosine.schema to supply the foundational attribute types it builds on, so you need both loaded or LDAP will throw errors when it tries to process those NIS-related entries. The other two options, misc.schema and inetorgperson.schema, serve different purposes entirely, misc covers some general-use attributes and inetorgperson is really about internet directory entries for people like email and phone, neither one is part of the NIS compatibility chain.
Viktor S.Jun 29, 2026Worth adding that core.schema is also in that dependency chain, because cosine.schema itself leans on core.schema for base attribute types, so the actual load order is core, then cosine, then nis, and skipping that first one will get you the same errors Nina described.
Grace U.Jun 23, 2026Does your LDAP setup already have cosine.schema loaded, since nis.schema depends on it?
Nina C.Jun 26, 2026Good call on that, and just to add one more layer, core.schema also has to be loaded before cosine.schema, so the full order that usually works is core first, then cosine, then nis.
Ingrid P.Jun 27, 2026The two you need are cosine.schema and nis.schema, where cosine.schema provides base attribute types that nis.schema depends on, so you really cannot load nis.schema alone and expect it to work. Do you have a card that specifically captures the dependency chain here, meaning why cosine.schema has to come first rather than just knowing the two names in isolation?
Viktor S.Jun 27, 2026cosine.schema and nis.schema are the right picks. cosine.schema provides the foundational attribute types that nis.schema depends on, so you need both loaded in that order or LDAP cannot represent the NIS object classes like posixAccount and posixGroup properly.
Luis F.Jun 29, 2026Solid breakdown Viktor, though worth mentioning that core.schema actually needs to come before cosine.schema too, so the full load order is core, cosine, then nis if you want everything to resolve without errors.
Luis F.Jun 19, 2026Guys I am pretty sure it is A and C, misc.schema handles the NIS mappings and nis.schema is obviously required too.
Ingrid P.Jun 21, 2026Luis, misc.schema does not handle NIS object classes, that role belongs to cosine.schema, which nis.schema depends on as a prerequisite, making B and C the correct pair.