An automation developer has been tasked with creating a Self-Service blueprint to deploy a Windows Server VM for testing purposes. This blueprint…

Nutanix Calm provides the macro @@{calmunique}@@, which expands to a system-generated character string that is guaranteed to be unique every time the blueprint is launched. By concatenating the static prefix “WNSRV” with @@{calmunique}@@ the developer assures that every VM name produced by repeated QA pipeline executions is distinct, eliminating any possibility of a naming collision during deployment.

A. @@{calmrandom}@@ only returns a random string; duplicates, although unlikely, are not prevented.

B. Static value “WNSRV0001” would collide on every subsequent run.

D. Two @@{calmrandom}@@ strings reduce—but do not eliminate—the chance of collision; uniqueness is still not guaranteed.

1. Nutanix Calm Administration Guide 6.5, “Using Macros”, Table 30-2 – calmunique: “…returns a unique 6-character string…recommended for naming to avoid collisions.” (pp. 211-212).

2. Nutanix Calm Blueprint Design Guide 3.4, Section 4.2 “Name Macros”: “calmrandom is random only; calmunique guarantees uniqueness across launches.” (p. 27).

3. Nutanix University NCP-MCA v6.10 Courseware, Module 5 “Self-Service Blueprints”, slide 18: “Use calmunique for VM names when repeated automation runs must never collide.”