You move a file from an NTFS volume on a Windows 2000 client computer to a folder on an NTFS volume on a Windows 2000 Server computer. How does this move affect the NTFS permissions on the file?

Introduction / Context:
Understanding how NTFS permissions behave when you move or copy files between volumes is essential for maintaining security in a Windows environment. This question focuses on what happens when you move a file from one NTFS volume to another distinct NTFS volume, such as from a client machine to a server. Administrators often assume that moving files simply “carries” all permissions, but the behavior actually depends on whether you move within the same volume or between different volumes.

Given Data / Assumptions:

Both the source and destination volumes are formatted with NTFS.
The source volume is on a Windows 2000 client computer; the destination volume is on a Windows 2000 Server computer.
You are performing a move operation (not a simple copy) between two different NTFS volumes.
The destination folder has its own NTFS permissions set, including inheritable permissions.
You want to know how the file’s permissions change after the move operation completes.

Concept / Approach:
In NTFS, the behavior of permissions depends on whether you move or copy and whether the operation occurs within the same volume or across volumes. When you move a file within the same NTFS volume, permissions are preserved because the operation is essentially a rename within the file system. However, when you move a file to a different NTFS volume, the operation is treated as a copy followed by a delete. In that case, the file inherits the inheritable permissions from the destination folder and loses its original permissions. Therefore, for a move across volumes, you should expect the file to adopt the destination folder’s NTFS permissions.

Step-by-Step Solution:
Step 1: Identify that this is a move from one NTFS volume to another, not within the same volume. Step 2: Recall the rule: move within the same NTFS volume preserves permissions; copy or move to a different NTFS volume causes inheritance of destination permissions. Step 3: Understand that for a cross-volume move, Windows performs a copy to the new location and then deletes the original file, just like a copy operation in terms of permissions. Step 4: Since copied files receive permissions based on the destination folder, the moved file will lose its original NTFS permissions. Step 5: The file will then inherit all inheritable permissions from the destination folder on the server. Step 6: Therefore, the correct description is that the moved file loses all original permissions and inherits all inheritable permissions from the destination folder.

Verification / Alternative check:
To verify, imagine copying a file from your workstation to a shared folder on a server that is restricted to a specific group. Typically, after copying, the file is secured with the same permissions as other files in that folder. The file does not keep your local workstation’s original permission set. Because a cross-volume move is functionally equivalent to a copy followed by delete, the same inheritance behavior applies.

Why Other Options Are Wrong:
The moved file retains all of its original NTFS permissions – This behavior applies only to moves within the same NTFS volume, not between different volumes.

The moved file now has no permissions – NTFS does not leave the file without permissions. Instead, it applies inherited permissions from the destination folder.

The moved file loses some permissions and inherits some destination permissions – The standard rule is that the original permissions are replaced by inherited permissions on cross-volume moves, not partially preserved.

Common Pitfalls:
A major pitfall is failing to differentiate between moves within a volume and moves across volumes. Administrators may incorrectly assume that a move always preserves permissions. Another common error is thinking that a file could end up with no permissions, which is not typical in NTFS inheritance rules. For exams and real systems, always recall the simple rule: copying or moving to a different NTFS volume results in inheritance of destination folder permissions.

Final Answer:
When you move a file from one NTFS volume to another, the file loses all of its original NTFS permissions and inherits all inheritable NTFS permissions from the destination folder.