Your operations team requires a cluster health check to run automatically every Monday at 02:00. Which Nutanix automation capability should you use?

Nutanix Cluster Check (NCC) is the built-in health-check framework, and Prism can run it on a schedule without any extra automation. In the Health dashboard, the Set NCC Frequency action lets you choose a run interval, such as every few hours, daily or weekly, and for weekly runs pick the day and start time. Setting it to weekly on Monday at 02:00 runs the full NCC suite automatically at that time, records the results in Prism, and can email the summary to the operations team. Adding a cron entry on an AHV host is unsupported customization: it bypasses Prism, is lost on reimaging or upgrades, and hosts are not where NCC is designed to run. Running NCC manually from a CVM every Monday works technically, but it depends on someone being awake at 02:00 and fails the automation requirement. An alert policy reacts to conditions that have already occurred and notifies people; it doesn't schedule NCC execution. Exam caveat: X-Play playbooks automate responses to alerts and events with actions such as running scripts or REST calls, but for a plain weekly health check the native NCC schedule is the documented method. Operational check: after setting the frequency, confirm the next scheduled run time in Prism Health and verify that the report arrives after the first Monday run.