You're designing your organization's eDirectory tree. You want to create Country objects at the top of your tree for each country where your organization has an office. Each of these offices has a…

Not all eDirectory rules are observed because the schema prohibits placing User leaf objects directly inside Country container objects.

eDirectory names only need to be unique within the same container, not across the entire tree, so having multiple objects named Admin in different Country containers is permitted.

eDirectory enforces a strict container hierarchy: Country (C) objects can only contain Organization (O) objects, and leaf objects such as User objects must reside at the Organization or Organizational Unit level. Placing a User object named Admin directly inside a Country container violates this schema rule and is not permitted by the eDirectory object class definitions.

eDirectory fully supports distributed administration with administrators in different containers, so this is not a valid reason to reject the design.

The name 'Admin' is not reserved in eDirectory; any valid string can be used as a User object name.

eDirectory trees can be organized geographically, departmentally, or by any structure that fits the organization - there is no requirement to use only departmental design.