LX0-104 · Question #345
Which statements are true of object classes in an LDAP directory? (Choose TWO correct answers)
The correct answer is C. An entry cannot have more than one structural object class. D. Once an entry has been created, its structural object class cannot be changed without re creating. This question asks to identify two true statements regarding the properties and limitations of structural, auxiliary, and abstract object classes in LDAP.
Question
Options
- AAuxiliary object classes - when used on their own - provide access to extended schema.
- BAn entry cannot have more than one auxiliary object class.
- CAn entry cannot have more than one structural object class.
- DOnce an entry has been created, its structural object class cannot be changed without re creating
- EAbstract object classes are no longer officially support by the LDAP protocol.
How the community answered
(20 responses)- A5% (1)
- C90% (18)
- E5% (1)
Why each option
This question asks to identify two true statements regarding the properties and limitations of structural, auxiliary, and abstract object classes in LDAP.
Auxiliary object classes provide additional attributes and capabilities to an existing structural entry; they are not typically used 'on their own' to provide access to extended schema, but rather to extend entries that already possess a structural object class.
An LDAP entry can have multiple auxiliary object classes to incorporate various sets of optional attributes and rules.
An LDAP entry can have only one structural object class, which defines the primary type of the entry (e.g., person, organizationUnit). While entries can have multiple auxiliary object classes, the structural class provides the fundamental definition.
Once an LDAP entry has been created with a specific structural object class, that class typically cannot be changed. Modifying the structural object class would fundamentally alter the entry's type and schema rules, which usually requires deleting and recreating the entry with the new structural class.
Abstract object classes are fully supported by the LDAP protocol and schema and serve as templates for other object classes; they cannot be directly instantiated as entries themselves.
Concept tested: LDAP object class types and rules
Source: https://ldap.com/objectclass-attribute/
Topics
Community Discussion
No community discussion yet for this question.