Free Practice Questions for Cohesity COH-285 Exam

With ALL_LOCAL_DRIVES and Allow multiple data streams enabled, NetBackup can split each client backup into separate streams per drive or file system; Cohesity documentation states that NetBackup backs up the client and “splits the data from each drive” into its own stream when multiple data streams are enabled. However, the number of streams that can run concurrently is still constrained by job limits. Cohesity’s policy documentation states that concurrent stream count is affected by Maximum jobs per client, Limit jobs per policy, and related storage limits; when Maximum data streams is not explicitly set, NetBackup uses the lower of Maximum jobs per client or Limit jobs per policy. The default Maximum jobs per client is one job, so only one backup stream per client can run. With five clients, that means 5 active backup jobs, not 15.

The storage unit’s Maximum concurrent jobs = 15 does not restrict restores, because Cohesity states this setting controls backup and duplication traffic, not restore jobs. The disk pool’s Maximum I/O Streams = 20 limits read and write streams; restores read backup images and backups write them. Five backups plus ten restores equals 15 total streams, so all 10 restores can run.

The Enable FIPS mode option is presented during a fresh NetBackup installation of primary, media, client, or clustered server software. Cohesity NetBackup Installation Guide procedures show that, during local, remote, or clustered server installation, the installer displays the FIPS Compliance in NetBackup screen where the administrator can enable or disable FIPS mode; by default, FIPS mode is disabled. The guide further states that enabling FIPS causes the NetBackup installer and subsequent operations to run in FIPS mode, and that enabling it during clustered installation applies it to the nodes added on the NetBackup Remote Hosts screen. Client installation follows the same model: the Windows client installation procedure includes a FIPS Compliance in NetBackup screen where FIPS mode can be enabled or disabled. Option C is incorrect because Cohesity explicitly states that NetBackup does not support changing FIPS mode during upgrade; it must be enabled before upgrade or after upgrade as a post-install configuration. Reference topics: NetBackup Installation Guide, FIPS Compliance in NetBackup, and Enable FIPS mode on NetBackup during installation.

The correct answer is AES 256 bit CTR encryption and SHA256/SHA-2 fingerprinting. In NetBackup, MSDP stands for Media Server Deduplication Pool, and its security model protects deduplicated data using modern encryption and fingerprinting algorithms. Cohesity NetBackup documentation identifies the MSDP data-at-rest cipher as AES-256-CTR, specifically listing “MSDP: AES-256-CTR” under NetBackup data-at-rest encryption ciphers. For fingerprinting, Cohesity documents that NetBackup 8.1 introduced a more secure MSDP fingerprint algorithm where the SHA-2 algorithm replaces the existing MD5-like algorithm. The upgrade documentation further explains that rolling MSDP data conversion converts older containers to the AES encryption and SHA-2 fingerprint algorithm, confirming that Blowfish and MD5-like fingerprints are legacy mechanisms rather than the current MSDP security standard. Therefore, option A is the only choice that combines the correct MSDP encryption mode, AES-256-CTR, with the correct secure fingerprinting family, represented in the option as SHA256 fingerprinting. References/topics: NetBackup Security and Encryption Guide, Ciphers used in NetBackup, MSDP fingerprinting algorithm changes, and MSDP rolling data conversion.

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.