LFCS · Question #343
A private OID should be obtained for a company when:
The correct answer is D. The company plans to create custom schema files for their directory. A company requires a private OID when creating custom schema elements like new attributes or object classes to ensure their uniqueness within the global OID tree.
Question
Options
- AThat company runs out of public OIDs.
- BThe company intends to use LDAP for commercial purposes.
- CThe company wants to make their directory available to the public on the World Wide Web.
- DThe company plans to create custom schema files for their directory.
How the community answered
(32 responses)- A3% (1)
- B3% (1)
- D94% (30)
Why each option
A company requires a private OID when creating custom schema elements like new attributes or object classes to ensure their uniqueness within the global OID tree.
Companies do not 'run out' of public OIDs; rather, they are assigned a unique private OID branch for their specific needs.
Using LDAP for commercial purposes does not inherently require a private OID, unless it involves extending the schema with custom definitions.
Making a directory accessible to the public does not necessitate a private OID; OIDs are for defining schema, not for directory accessibility.
When a company intends to define new attributes or object classes for their LDAP directory, they must assign a globally unique Object Identifier (OID) to each custom schema element to prevent naming collisions. Obtaining a private OID branch guarantees a unique namespace for these custom definitions.
Concept tested: Object Identifier (OID) purpose in LDAP schema
Source: https://learn.microsoft.com/en-us/windows/win32/ad/about-object-identifiers-for-attributes-and-classes
Topics
Community Discussion
No community discussion yet for this question.