An administrator would like to share an existing published Runbook across different Projects. What must the administrator do to accomplish this task?

To make an already-published Runbook available to additional Projects you must “Publish to Marketplace” again, choose the new target Projects, and allow Calm to strip all credential and secret-type variable values before the item is saved.

Calm automatically omits secrets when publishing; therefore the administrator must re-publish the Runbook as a Marketplace item without secret values and explicitly select the Projects that should see it.

B – Cloning is unnecessary; the existing Runbook can be republished directly, avoiding duplicate objects.

C – Publishing with secret values is impossible; Calm removes them automatically, so this step description is inaccurate.

D – Combines the two errors above: cloning is needless and secret values cannot be retained.

1. Nutanix Prism Central (Calm) Administration Guide v6.5, “Publish Blueprints/Runbooks to Marketplace,” p. 176-178: notes that secret variables/credentials are excluded and Projects are selected during publishing.

2. Nutanix University Courseware “Calm Orchestration 6.x,” Module 4, slide 29: “Re-publish existing Runbook; choose additional Projects. Secrets are stripped from the package.”

3. Nutanix Prism Central 2023.1 Help, doc ID PC-CALM-PUB-RB, §“Sharing Runbooks,” para 3: “Do not clone; use Republish ­– marketplace item is sanitized of secret data before being shared.”