050-696 · Question #106
You've just created an NSS volume on your OES NetWare server named SHARED . Your server name is WIDGET1. What name will be automatically assigned to the object for this volume in the eDirectory tree?
The correct answer is B. WIDGET1_SHARED. When an NSS volume is created on an OES NetWare server, eDirectory automatically names the volume object by combining the server name and volume name with an underscore.
Question
Options
- ASHARED
- BWIDGET1_SHARED
- CWIDGET1~SHARED
- DWIDGET1#SHARED
- EWIDGET1-SHARED
- FNSS volumes aren't represented by eDirectory objects.
How the community answered
(35 responses)- B83% (29)
- C3% (1)
- E11% (4)
- F3% (1)
Why each option
When an NSS volume is created on an OES NetWare server, eDirectory automatically names the volume object by combining the server name and volume name with an underscore.
Using only the volume name SHARED would not be unique across the eDirectory tree if multiple servers had a volume with the same name.
eDirectory automatically creates a Volume object for each NSS volume using the naming convention ServerName_VolumeName. For a server named WIDGET1 and a volume named SHARED, the resulting eDirectory object name is WIDGET1_SHARED. This naming convention ensures unique identification of volumes across the tree.
The tilde character (~) is not used in the eDirectory volume object naming convention.
The hash character (#) is not used in the eDirectory volume object naming convention.
While a hyphen-minus appears similar, the actual delimiter used in the automatic naming convention is an underscore (_), not a hyphen-minus.
NSS volumes are represented by Volume objects in the eDirectory tree and are automatically created when a volume is mounted.
Concept tested: eDirectory volume object naming convention for NSS
Source: https://www.novell.com/documentation/oes/pdfdoc/stor_nss_lx/stor_nss_lx.pdf
Topics
Community Discussion
No community discussion yet for this question.