050-696 · Question #47
Which eDirectory object type is located at the top-most level of the eDirectory tree?
The correct answer is B. Tree root object. The Tree root object, represented as [Root], sits at the absolute top of the eDirectory hierarchy and is the single object from which all other objects descend.
Question
Options
- ALeaf object
- BTree root object
- CContainer object
- DRedirector object
- ETree schema object
- FTree boundary object
How the community answered
(33 responses)- A3% (1)
- B73% (24)
- C15% (5)
- D6% (2)
- E3% (1)
Why each option
The Tree root object, represented as [Root], sits at the absolute top of the eDirectory hierarchy and is the single object from which all other objects descend.
Leaf objects such as User, Printer, and Server reside at the lowest levels of the tree and cannot contain other objects, placing them at the bottom of the hierarchy, not the top.
The Tree root object (shown as [Root] in eDirectory tools) is the single top-most object in any eDirectory tree and serves as the common ancestor for all other objects in the hierarchy. Every container - such as Organization and Organizational Unit objects - and every leaf object exists somewhere below the Tree root. It defines the boundary of the entire eDirectory tree.
Container objects such as Organization and Organizational Unit objects hold other objects but are themselves subordinate to the Tree root, so they do not occupy the top-most level.
Redirector object is not a defined object class in the eDirectory schema and does not exist as a standard eDirectory object type.
The eDirectory schema governs object class and attribute definitions but is not itself an object positioned at the top of the directory tree.
Tree boundary object is not a standard eDirectory object type and has no defined role in representing the top level of the directory hierarchy.
Concept tested: eDirectory tree hierarchy and [Root] object
Source: https://www.netiq.com/documentation/edirectory-92/edir_admin/data/a2iii88.html
Topics
Community Discussion
No community discussion yet for this question.