You have a file server named Server1 that runs Windows Server 2012 R2. Server1 contains a folder
named Folder1.
You share Folder1 as Share1 by using Advanced Sharing. Access-based enumeration is enabled.
Share1 contains an application named Appl.exe.
You configure the NTFS permissions on Folder1 as shown in the following table.
The members of Group2 report that they cannot make changes to the files in Share1. The members
of Group1 and Group2 run Appl.exe successfully.
You need to ensure that the members of Group2 can edit the files in Share1.
What should you do?
A.
Replace the NTFS permissions on all of the child objects.
B.
Edit the Share permissions.
C.
Edit the NTFS permissions.
D.
Disable access-based enumeration.
Explanation:
Share permissions and NTFS permissions are independent in the sense that neither changes the
other. The final access permissions on a shared folder are determined by taking into consideration
both the share permission and the NTFS permission entries. The more restrictive permissions are
then applied.
References:
Training Guide: Installing and Configuring Windows Server 2012 R2: Chapter8: File Services and
Storage, Lesson 2: Provisioning and Managing Shared Storage, p.388
It’s not clear what means “cannot make changes to the files in Share1”. What kind of changes?
According to this link: http://www.ntfs.com/ntfs-permissions-file-folder.htm
Basic Read & Execute + Basic Write (which setted up for Group2) means users can do everything except – Delete Subfolders and Files, Delete, Change Permissions, Take Ownership. All other permissions are allowed. So basically Group2 get all “change” permissions from NTFS.
Also it’s not clear with what type of Share Permissions Share1 has been shared. So it’s most likely that Share1 has been created with Read share permission (which is default) which blocks Group2 from changing files.
So correct answer should be B – Edit the Share permissions.
agree.
Write means users can create the file, not edit. For editing you need of modifiy permissions