AZ-802 Manage Storage and File Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Live Microsoft SQL Server databases

  Why it's wrong here

  SQL Server databases are constantly changing and perform many small write operations. Data Deduplication is not supported for active SQL database files because the overhead of managing chunks and the potential for file locking conflicts can lead to severe performance degradation and database corruption. Databases require specialized storage optimization techniques rather than block-level deduplication.

• ✓

  VDI deployment share (VHDs)

  Why this is correct

  Virtual Desktop Infrastructure (VDI) environments contain many virtual machine disks that are nearly identical. This high level of redundancy makes VDI a perfect candidate for Data Deduplication, often resulting in storage savings of up to 90 percent. Windows Server includes a specific optimization mode designed to handle the unique I/O patterns of VDI workloads.

• ✗

  Active Exchange Server databases

  Why it's wrong here

  Exchange Server uses an Extensible Storage Engine (ESE) that performs frequent, random I/O. Similar to SQL Server, active Exchange databases are not supported for Data Deduplication due to the high rate of change and the sensitivity of the transaction logs. Enabling deduplication on these files would likely result in mounting errors and significant latency.

• ✓

  General-purpose file shares

  Why this is correct

  General-purpose file shares often host many versions of the same documents, installers, and office files. This workload is the primary use case for Data Deduplication. It provides a balanced approach to storage savings and performance, allowing the server to reclaim significant space while maintaining fast access times for end users through intelligent caching.

• ✗

  Encrypted volumes using BitLocker

  Why it's wrong here

  While Data Deduplication can run on a volume encrypted by BitLocker, the deduplication engine itself cannot process files that are encrypted at the file level (such as EFS). Furthermore, if the data is encrypted before it reaches the deduplication engine, the data will appear unique, resulting in zero savings. This makes it an inefficient choice.