IIS permissions scenario: The Administration group is nested in the Security group and has Full Control on the Sales virtual directory; the Intern group is nested in the Nonsecurity group. Nate (an Intern) must update files under Sales. What should you change so Nate can update the Sales content without weakening site security?

Difficulty: Easy

Correct Answer: Make Nate a member of the Security group

Explanation:


Introduction / Context:
Effective access in Windows/IIS depends on group memberships and the resulting NTFS/IIS permissions. Here, Full Control is granted to the Security group on the Sales virtual directory. Nate, an Intern, needs update rights. The cleanest approach is to adjust group membership so that Nate inherits the required permissions without broadening access for all interns or exposing content anonymously.


Given Data / Assumptions:

  • Administration → Security → Full Control on Sales (via group nesting).
  • Interns → Nonsecurity (no write permissions on Sales).
  • Nate alone needs write/update capability.


Concept / Approach:

Group-based authorization is preferred over per-user ACE sprawl. Adding Nate to the Security group grants him the same Full Control that Administration has, satisfying the update requirement. Enabling anonymous access would bypass authentication/authorization and is insecure. Removing Nate from Interns does not grant rights by itself. Adjusting only Nate’s membership avoids changing other Interns’ privileges.


Step-by-Step Solution:

Confirm that Security has the necessary permissions on Sales.Add Nate to the Security group (direct membership or via a suitable intermediate group).Have Nate reauthenticate or log off/on to refresh tokens.Verify write/update operations on the Sales directory.


Verification / Alternative check:

A targeted per-user ACE on Sales could work but contradicts least-administration principles. The group-membership approach scales better and maintains consistent permissions.


Why Other Options Are Wrong:

Anonymous access (site or directory): Grants access to everyone, not just Nate, and typically removes auditing of identities.

Remove Nate from Interns: Does not provide access unless he joins a group with rights.

None: A clear, minimal-change fix exists.


Common Pitfalls:

Granting NTFS write directly to the user rather than using groups; forgetting token refresh after membership changes.


Final Answer:

Make Nate a member of the Security group

More Questions from Windows 2000 Server

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion