If a database administrator is unable to provision a new MongoDB database using an existing software profile, the most likely cause is that the administrator lacks the proper permissions in Prism Element. NDB relies on Prism Element for cluster-level operations (e.g., storage and compute resource allocation). The database administrator needs appropriate Prism Element roles (e.g., Cluster Admin) to interact with the underlying infrastructure, even if the software profile is available in NDB. Without these permissions, the provisioning action will fail.
Other options are less likely:
A. A database clone operation is in progress: This might delay actions but wouldn’t prevent provisioning unless it locks resources indefinitely.
B. The software profile was created by another user: NDB allows profile reuse across users if published, so this is not a barrier.
D. The software profile is undergoing a patching operation: Patching affects the profile’s state but doesn’t block provisioning unless explicitly locked.
Thus, the verified answer is C, highlighting the need for Prism Element permissions.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 3: Managing Database Instances, Lesson 3.1: Provisioning Databases.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 3: Manage NDB Solutions, Objective 3.1: Troubleshoot Provisioning Issues (applicable to v7.5).
Nutanix NDB Administration Guide: "Prerequisites for Database Provisioning" section, noting Prism Element roles.
