Pass the Nutanix Certified Professional (NCP) NCP-DB Questions and answers with ExamsMirror

The Alerts dashboard in Nutanix displays alert messages with three severity levels: Critical, Warning, and Info1. These severity levels help users understand the importance and urgency of each alert, allowing them to prioritize their responses accordingly1.

The Nutanix Era Time Machine provides various capabilities depending on the Service Level Agreement (SLA) selected during database registration1. For a database with a Bronze SLA, the Time Machine supports both “Log Catch up” and "Snapshots"2. “Log Catch up” allows the Time Machine to keep up with the latest changes in the database by capturing log data2. “Snapshots” are point-in-time copies of the database that can be used for recovery or cloning2.

Nutanix Era (NDB) utilizes DEFAULT_008 SLAs with varying frequencies for snapshots and log backups to achieve different recovery point objectives (RPOs). Here's how they compare:

DEFAULT_008 GOLD SLA: Typically has frequent log backups (e.g., every 15 minutes) and snapshots every few hours. This is designed for critical databases with very low RPOs.

DEFAULT_008 SILVER SLA: Offers a balance between protection and resource usage. Log backups might occur every hour with snapshots less frequently. This SLA is often suitable for databases requiring a good RPO without being overly resource-intensive.

DEFAULT_008 BRONZE SLA: Has less frequent log backups (e.g., every few hours) and less frequent snapshots. This is used for databases with less stringent RPO requirements.

DEFAULT_008 BRASS SLA: This has infrequent log backups and is usually considered the least protective SLA with the longest potential RPO

Reasoning:

Since the requirement is to have at least a 7-day log recovery period, any SLA with more frequent log backups than daily is excessive. The DEFAULT_008 SILVER SLA, with its hourly log backups, easily satisfies this requirement, offering the ability to restore to a point in time within the last hour of the past seven days.

References:

Nutanix Era User Guide/SLA Management: https://portal.nutanix.com/page/documents/details?targetId=Nutanix-NDB-User-Guide-v2_5:top-sla-management-c.html  ]

NDB sends alert notifications using configurations auto-populated from the cluster during the initial setup, typically relying on default SMTP settings. If a dedicated SMTP server is required (e.g., for security or compliance), the administrator must change the SMTP Server configuration in NDB Service. This is configured under the NDB Admin Center, where the administrator can specify the dedicated SMTP server’s details (e.g., hostname, port, credentials, and security settings like TLS/SSL).

Other options are incorrect:

A. IDP configuration in Admin Center IAM page: Identity Provider (IDP) settings are for authentication, not email alerts.

B. Alert Email configuration in Prism Element: Prism Element manages cluster alerts, not NDB-specific email settings.

D. SNMP configuration in Prism Central: SNMP is for network monitoring, not email notifications.

Thus, the verified answer is C, reflecting NDB’s alert notification setup.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 6: Monitoring and Alerts, Lesson 6.1: Configuring Alert Notifications.

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.2: Manage Alerts (applicable to v6.10).

Nutanix NDB Administration Guide: "Configuring SMTP for Alerts" section.

The provided exhibit shows the NDB Time Machine restore interface for October 31, 2024, with a Point-in-Time (PIT) restore option selected at 21:50. However, the restore option is unavailable, as indicated by the question. The exhibit includes a warning: "Logs to Backup: The database may contain additional logs. Backup any remaining logs before restore or they will be lost." This suggests that PIT restore requires continuous log retention, and if logs since the last snapshot (at 01:10:00) are not backed up, the restore to 21:50 cannot proceed. Running the "Logs to Backup" operation ensures all transaction logs are captured, enabling PIT restore by allowing NDB to replay logs to the desired point.

Option A (Point in time must be within the most recent range) is incorrect because the selected 21:50 is within the log retention period shown (up to the current time), but logs need to be backed up.

Option B (Selected Restore time is not available) is incorrect because 21:50 is a valid time within the log range, but log backup is the issue.

Option C (Change to snapshot option) is incorrect because switching to a snapshot limits the restore to the snapshot time (01:10:00), not 21:50.

