When OceanProtect backup storage is used with Comuvault, what is the correct way to configure the WORM policy (write once, read many) to prevent data tampering?

Question

Options

• AConfigure on Commvault iDA
• BConfigure on Commvault CommServe, but automatically call OceanProtect WORM
• CConfigure on OceanProtect
• DConfigure on Commvault CommServe

• A
  9% (3)
• B
  82% (27)
• C
  6% (2)
• D
  3% (1)

Explanation

Option B is correct because in a Commvault + OceanProtect integration, WORM policy is managed at the Commvault CommServe level - the central management server - which then automatically triggers the WORM lock on the OceanProtect appliance via API calls. This two-tier approach keeps policy control centralized in Commvault while delegating the actual immutability enforcement to OceanProtect's hardware-level WORM capabilities.

Why the distractors are wrong:

• A (Commvault iDA): The iDA (intelligent Data Agent) is a client-side agent responsible for data backup, not policy management - WORM configuration doesn't belong here.
• C (OceanProtect directly): Configuring WORM solely on OceanProtect bypasses Commvault's policy management, breaking the integration and requiring manual coordination outside the backup workflow.
• D (Commvault CommServe alone): This is a partial truth - CommServe does initiate the configuration, but the answer omits the critical detail that it automatically calls OceanProtect to apply WORM, making D incomplete and misleading.

Memory tip: Think of CommServe as the "boss" that issues the WORM order, and OceanProtect as the "enforcer" that physically locks the data - the boss gives the command, the enforcer executes it automatically.

No community discussion yet for this question.