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:
The shared folder should have NTFS and shared folder permissions that will allow the
members of Group2 to edit the files. Thus you should edit the Share permissions
accordingly.
References:
Training Guide: Installing and Configuring Windows Server 2012 R2: Chapter8: File Services
and Storage, Lesson 2: Provisioning and Managing Shared Storage, p.388
This one is tricky because Group 2 requires modify rights to “edit” or “change” files.
But if the share permissions are ready only it will also not work.
I’ll go for C though.
0
0
@AJ, I think B is correct. The question is asking about one group being able to do something to files in another ‘group’. When we are talking group access, this is to do with changing ‘share’ properties. If it were talking about file access/perms within the group then I’d say NTFS perms.
0
0
user can see and read the files….not about share permissions…its about NTFS permissions i think…am i wrong ?
0
0
I think B is correct, because NTFS permissions is OK
0
0
Yes it´s B as the list of NTFS permissions suggests they should be able to write to files, so the Share permission to change is missing probably.
0
0
100% B. most restrictive of ntfs / share permissions apply if accessing across a network. we needto assume the share permissions are more restrictive as the users cant edit
0
0
It’s B, like kurtis said, between share and ntfs permissions, the most restrictive permissions prevail, since with the ntfs permissions everything seems to be ok, i assume that the share permissions are prevailing here.
Reference:
“When using share permissions and NTFS permissions together, if there is a conflict in the configuration, the most restrictive permission prevails.”
http://www.ntfs.com/ntfs-permissions-combined.htm
0
0
B
0
0
It has to be B, because the NTFS permissions for group2 are established, it has to be something wrong with the share permissions…
0
0
thanks guys for your help… this site is always helpfull
0
0