In an NDB environment, the repository VM stores metadata and configuration data but is not a critical runtime component for service availability. If the team powers off the repository VM during maintenance, and it is neither the primary nor a synchronized copy node, the NDB service will continue to operate without interruption. NDB’s high availability (HA) architecture, managed by HAProxy and other components, ensures redundancy and failover capabilities, allowing the system to rely on the primary and synchronized nodes. The repository VM’s downtime only affects metadata access, which can be restored post-maintenance without impacting ongoing database operations.
Option A (The HAProxy VMs will failover instead) is incorrect because HAProxy failover is triggered by primary service node failures, not repository VM power-off.
Option B (There will be no service interruption) is correct as the HA design tolerates a non-primary, non-synchronized repository VM being offline.
Option C (Manual interaction will be required to restore service) is incorrect because no service restoration is needed during this scenario.
Option D (NDB services will fail over immediately) is incorrect because failover is not triggered by a non-critical repository VM power-off.
This reflects NDB’s robust HA implementation.
References
Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section: High Availability Architecture
Nutanix Support & Insights, Knowledge Base Article: "Impact of Repository VM Maintenance in NDB"
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 3: Configure an NDB Environment
