An administrator needs to provision multiple database clones from the same source database for different purposes (e.g., QA and Test/Development) while avoiding resource starvation by differentiating VM resources for each department. The most efficient way to achieve this is by creating multiple Compute profiles in NDB. Compute profiles define CPU, memory, and other resource allocations for VMs, allowing the administrator to tailor resource limits (e.g., higher resources for QA, lower for Development) and apply them during clone provisioning. This approach is built into NDB, ensuring consistent resource management without manual adjustments.
Option A (Create multiple Compute profiles) is correct as it provides a scalable and efficient way to allocate resources per department.
Option B (Leverage NCM Self Service to deploy database clones) is incorrect because Nutanix Cluster Management (NCM) Self Service is for end-user provisioning, not resource differentiation.
Option C (Use a VM Template for each department) is incorrect because VM templates are less flexible and not natively integrated with NDB clone provisioning.
Option D (Generate a playbook to resize database VMs when released) is incorrect because playbooks are for automation, not initial resource allocation, and resizing post-provisioning is less efficient.
This method optimizes resource use across departments.
References
Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Database Servers, Section: Configuring Compute Profiles
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Servers
