Nutanix NCP-DB - Nutanix Certified Professional - Database Automation (NCP-DB v7.5)

The correct answer is A and D because these are the two Time Machine options that are available when creating a database clone in NDB. Point in time allows the user to specify a date and time to create a clone from a specific point in the database history. Snapshot allows the user to select a previously taken snapshot to create a clone from a consistent state of the database. Option B is incorrect because Restore point is not a Time Machine option, but a feature that allows the user to restore a source database to a previous point in time. Option C is incorrect because Backup is not a Time Machine option, but a feature that allows the user to backup a database to a remote location.

The following sources provide more information about the Time Machine options and cloning features in NDB:

Nutanix Database Management & Automation (NDMA) course, Module 4: Protecting Databases Using Time Machine, Lesson 4.2: Cloning Databases

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 5 - Protect NDB-managed Databases Using Time Machine

Nutanix Database Service (NDB) User Guide, Chapter 6: Protecting Databases Using Time Machine, Section 6.2: Cloning Databases

[Nutanix Support & Insights], NDB Time Machine Under the Hood

NDB implements Oracle database disaster recovery by orchestrating Oracle Data Guard, not by duplicating every write through cross-site iSCSI or relying on a generic guest replication agent. The NDB Oracle workflow provisions or manages a standby database on the remote cluster and configures the native Data Guard relationship, including redo transport and the supported protection mode. This lets administrators manage DR through the NDB console and APIs and perform planned or unplanned role transitions within the supported workflow. Nutanix storage snapshots and Time Machine replication remain important for backup, clone, and restore operations, but scheduled snapshot replication is not the mechanism used to continuously maintain an Oracle DR standby. Therefore, deploying the remote Oracle instance and configuring native Oracle Data Guard log transport is the correct architecture. Nutanix documents this capability under Oracle Database Disaster Recovery.

NDB alert policies are enabled by default and may be disabled when an administrator does not want a particular policy to generate alerts. The policy can later be enabled again, allowing alert generation to resume without recreating the policy or changing the monitored resource. This preserves the policy definition while suppressing unwanted notifications and events. NDB also supports operations such as configuring retention and resolving alerts, but those are separate alert-management functions. Pause is terminology associated with other scheduled processes, not the alert-policy control. Publish applies to objects such as software profile versions, and deletion is not the standard control exposed for built-in NDB alert policies. Consequently, Disable is the valid action among the choices. The supported behavior is described in Nutanix’s Disabling or Enabling Alert Policies procedure.

The correct answer is D because it allows the administrator to make the profile available to all users without requiring any additional permissions or roles. A profile is a collection of settings that define how NDB manages a database server or a database. By default, a profile is only available to the user who created it and the Database Admin role. To make a profile available to all users, the administrator can update the profile and set the available state to All. This will enable all users to view and use the profile for their database operations. The other options are not correct because they either require additional steps or do not achieve the desired outcome. Option A is not correct because creating an Access Control role with the Create Profile right and assigning it to all users will only allow them to create their own profiles, not use the existing one. Option B is not correct because creating an Access Control group with the desired users and granting it the Database Admin role will only make the profile available to those users, not all users. Option C is not correct because updating the profile and setting the status to Published will not change the availability of the profile, only the state of the profile. A published profile is a profile that has been tested and verified by the administrator and is ready for use. A draft profile is a profile that is still under development or testing and is not ready for use. References: Nutanix Database Management & Automation (NDMA) course, Nutanix Certified Professional - Database Automation (NCP-DB) certification, Nutanix NCP-DB Certification Exam Syllabus and Study Guide, Nutanix Certified Professional - Database Automation (NCP-DB) datasheet

To assign the minimum permissions required for provisioning new databases in an NDB deployment, the IT manager should assign the Database Administrator role. This role provides the necessary privileges to provision, configure, and manage database instances within NDB, including creating new databases using software profiles and registering database servers. It is designed for database-specific tasks without granting broader infrastructure or administrative control, making it the least privileged role suited for this purpose.

Other options exceed the minimum requirements:

A. Infrastructure Administrator: Manages cluster infrastructure (e.g., storage, networking), which is more than needed for database provisioning.

B. Super Administrator: Grants full control over NDB, including user management and system configuration, far beyond provisioning.

C. Database Infrastructure Administrator: Includes infrastructure management in addition to database tasks, exceeding the minimum scope.

