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.

The correct setting is Network Connections > Maximum concurrent jobs. In Cohesity NetBackup documentation, the Scalable Storage host property is accessed from Hosts > Host properties, selecting the media server, editing media server properties, and choosing Scalable storage. These settings cover cloud encryption, metering, bandwidth throttling, and network connections between NetBackup hosts and the cloud storage provider. The key requirement in the question is to reduce network use by limiting the number of parallel backup streams. Cohesity documents Maximum concurrent jobs as “the default maximum number of concurrent jobs that the media server can run for the cloud storage server,” and notes that when jobs exceed the allowed connection count, additional backup or restore jobs fail after the maximum is reached. By reducing this value, the administrator directly limits simultaneous cloud backup streams and therefore reduces concurrent network consumption. The other options control different behaviors: Metering interval affects reporting collection frequency, Total available bandwidth defines the cloud connection speed, and Sampling interval controls how often bandwidth usage is measured for throttling. References/topics: Scalable Storage properties, Network Connections, Maximum concurrent jobs, and Cloud storage server bandwidth throttling properties.