050-696 · Question #59
You're designing your company's eDirectory tree. You've named the tree WIDGETCORP-TREE . Below the tree root, you want to create six Organizational Units that represent each American state and…
The correct answer is D. No, Organizational Units can't reside directly below the tree root. This eDirectory design fails because Organizational Units cannot reside directly below the tree root; an Organization object must exist between the tree root and any Organizational Unit.
Question
Options
- AYes, all eDirectory rules have been observed.
- BNo, hyphens aren't allowed in eDirectory tree names.
- CNo, User objects can't reside within Organization Units.
- DNo, Organizational Units can't reside directly below the tree root.
- ENo, you can't use Organizational Units to represent geographic locations.
- FNo, you can't create Organizational Units within other Organizational Units.
- GNo, you can't mix Organizational Units that represent geographic locations with Organization Units
How the community answered
(22 responses)- A5% (1)
- D77% (17)
- E5% (1)
- F14% (3)
Why each option
This eDirectory design fails because Organizational Units cannot reside directly below the tree root; an Organization object must exist between the tree root and any Organizational Unit.
The design does not satisfy eDirectory rules because OUs cannot be placed directly under the tree root without an intervening Organization object.
Hyphens are valid characters in eDirectory tree names, making WIDGETCORP-TREE an acceptable name.
User objects are fully supported within Organizational Units; this is in fact the most common placement for User objects in eDirectory.
The valid eDirectory hierarchy below the tree root is: Tree Root -> Country (optional) -> Organization -> Organizational Unit. An Organization (O=) container is mandatory before any Organizational Unit can be created. Placing six OUs as immediate children of the tree root skips the required Organization level and violates the eDirectory schema rules.
Organizational Units are commonly used to represent geographic locations such as states or provinces; this is a valid and widely recommended design practice.
Organizational Units can be nested inside other Organizational Units, allowing multilevel administrative hierarchies.
Mixing OUs that represent geographic areas with OUs that represent functional groups is a supported and common hybrid design approach.
Concept tested: eDirectory mandatory Organization layer below tree root
Source: https://www.netiq.com/documentation/edirectory-92/edir_admin/data/a2iii88.html
Topics
Community Discussion
No community discussion yet for this question.