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 command is vxlogview -o 118 -d D,T,x. Status code 96 commonly indicates that NetBackup could not allocate required media or storage resources, so troubleshooting should focus on the NetBackup Resource Broker, also known as nbrb. Cohesity NetBackup documentation identifies originator ID 118 as nbrb, the NetBackup Resource Broker, which maintains available resource information and locates the physical and logical resources needed for backup and tape restore operations. The vxlogview command is the supported utility for reading unified logs, because unified log files are binary and must be assembled by vxlogview. The -o 118 option filters log records for the Resource Broker originator, while -d D,T,x displays the required fields: date, timestamp, and actual log message text. The command reference defines D as display date, T as display timestamp, and x as display actual log message text. Option C is incorrect because w displays who logged diagnostic/debug messages, not the actual message text. References/topics: NetBackup unified logging, vxlogview, originator IDs, nbrb Resource Broker logging, and status 96 resource allocation troubleshooting.

The default summary interval is 24 hours. In NetBackup Appliance AutoSupport/Call Home behavior, when Call Home is enabled and a monitored hardware or software failure occurs, the appliance uploads diagnostic and monitoring information to the AutoSupport server and also generates email notifications to the configured recipient list. The official Appliance AutoSupport Reference Guide describes three email notification types: an initial error notification when the failure is detected, a resolved notification when the failure clears, and “a 24-hour summary by email” for unresolved errors. The NetBackup Appliance Security Guide states the same operational sequence: the appliance sends an error email, a resolved email, and a 24-hour summary of currently unresolved errors. Therefore, 15 minutes, 1 hour, and 12 hours are not the documented default intervals for unresolved-error summary notification. Those values may resemble polling or alerting intervals in other monitoring systems, but NetBackup Appliance Call Home uses the daily summary model to reduce repeated notifications while keeping administrators informed of unresolved conditions. Reference topics: Appliance AutoSupport Reference Guide – About Call Home, Settings > Notification > Alert Configuration, and NetBackup Appliance Security Guide – Call Home alert behavior.