The correct action is to run content router queue processing on the media server that hosts the MSDP storage server. In an MSDP environment, expiring backup images with bpexpdate removes or marks the NetBackup catalog references, but the deduplicated segment references in MSDP are reclaimed through the deduplication transaction queue. Cohesity NetBackup documentation explains that after images are expired, MSDP may not immediately reclaim the freed space and that administrators can accelerate reclamation by manually processing the MSDP transaction queue. The deduplication process writes transaction log data into the queue directory, and that queue data is later processed during the next content router queue processing operation. Official NetBackup Deduplication procedures specify running crcontrol --processqueue on the MSDP storage server, not on the primary server. Image cleanup alone is not the MSDP space-reclamation mechanism after manual expiration, and a storage-pool inventory does not dereference deduplicated fragments. Therefore, the required step is option A.