Option D (Logs to Backup must be run first) is correct as the warning indicates that backing up remaining logs is necessary for PIT restore.

After running the backup, the administrator can proceed with the PIT restore.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Point-in-Time Restore Requirements

Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting PIT Restore Issues in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

When an administrator needs to restore databases provisioned with a shared disk configuration on Windows Storage Spaces in Nutanix Database Service (NDB), the restore operation focuses on the disks associated with the database. Windows Storage Spaces provides a virtualized storage layer, and NDB manages the restoration by reverting or recovering the specific disks that host the database files and logs. This ensures that the database is restored to its previous state using the snapshot or backup data, while preserving the shared disk configuration integrity. NDB does not replace the source volume or perform additional operations like tail log backups unless explicitly configured.

Option A (NDB restores the disk that are associated with the database) is correct as it accurately describes NDB’s restore behavior for shared disk setups.

Option B (NDB copies the DB files to be restored to the source volume) is incorrect because NDB restores the entire disk state, not just copying files to the source.

Option C (NDB replaces the source volume with the snapshot volume) is incorrect because NDB restores data to the existing volume, not replacing it entirely.

Option D (NDB performs Tail Log backup to backup any remaining logs) is incorrect because tail log backups are not automatically part of the restore process unless specified for point-in-time recovery.

This approach ensures compatibility with Windows Storage Spaces configurations.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Restoring Databases with Shared Disks

Nutanix Support & Insights, Knowledge Base Article: "Restoring Windows Storage Spaces in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine

In Nutanix Database Service (NDB), alert retention is a configurable setting that determines how long alerts (e.g., system issues, performance warnings, or database events) are stored in the system for review and analysis. Based on NDB’s design and administrative policies, the maximum number of days allowed for alert retention is 180 days. This duration allows administrators to maintain a reasonable historical view of system health while preventing excessive data accumulation that could impact performance. This value is typically set as a default maximum in the NDB settings or via Prism Central integration, and administrators can adjust retention periods within this limit based on organizational needs.

Option A (90) is incorrect as it represents a shorter retention period, which may be a configurable minimum or intermediate value but not the maximum.

Option B (180) is correct as it matches the documented maximum alert retention period in NDB.

Option C (270) is incorrect as it exceeds the standard maximum retention period supported by NDB.

Option D (306) is incorrect as it is not a supported retention limit in NDB’s configuration options.

Administrators should verify this setting in the NDB UI under alert management or consult Nutanix support for custom configurations.

References

Nutanix Database Service (NDB) User Guide, Chapter 6: Administering an NDB Environment, Section: Configuring Alert Settings

Nutanix Support & Insights, Technical Note: "Alert Retention and Management in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 6: Administer an NDB Environment

Nutanix Era offers Role-Based Access Control capabilities by organically embedding them in the product. It provides the ability to add and remove users from Era, create and assign roles to users, and associate various privileges with a role1. The default roles available within Era for Role-Based Access Control are:

prism Admin

Era Super Admin

Era Database Admin

Era Infrastructure Admin1 These roles allow for the management of both physical resources like IP addresses and VLANs along with database entities like databases, time-machines, clones, and so on1.

Point in Time Recovery (PITR) is a feature of NDB that allows restoring a database to any point in time within the retention period of the SLA. To enable PITR, the SLA must support Continuous Log retention, which means that NDB captures and stores the database logs continuously. This allows NDB to replay the logs from the last snapshot to the desired point in time during the restore process. The other options do not enable PITR, but rather affect the frequency and timing of the snapshots and log catch up operations.

References: Nutanix Support & Insights, section “NDB Time Machine Point in Time Recovery”

When performing a SQL Server Restore Source Database operation in Nutanix Database Automation (NCP-DB), an administrator might choose the Restore Location as New Location if they want to restore to a new location and have Era apply Nutanix best practices1. This is because Nutanix Era automates and simplifies database management, allowing the administrator to manage databases at scale, and it applies Nutanix best practices during the restore process1. This ensures optimal performance and reliability of the restored database1.