Thus, the verified answer is D, aligning with the principle of least privilege.

Official Nutanix Database Automation References

Nutanix Database Management & Automation (NDMA) course, Module 1: Introduction to NDB, Lesson 1.4: Managing Users and Roles.

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 1: Understand NDB Basics, Objective 1.3: Manage User Permissions (applicable to v7.5).

Nutanix NDB Administration Guide: "Role-Based Access Control (RBAC)" section, detailing Database Administrator role.

SELinux enforcing mode permits access only when files, directories, mount points, and processes carry labels allowed by the active policy. NDB’s supported model uses database-engine-specific SELinux configuration and policies so restored storage paths receive the expected security contexts and remain accessible after attachment. This is why predefined contexts and file policies tailored to the database paths are the valid mechanism. NDB does not guarantee restores by switching the host to permissive mode, because that would suspend enforcement. It also does not install kernel-bypass modules or disable auditing. Dynamically inventing policies during every restore would be operationally unsafe and inconsistent with the documented requirement to prepare SELinux for the relevant database engine. Correctly applied persistent contexts allow the kernel to authorize mount and database access while SELinux remains fully enforcing. Nutanix describes the supported model in Security-Enhanced Linux Configuration.

In Nutanix Database Service (NDB), when an administrator deprecates a software profile version, it is marked as obsolete and restricted from certain operations. Specifically, a deprecated software profile version can no longer be used for provisioning new database instances or VMs. This ensures that only current, supported versions are utilized for new deployments, maintaining consistency and security. Existing database servers using the deprecated profile can continue to operate and may still be patched (if updates are compatible), but the profile itself is excluded from future provisioning tasks.

Option A is correct because deprecation explicitly prevents the profile version from being selected for new provisioning, aligning with NDB’s lifecycle management.

Option B (It can be used in provisioning) is incorrect as this contradicts the purpose of deprecation.

Option C (Any database server using that profile will be updated to the latest software profile) is incorrect because deprecation does not automatically update existing servers; it only affects new provisioning.

Option D (Any database server using that software profile can no longer be patched) is incorrect because patching existing servers is still possible if compatible updates exist, independent of the profile’s deprecated status.

Deprecation is a deliberate administrative action to phase out outdated profiles while preserving existing deployments.

References

Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Deprecating Software Profile Versions

Nutanix Support & Insights, Knowledge Base Article: "Software Profile Management in NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Blueprint, Section 4: Manage Database Software Profiles

A database administrator wanting to be notified in advance before any database clones are removed using a removal schedule can configure this directly within the NDB interface. The "Update Removal Schedule" feature includes an option labeled "Create an Alert Before Removal," which is pre-selected as non-optional by default but can be customized. Selecting this option generates an alert (e.g., via email or the NDB dashboard) prior to the scheduled clone removal, allowing the administrator to take action if needed. This is the most efficient and built-in method, avoiding the complexity of custom scripts or reports.

Option A (Create a Playbook to create an alert based on the removal event) is incorrect because a Playbook is an advanced automation tool, not the simplest solution for this notification need.

Option B (Select the Create an Alert Before Removal option) is correct as it is a native NDB feature designed for this purpose.

Option C (Build a custom report in Prism to report on these events) is incorrect because Prism reports are for historical analysis, not real-time notifications.

Option D (Configure SMTP alerts for all actions in NDB) is incorrect because configuring SMTP for all actions is overly broad and less targeted than the specific alert option.

This ensures timely notifications with minimal configuration.

References

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Managing Clone Removal Schedules

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

NDB requires management and storage connectivity to a registered Nutanix cluster. TCP 9440 carries Prism REST API communication between NDB components and the Nutanix cluster. TCP 3205 and 3260 support iSCSI redirection/data and standard iSCSI control traffic used when NDB attaches Volume Group disks. Therefore, both option B and option D must be allowed through the segmented network. Port 443 is used for HTTPS communication in other NDB paths, but it is not the required Prism/CVM port represented by this question. Ports 1433 and 5432 are database listener ports for Microsoft SQL Server and PostgreSQL, respectively, rather than NDB-to-CVM infrastructure ports. The source answer “D” is incomplete; the verified answer is B and D. Nutanix port reference

================

For restoring a database provisioned on Storage Spaces, especially when virtual disks are shared among multiple databases, the supported method is a copy-based restore via the NDB GUI. This method allows for a precise and controlled restoration process suitable for shared storage environments.