nerdexam
Novell

050-696 · Question #177

You're troubleshooting a problem with file system rights on your WIDGET1 OES NetWare server. WIDGET1 is in the .SLC . WIDGET context. The RHugie.LON.WIDGET user object has Supervisor access to every…

The correct answer is A. RHugie has the Supervisor right to the WIDGET1 server object in eDirectory. In Novell OES NetWare, holding the Supervisor right to a server object in eDirectory automatically confers Supervisor access to all file system volumes on that server, even without any explicit volume trustee assignment.

File System and Storage Management

Question

You're troubleshooting a problem with file system rights on your WIDGET1 OES NetWare server. WIDGET1 is in the .SLC . WIDGET context. The RHugie.LON.WIDGET user object has Supervisor access to every file and directory on every volume on WIDGET1. You've checked the trustee list for the volume and directories on WIDGET1 and RHugie does not have an explicit Novell 050-696 Exam rights assignment. Why does RHugie have Supervisor access to the file systems on WIDGET1?

Options

  • ARHugie has the Supervisor right to the WIDGET1 server object in eDirectory .
  • BRHugie has the Supervisor right granted to WIDGET1's volume objects in eDirectory.
  • CRHugie has the Supervisor right to the LON organizational unit object in eDirectory.
  • DThe NetWare server needs to have the latest Support Pack installed to fix this known bug.
  • ERHugie has Browse, Create, Rename, and Delete rights to the SLC organizational unit object in eDirectory.

How the community answered

(31 responses)
  • A
    77% (24)
  • B
    10% (3)
  • C
    6% (2)
  • D
    3% (1)
  • E
    3% (1)

Why each option

In Novell OES NetWare, holding the Supervisor right to a server object in eDirectory automatically confers Supervisor access to all file system volumes on that server, even without any explicit volume trustee assignment.

ARHugie has the Supervisor right to the WIDGET1 server object in eDirectory .Correct

The Supervisor right granted to a NetWare server object in eDirectory maps directly to Supervisor-level access over all file system resources hosted on that server. This NDS-to-file-system rights linkage explains why the volume trustee list shows no explicit entry for RHugie, yet he still has full Supervisor access to every file and directory on WIDGET1.

BRHugie has the Supervisor right granted to WIDGET1's volume objects in eDirectory.

While Supervisor rights to volume objects would also grant file system access, the question explicitly states that the trustee list on volumes was checked and no explicit assignment for RHugie exists there.

CRHugie has the Supervisor right to the LON organizational unit object in eDirectory.

The LON organizational unit is a different container from the SLC container where WIDGET1 resides, so Supervisor rights to LON would affect objects in that context, not the server or its file systems in SLC.

DThe NetWare server needs to have the latest Support Pack installed to fix this known bug.

The described behavior is an intentional design feature of NetWare, not a known bug, and applying a support pack would not change it.

ERHugie has Browse, Create, Rename, and Delete rights to the SLC organizational unit object in eDirectory.

Browse, Create, Rename, and Delete are eDirectory object rights that govern management of NDS objects, not file system access, and they do not translate into Supervisor rights over a server's file system.

Concept tested: eDirectory server object Supervisor right grants file system access

Source: https://www.novell.com/documentation/oes2015/bsinfo_enu/data/bsinfo_enu.html

Topics

#Supervisor right#server object rights#eDirectory rights flow#file system inheritance

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 050-696 Practice