NCP-DB-6.10 Online Practice Questions

Explanation:
NDB Agents handle log backups for database instances, but storing these backups locally can lead to bottlenecks (e.g., disk I/O, storage capacity). To alleviate this, integrating NDB with Nutanix Objects is the recommended solution. Nutanix Objects is an S3-compatible object storage service within the Nutanix ecosystem, ideal for offloading log backups from NDB Agents to a scalable, centralized storage platform. This reduces local storage pressure, improves performance, and ensures strict SLAs for database recovery by leveraging efficient backup retrieval.
Other options are less effective:
A: Integrating with AWS S3 or Azure Blob is possible but requires external connectivity and introduces latency, complexity, and cost compared to Nutanix Objects.
B: Adding NDB Agent VMs increases management overhead and doesn’t address the root storage bottleneck.
D: Increasing RAM/CPU on NDB Agents may help processing but doesn’t solve storage capacity or I/O issues for log backups.
Thus, C is the verified answer, aligning with Nutanix’s integrated ecosystem approach.
Official Nutanix Database Automation
Reference: Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.3: Configuring Log Backup Storage.
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.3: Configure Backup Storage Options (applicable to v6.10).
Nutanix NDB Administration Guide: "Integrating NDB with Nutanix Objects for Log Backups" section.

Explanation:
The Global Service Level Agreement (SLA) feature of Era allows an administrator to create Time Machine policies in a Multi-Cluster configuration1. This feature provides a unified way to manage and enforce backup and replication policies across multiple clusters, ensuring consistent data protection and recovery across the entire environment1.

Explanation:
In an NDB high availability (HA) environment spanning multiple Nutanix clusters, with two clusters running VMware ESXi and one running Nutanix AHV, cross-hypervisor compatibility becomes essential to manage the heterogeneous environment effectively. Nutanix Prism Central is the centralized management platform that provides a unified interface and orchestration capabilities across multiple clusters, regardless of the underlying hypervisor (ESXi or AHV). For NDB HA to function seamlessly across these clusters, Prism Central is required to coordinate cluster operations, manage resources, and ensure consistent policy enforcement, including VM placement, failover, and database management tasks. It abstracts the differences between hypervisors, enabling NDB to operate in a mixed environment.
Option A (Stretched VLANs for all nodes) is incorrect because stretched VLANs address network connectivity, not hypervisor compatibility or NDB HA management.
Option B (NGT - Nutanix Guest Tools) is incorrect as NGT enhances guest VM functionality (e.g., drivers, backups) but does not facilitate cross-hypervisor orchestration for NDB HA.
Option C (Nutanix Prism Central) is correct because it provides the necessary multi-cluster management and compatibility layer for NDB HA across ESXi and AHV.
Option D (VirtlO) is incorrect as VirtIO refers to paravirtualized drivers for VMs, not a component for NDB HA or cross-hypervisor support.
Prism Central’s role ensures that NDB can manage database workloads across diverse hypervisor platforms efficiently.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 3: Configuring an NDB Environment, Section:
Multi-Cluster and Multi-Hypervisor Support
Nutanix Prism Central Administration Guide, Section: Managing Mixed Hypervisor Environments
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 3: Configure an NDB Environment

Explanation:
The Database Agent is used to temporarily store the transaction logs of the source database before they are copied to the log. This is a critical component for ensuring data consistency and recovery in database operations.
Reference: Nutanix Database Automation documentation, focusing on database agents and their roles in transaction log management.

Explanation:
To configure a database with a Time Machine protection mode that includes the Log Catchup operation in NDB, the most essential component is a Service Level Agreement (SLA) that supports continuous log retention. The Log Catchup operation enables point-in-time recovery (PITR) by replaying transaction logs from a specified point, ensuring minimal data loss and meeting Recovery Point Objective (RPO) requirements. This functionality depends on the Time Machine being configured with an SLA that includes the "Continuous Log Retention" option, which ensures transaction logs are captured and retained continuously alongside snapshots.
Option A is incorrect because a daily snapshot alone is insufficient without log retention to enable Log Catchup.
Option B is incorrect because an SLA retention schedule for daily snapshots does not inherently include continuous log capture, which is required for Log Catchup.
Option C is correct as it specifies the Continuous Log Retention option, the critical feature for enabling Log Catchup in a Time Machine SLA.
Option D is incorrect because while frequency settings are important, they are secondary to selecting an SLA with continuous log retention as the foundational requirement.
This configuration ensures robust data protection and recovery capabilities tailored to the database’s needs.
Reference: Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Setting Up SLAs with Log Catchup
Nutanix Support & Insights, Knowledge Base Article: "Configuring Time Machine with Log Catchup in NDB"
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine