NCP-MCA

It tests whether you can design, run, and troubleshoot automation in Prism Central rather than just describe it. Expect scenario questions on playbook triggers and actions, Calm blueprints and lifecycle actions, runbooks, script and API integration, plus governance and failure diagnosis. Hands-on familiarity with the interface matters more than memorized terminology.

It is a proctored multiple-choice exam, including multiple-response items where more than one answer is correct. Read each stem carefully for qualifiers such as 'best' or 'select two'. Confirm the current delivery options and item formats with Nutanix before scheduling, since delivery methods can change.

Nutanix publishes the current question count and time limit for each certification, and they are not fixed here because they change between releases. Check the official Nutanix certification page for your exam version before you book, and plan your pacing around the figure shown there.

People with regular Prism Central automation work generally find it manageable; those who have only read documentation find it hard. Most candidates benefit from several weeks of lab practice covering playbooks, blueprints, and runbooks. Difficulty concentrates in multi-step scenarios where trigger conditions and action order decide the answer.

Fees and passing scores are set and published by Nutanix, and they vary by region and exam version. This page does not quote them because outdated numbers mislead candidates. Check the official Nutanix certification site for the current fee, passing score, and any bundled training offers before purchasing.

Retake rules, waiting periods, and any additional fees are defined by Nutanix in its certification policy. Review that policy before scheduling so you know your options. If you do retake, focus your review on the domains where you were weakest rather than rereading material you already know.

Start with automation fundamentals and Prism Central concepts, then playbooks, then Calm self-service and lifecycle management, since those carry the most weight and build on each other. Add runbooks, then integrations and APIs, and finish with monitoring, governance, and troubleshooting, which draw on everything before them.

Common causes: confusing alert-triggered playbooks with scheduled runbooks, ignoring action ordering and dependencies, missing that a blueprint needs approval or project scoping, and overlooking error-handling paths. Another frequent miss is assuming an API call or script succeeds without checking credentials, endpoints, and return codes.

Yes. Questions describe real configuration choices, and the fastest way to internalize them is to build a playbook against a live alert, publish a blueprint end to end, and script an API call. Reading alone rarely prepares you for questions about why an automation did not trigger or stopped partway.

Validity periods and recertification requirements are set by Nutanix and can change, so confirm them on the official site. This page is independent study material and is not affiliated with, endorsed by, or sponsored by Nutanix; all product names belong to their owners.