You have a server named Server1 that runs Windows Server and contains two drives named C and D. Server1 hosts multiple file shares. You enable Data Deduplication on drive D and select the General…

Question

Options

• ARun the Set-DedupVolume cmdlet and configure the Scrubbing job.
• BRun the Set-DedupSchedule cmdlet and configure a GarbageCollection job.
• CRun the Set-DedupVolume cmdlet and configure the InputOutputScale settings.
• DRun the Set-DedupSchedule cmdlet and configure the Optimization job.

• A
  5% (3)
• B
  72% (46)
• C
  8% (5)
• D
  16% (10)

Explanation

When files are modified or deleted on a deduplicated volume, their previously deduplicated chunks become orphaned in the chunk store - they are no longer referenced but still consume disk space. The GarbageCollection job is specifically designed to identify and remove these unreferenced (orphaned) chunks, reclaiming that space. To control when this runs, you use Set-DedupSchedule to configure the GarbageCollection job's schedule or trigger it manually. Set-DedupVolume with Scrubbing (A) validates data integrity, not space reclamation. InputOutputScale (C) adjusts concurrency for I/O, not space. The Optimization job (D) deduplicates new or unprocessed data - it does not remove orphaned chunks from deleted/modified files.

No community discussion yet for this question.