NCP-MCA practice question 17 of 25

An administrator has published a Runbook and needs to execute it. However, the administrator needs to change one of the variable values, which is not currently possible. What is the reason for this?

Full set: 101 questions
Answer options
A: Runbooks do not allow variables to be changed.
B: Variable was not marked as runtime editable when it was added. Correct answer
C: Runbook itself needs to be reopened for editing.
D: Variables need to be changed in the eScript section of the Runbook.
Correct Answer:
B. Variable was not marked as runtime editable when it was added.
Explanation

In Calm Runbooks, a variable must be flagged as Runtime Editable when it is created. Only variables with this attribute appear in the launch dialog and can be modified each time the runbook is executed. If the administrator cannot change the value, the variable was created without the Runtime Editable flag; publishing the runbook does not, by itself, lock variables.

Why Incorrect

A. Runbooks do allow variable changes at launch if the variable is marked Runtime Editable.
C. Re-opening the runbook does not permit runtime editing; the variable attribute determines editability.
D. eScript content is separate from variable definition; variables are managed in the Variables pane, not inside the script body.

References

1. Nutanix Prism Central (Calm) Administration Guide v6.7, “Defining Variables” → Table 6-4, column “Runtime Editable”, p. 237.

2. Nutanix Calm User Guide v2023.1, “Launching a Runbook” → Step 3: “Modify any variables marked Runtime Editable”, p. 119.

3. Nutanix University Courseware “Calm Orchestration Fundamentals”, Module 4, slide 18: “Mark a variable Runtime Editable to allow value override at execution.”

Scroll to Top