Free Practice Questions for Cohesity COH-285 Exam

The unavailable credential type is Secret key. In the Cohesity NetBackup Web UI Cloud Administrator’s Guide topic “Add a cloud provider for a Snapshot Manager,” the Microsoft Azure configuration table identifies the supported credential types as Application service principal, System managed identity, and User managed identity. For an Application service principal, the wizard requires related parameters such as Tenant ID, Client ID, and Secret key; however, Secret key is listed as a field used by the application service principal, not as an independent credential type. Cohesity describes the secret key simply as “the secret key of the application,” while the actual credential type heading remains Application service principal. The same table separately lists System managed identity, which requires enabling system-managed identity on the Snapshot Manager host in Azure and assigning the role, and User managed identity, which uses the Client ID of the user-managed identity connected to the Snapshot Manager host. Therefore, options A, B, and D are valid Azure Snapshot Manager credential types, while option C is only an authentication parameter under service-principal configuration. Reference topics: NetBackup Web UI Cloud Administrator’s Guide, Configure Snapshot Manager in NetBackup, and Add a cloud provider for a Snapshot Manager.

The correct answer is C. During an image verification operation, NetBackup validates the backup image stored on backup storage by reading the backup volume and comparing what is present on that storage with the metadata recorded in the NetBackup catalog. Cohesity NetBackup documentation states that NetBackup verifies backup contents “by reading the volume and comparing its contents to what is recorded in the NetBackup catalog.” It also clarifies that this operation does not compare the backup image with the original client disk contents. Therefore, the validation scope is the readability and catalog consistency of the stored backup image, not a live comparison against the client file system and not a primary-server data check. This distinction is important operationally: image verification confirms that NetBackup can locate and read the blocks belonging to the backup image and that the stored image aligns with catalog records. It is not a restore test and does not prove that current client data is unchanged. References/topics: Catalog utility, Verify backup images, bpverify, NetBackup catalog image validation, and backup storage readability verification.