nerdexam
Novell

050-696 · Question #62

Novell 050-696 Exam You've just installed a NetWare 6.5 server named WIDGET1 into the WIDGETCORP-TREE . During installation, you created three server volumes: SYS, DATA, and SHARED . What is the…

The correct answer is D. WIDGET1_SYS, WIDGET1_DATA, and WIDGET1_SHARED. NetWare 6.5 automatically names Volume objects in eDirectory using the format SERVERNAME_VOLUMENAME. For server WIDGET1 with volumes SYS, DATA, and SHARED, the resulting object names are WIDGET1_SYS, WIDGET1_DATA, and WIDGET1_SHARED.

Novell eDirectory Management

Question

Novell 050-696 Exam You've just installed a NetWare 6.5 server named WIDGET1 into the WIDGETCORP-TREE . During installation, you created three server volumes: SYS, DATA, and SHARED . What is the default name that will be assigned to these volumes' associated Volume objects in the WIDGETCORP-TREE eDirectory tree?

Options

  • ASYS, DATA, and SHARED
  • BSYS_1, DATA_1, and SHARED_1
  • CSYS_WIDGET1, DATA_WIDGET1, and SHARED_WIDGET1
  • DWIDGET1_SYS, WIDGET1_DATA, and WIDGET1_SHARED
  • ESYS_WIDGETCORP, DATA_WIDGETCORP, and SHARED_WIDGETCORP
  • FWIDGETCORP_SYS, WIDGETCORP_DATA, and WIDGETCORP_SHARED

How the community answered

(39 responses)
  • C
    10% (4)
  • D
    82% (32)
  • E
    3% (1)
  • F
    5% (2)

Why each option

NetWare 6.5 automatically names Volume objects in eDirectory using the format SERVERNAME_VOLUMENAME. For server WIDGET1 with volumes SYS, DATA, and SHARED, the resulting object names are WIDGET1_SYS, WIDGET1_DATA, and WIDGET1_SHARED.

ASYS, DATA, and SHARED

Using only the volume name (SYS, DATA, SHARED) would cause naming conflicts in an eDirectory tree where multiple servers could have volumes with identical names.

BSYS_1, DATA_1, and SHARED_1

Appending a '_1' numeric suffix is not a NetWare naming convention for Volume objects and does not reflect any standard installation behavior.

CSYS_WIDGET1, DATA_WIDGET1, and SHARED_WIDGET1

The format SYS_WIDGET1 reverses the correct order - NetWare places the server name first, followed by the volume name, not the other way around.

DWIDGET1_SYS, WIDGET1_DATA, and WIDGET1_SHAREDCorrect

NetWare follows the naming convention SERVERNAME_VOLUMENAME when creating Volume objects in eDirectory during server installation, so the three volumes on WIDGET1 become WIDGET1_SYS, WIDGET1_DATA, and WIDGET1_SHARED - this ensures globally unique object names across the tree even when multiple servers use identical volume names.

ESYS_WIDGETCORP, DATA_WIDGETCORP, and SHARED_WIDGETCORP

Appending the tree name (WIDGETCORP) to volume names is not how NetWare names Volume objects; the server name, not the tree name, is used as the qualifying prefix.

FWIDGETCORP_SYS, WIDGETCORP_DATA, and WIDGETCORP_SHARED

Using the tree name as a prefix (WIDGETCORP_SYS) is not the NetWare convention; the server name is the identifier used to qualify Volume objects in eDirectory.

Concept tested: NetWare eDirectory Volume object default naming convention

Source: https://www.netiq.com/documentation/netware65/index.html

Topics

#Volume objects#naming conventions#server volumes#eDirectory tree

Community Discussion

No community discussion yet for this question.

Full 050-696 Practice