Understanding Disk Fragmentation Which option best describes a fragmented hard drive in the context of DOS/Windows FAT file systems?

Introduction / Context:Fragmentation affects file access speed because files become split across noncontiguous areas of the disk. Understanding what fragmentation is helps users decide when to run defragmentation utilities and diagnose performance problems.

Given Data / Assumptions:

• FAT/FAT32-style file systems allocate files in clusters.
• As files grow or free space becomes scattered, files can be split.
• Hardware is otherwise functioning correctly.

Concept / Approach:Fragmentation is a logical placement issue, not a physical hardware failure. When a file is not stored in consecutive clusters, the disk head must seek more, increasing access time.

Step-by-Step Solution:Consider a file requiring N clusters.If free space is noncontiguous, the file is written in pieces to multiple separated cluster ranges.Future reads require multiple seeks, slowing performance.

Verification / Alternative check:Run a defragmenter (e.g., DOS DEFRAG or Windows Defrag) and view the map: fragmented files show as multiple separated blocks. After defragmentation, files appear contiguous and access is faster.

Why Other Options Are Wrong:Bad platters (Option A) indicate physical damage, not fragmentation.Corrupted data (Option B) may be a consequence of other issues, not the definition of fragmentation.Damaged clusters (Option C) refers to bad sectors, again a hardware/media integrity issue, not fragmentation.

Common Pitfalls:

• Confusing fragmentation with disk errors; fragmentation is resolved by defragmenting, not by low-level repair.
• Believing SSDs need the same defrag treatment; SSDs handle fragmentation differently, and defragging can be counterproductive.

Final Answer:Files are not stored in consecutive clusters