Which term best describes a file that is not stored contiguously but in separated pieces?

Which term best describes a file that is not stored contiguously but in separated pieces?

• A. Fragmented File
• B. Split File
• C. Non-Adjacent Files
• D. Shattered File

Answer: (C)

When a file’s data isn’t stored in a single, continuous run on the disk but is broken into pieces scattered across different locations, that file is described as fragmented. The term fragmented file directly communicates the situation: the file has multiple fragments rather than one unbroken sequence of blocks. This often happens over time as files are created, modified, and deleted, leaving gaps that get filled in noncontiguously. Why this is the best choice: fragmented file is the standard, precise term used in operating systems and storage discussions. It clearly conveys that the file’s data is spread out, which is the core idea behind the concept being tested. Why the other terms aren’t as appropriate: non-adjacent files reads as a descriptive phrase and sounds plural or general rather than naming the specific condition of a single file; it’s not the conventional label used in OS literature. split file suggests the file was purposefully divided or split for some reason, which isn’t the typical result of normal file operations. shattered file is not a recognized technical term, so it would be less clear to someone studying how storage works. Context to connect the idea: when data blocks are noncontiguous, reading the file may require multiple seeks to different disk regions, which can slow access. Defragmentation tools reorganize the blocks to restore contiguity and improve performance.

When a file’s data isn’t stored in a single, continuous run on the disk but is broken into pieces scattered across different locations, that file is described as fragmented. The term fragmented file directly communicates the situation: the file has multiple fragments rather than one unbroken sequence of blocks. This often happens over time as files are created, modified, and deleted, leaving gaps that get filled in noncontiguously.

Why this is the best choice: fragmented file is the standard, precise term used in operating systems and storage discussions. It clearly conveys that the file’s data is spread out, which is the core idea behind the concept being tested.

Why the other terms aren’t as appropriate: non-adjacent files reads as a descriptive phrase and sounds plural or general rather than naming the specific condition of a single file; it’s not the conventional label used in OS literature. split file suggests the file was purposefully divided or split for some reason, which isn’t the typical result of normal file operations. shattered file is not a recognized technical term, so it would be less clear to someone studying how storage works.

Context to connect the idea: when data blocks are noncontiguous, reading the file may require multiple seeks to different disk regions, which can slow access. Defragmentation tools reorganize the blocks to restore contiguity and improve performance.