The correct behavior is that Maximum jobs per client is ignored, and NetBackup applies the lower value between Maximum data streams and Limit jobs per policy. In Cohesity NetBackup, the Maximum data streams property is configured under Hosts > Host properties > primary server > Client attributes > General tab. This setting defines the maximum number of jobs allowed at one time for each selected client, and Cohesity documentation clarifies that it applies to client job count even when multistreaming is not used. The guide further states that when Maximum data streams is not set, NetBackup limits jobs by either Maximum jobs per client or Limit jobs per policy, whichever is lower. However, when Maximum data streams is set, NetBackup ignores Maximum jobs per client and uses either Maximum data streams or Limit jobs per policy, whichever is lower. Therefore, option B precisely matches the documented interaction. The storage-unit Maximum concurrent jobs setting is unrelated to this specific client attribute behavior, so options C and D are incorrect. Reference topics: Client attributes properties, General tab of the Client attributes properties, and Limit jobs per policy.

( To configure AdvancedDisk storage in NetBackup, you need to specify the AdvancedDisk storage path and disk group parameters, including the disk type, RAID level, and capacity.)

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.