You are configuring a new Windows Server 2022 Datacenter system that will host a 60-TB RAID-60 logical drive for on-server backup images. The backup application requires that all space be presented as one contiguous data volume and that individual image files larger than 4 TB be supported. Management also insists on enforcing built-in, per-user disk quotas to track storage consumption. Which approach satisfies all of these requirements while keeping the configuration steps to a minimum?
Initialize the disk with GPT, create one NTFS volume using 64-KB clusters, and turn on disk quotas.
Initialize the disk with GPT, format the volume with ReFS (4-KB clusters), and enable Data Deduplication.
Initialize the disk with MBR, convert it to a dynamic disk, span an NTFS volume across the drive, and enable NTFS compression.
Create eight 7.5-TB NTFS partitions on an MBR disk and mount each partition into an empty folder under a common root.
A single NTFS volume placed on a disk that is initialized with the GUID Partition Table (GPT) overcomes the 2 TB limit of MBR and supports very large files. When the volume is formatted with a 64-KB allocation unit, NTFS can grow well beyond 32 TB, comfortably holding the 60-TB repository. NTFS is also the only Windows file system that offers native disk-quota enforcement, so quotas can be enabled immediately after formatting. The alternative configurations either hit the 2 TB MBR barrier, lack file-system quotas (ReFS), or fragment the capacity into multiple mounts, violating the requirement for a single contiguous volume.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the difference between GPT and MBR?
Open an interactive chat with Bash
Why are 64-KB allocation units recommended for large volumes?
Open an interactive chat with Bash
Why is NTFS preferred over ReFS for this configuration?