Verified & Correct NCP-DB-6.5 Practice Test Reliable Source Feb 15, 2025 Updated [Q66-Q86]

February 15, 2025February 15, 2025 examdumpsVerified & Correct NCP-DB-6.5 Practice Test Reliable Source Feb 15, 2025 Updated [Q66-Q86] 0 Comment

Tags: NCP-DB-6.5 download pdf, NCP-DB-6.5 key concepts, NCP-DB-6.5 reliable exam pattern, NCP-DB-6.5 reliable study materials, NCP-DB-6.5 valid exam cram, NCP-DB-6.5 valid guide files, NCP-DB-6.5 valid test pass4sure

4.7/5 - (7 votes)

Verified & Correct NCP-DB-6.5 Practice Test Reliable Source Feb 15, 2025 Updated

Free Nutanix NCP-DB-6.5 Exam Files Downloaded Instantly

Nutanix NCP-DB-6.5 Exam Syllabus Topics:

Topic	Details
Topic 1	Apply procedural concepts to test and publish database patches Protect NDB-managed Databases Using Time Machine
Topic 2	Given a scenario, troubleshoot NDB operations Determine the correct method to apply Linux OS patches
Topic 3	Describe NDB features and benefits Define database and NDB terminology
Topic 4	Monitor Alerts and Storage Usage Within an NDB Implementation Apply procedural concepts to add Nutanix clusters to NDB

Q66. Which policies define Time Machine data availability across multiple registered clusters in NDB?

Recovery Plans

Data Access Management

Data Protection

Service Level Agreements

Q67. When trying to restore a database via Time Machine (TM), the option to restore data to a Point in Time is not available.
What should the administrator do to enable Point in Time Recovery?

Use an SLA that supports Continuous Log retention.

Update the TM schedule to perform DB Log catch up.

Take a Manual snapshot and use it for DB recovery.

Use Brass SLA & update the Log catch up frequency.

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.
Reference: Nutanix Support & Insights, section “NDB Time Machine Point in Time Recovery”

Q68. Refer to the exhibit.

An administrator attempts to provision their first clustered database environment with NDB. The operation fails with the Operation Error shown in the exhibit.
Which database engine was being deployed during this operation?

Oracle

MySQL

Microsoft SQL

PostgreSQL

Q69. Which response shows two ways to upgrade an NDB Server?

Out-of-Place Upgrade and In-place Upgrade

One-click Upgrade and In-place Upgrade Auto

Upgrade and Manual Upgrade

One-click Upgrade and Offline Upgrade

There are two ways to upgrade an NDB Server: one-click upgrade and offline upgrade. One-click upgrade is the recommended method, as it automatically downloads and installs the latest NDB software version from the Nutanix portal. Offline upgrade is an alternative method, which requires you to manually download the NDB software bundle and upload it to the NDB Server VM. Both methods require you to have a valid Nutanix account and an internet connection.
Reference: Nutanix Certified Professional – Database Automation (NCP-DB), Section 6 – Administer an NDB Environment Database (NCP-DB) Exam Blueprint Guide – Nutanix, Page 10, Objective 6.2 Nutanix Database Management & Automation (NDMA) course, Module 6, Lesson 6.1 – NDB Software Upgrade

Q70. What is the minimum frequency in minutes configurable for NDB Log Catch-up operation?

120

Q71. An administrator needs to perform patching on a MongoDB server cluster within an NDB environment.
How should the administrator accomplish this task?

Perform a rolling upgrade, applying the patch to the primary member first, followed by the secondary members.

Apply the patch to all nodes at once.

Perform a rolling upgrade, applying the patch to the secondary members first, followed by the primary member.

Disable the replica set while patching.

Q72. An administrator needs to replace the default Nutanix self-signed certificates in Era.
Which SSL Certificate file format is supported?

PKCS#7

DER encoded binary X.509

Base-64 encoded X 509

PKCS#12

According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era supports x509 certificates in Base-64 encoded PEM format1. This format is used when an administrator needs to replace the default Nutanix self-signed certificates in Era1.

Q73. What feature of Era allows an administrator to create Time Machine policies in a Multi-Cluster configuration?

Data Access Management

Global Data Protection

Time Machine Cloud Orchestration

Global Service Level Agreement

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.

Q74. Which NDB feature collects logs and snapshots from databases?

Database Restore

Time Machine

SLA

One-click Patching

Q75. An administrator needs to deploy a cumulative update (CU) for SQL Server.
What steps would the administrator take to prepare this deployment with NDB?

Apply the patch to the profile VM, delete the existing Software Profile and create a new Software Profile using the profile VM as the source.

Create a new Software Profile version using the CU executable and publish that version.

Apply the patch to the profile VM, then create a new Software Profile version using the profile VM as the source.

Create a new Software Profile using the CU executable and publish that profile.

The correct answer is C because it follows the recommended procedure for applying a CU to a SQL Server Software Profile in NDB. By applying the patch to the profile VM, the administrator ensures that the CU is compatible with the existing Software Profile settings and configuration. By creating a new Software Profile version, the administrator preserves the previous version of the Software Profile for rollback purposes and allows the new version to be tested and published. Option A is incorrect because it deletes the existing Software Profile, which may cause data loss and prevent rollback. Option B is incorrect because it does not apply the patch to the profile VM, which may result in errors or inconsistencies in the Software Profile. Option D is incorrect because it creates a new Software Profile instead of a new version, which may cause confusion and duplication.
Reference: The following sources provide more information about the Software Profile management and patching in NDB:
Nutanix Database Management & Automation (NDMA) course, Module 5: Patching Databases Using NDB, Lesson 5.2: Creating and Modifying Software Profiles Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 4 – Operate and Maintain an NDB Environment Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.2:
Creating and Modifying Software Profiles
Nutanix Database Service (NDB) User Guide, Chapter 5: Patching Databases Using NDB, Section 5.3:
Testing and Publishing Database Patches

Q76. An administrator needs to make new VLANs available when provisioning a Oracle cluster database, which have been added to NDB via the Administration menu.
What needs to be done to expose the new VLANs for provisioning?

Create a new VLAN in Prism Element and discover it in NDB.

Update the Network Profile to include the new VLANs.

Update Prism Element with the new VLAN and discover it in NDB.

Create a new Network Profile with the new VLANs.

Q77. An administrator needs to roll back an Oracle patch on a database server VM using NDB.
What is required for this action to be successful?

The patch must have been applied using NDB.

The database must be shut down.

The patch must have been applied on Grid home only using NDB.

The database must be in read-only mode.

To roll back an Oracle patch on a database server VM using NDB, the patch must have been applied using NDB in the first place. This is because NDB maintains a patch inventory and history for each database server VM and database that it manages. NDB uses this information to determine which patches can be rolled back and how to revert the changes made by the patch. If the patch was applied outside of NDB, NDB would not have the patch information and would not be able to roll back the patch.
Therefore, the patch must have been applied using NDB for the rollback action to be successful. The other options are not required for the rollback action. The database does not need to be shut down or in read-only mode, as NDB can perform the rollback operation online. The patch does not need to be applied on Grid home only, as NDB can roll back patches applied on both Grid home and Database home.
Reference: Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Section 4 – Operate and Maintain an NDB Environment, Objective 4.4: Determine the correct method to apply Linux OS patches Nutanix Database Management & Automation (NDMA) Course, Module 5: Nutanix Database Service (NDB) Patching, Lesson 5.1: Patching Overview, Topic: Patching Concepts
[Nutanix Database Service (NDB) User Guide], Chapter 7: Patching, Section: Rolling Back a Patch

Q78. While adding Time Machine data access to a Nutanix cluster, when is a storage container mapping needed

When the source database and NDB Server containers are different.

When the source database and NDB VM are on the same container.

When the source and destination database containers are different.

When the source database and NDB provisioning container are the same.

Q79. How should an administrator create a database clone using the Era IJI?

Select Databases, Clones, Create Clone.

Select Databases, Sources, select a source database and then choose Create Clone.

Select Time Machines, select e source database end then choose Create Clone.

Select Database Server VMs, select a database server VM and then choose Create Clone.

In Nutanix Database Automation (NCP-DB), the Time Machine feature is used for protecting databases and creating database clones. To create a database clone using the Era Interface, an administrator should select Time Machines, select a source database, and then choose Create Clone12. This process allows the administrator to create a copy of the source database at a specific point in time1.

Q80. What is required to create an NDB Software Profile?

Installer package for database software

Database server VM registered with NDB

Patch file for the installed databases

OS image registered with Prism Element

Q81. An administrator needs to distribute NDB management plane components.
Which NDB HA VM needs to be deployed on the same L2 network?

NDB Agent

API Server

Repository VMs

HA Proxy VMs

NDB High Availability (HA) is a feature that ensures the availability and reliability of the NDB management plane components, such as the API Server, the Repository VMs, and the NDB Agents. To enable NDB HA, you need to deploy at least three HA Proxy VMs on the same L2 network as the NDB Server VM. The HA Proxy VMs act as load balancers and health monitors for the NDB management plane components, and they also provide a single endpoint for accessing the NDB APIs and UI.
Reference: Nutanix Certified Professional – Database Automation (NCP-DB), Section 2 – Deploy and Configure an NDB Solution Database (NCP-DB) Exam Blueprint Guide – Nutanix, Page 7, Objective 2.3 Nutanix Database Management & Automation (NDMA) course, Module 2, Lesson 2.3 – NDB High Availability

Q82. An administrator enables NDB Multi-Cluster on Cluster

Cluster B is then registered with NDB.
What are the different NDB Service VMs present in each Nutanix cluster?B. Cluster A: 1 NDB Server Cluster B: 1 NDB Agent

Cluster A: 1 NDB Agent
Cluster B: 1 NDB Server, 1 NDB Agent

Cluster A: 1 NDB Server, 1 NDB Agent
Cluster B: 1 NDB Agent

Cluster A: 1 NDB Agent
Cluster B: 1 NDB Server

Q83. Where are two locations an administrator would find the size of a Source Database? (Choose two.)

On the Era Dashboard Database Summary Table under Source Database.

Under the Capacity widget on the Database Server VMS > List database summary page.

On the Databases > Sources table.

On the Profiles > Database Parameters list for the assigned DB Parameter Profile.

Option A: On the Era Dashboard Database Summary Table under Source Database. The dashboard provides a summary of the databases, including their sizes1.
Option B: Under the Capacity widget on the Database Server VMS > List database summary page.
While this might provide information about the capacity, it does not specifically provide the size of a Source Database.
Option C: On the Databases > Sources table. This table provides detailed information about the databases, including their sizes1.
Option D: On the Profiles > Database Parameters list for the assigned DB Parameter Profile. This list provides parameters for the database but does not provide the size of a Source Database.

Q84. A development team has requested that an administrator provide them a copy of the production Finance database. The business requires that any financial data is masked before going into development.
How should the administrator create a clone with masked data for the development environment?

From the Time Machine, create a clone and paste the masking commands in the post-clone field of the Pre-Post Commands section.

1. Create a masking script on the source DB VM, Dev VM or SW Profile VM.
2. Create the clone from the Time Machine and define the post-clone option with the full pathname of the masking script.

1. Create a script to mask the data.
2. Create the clone from the Time Machine and define the post-clone option with the full pathname of the masking script.

From the Time Machine, create a clone and paste the masking commands in the pre-clone field of the Pre-Post Commands section.

According to the Nutanix Database Automation (NCP-DB) course, the Pre-Post Commands section allows the administrator to specify custom scripts that can be executed before or after the clone operation1. The masking script can be created on any of the VMs that have access to the source database, such as the source DB VM, the Dev VM, or the SW Profile VM2. The script should contain the commands to mask the sensitive data in the Finance database, such as replacing the real values with dummy values or encrypting the data2. The administrator can then create the clone from the Time Machine and define the post-clone option with the full path and name of the masking script1. This will ensure that the script is executed after the clone is created, and the data is masked before it is available for the development team1. The other options are not correct, as they either use the wrong field (pre- clone instead of post-clone), or do not specify where to create or store the masking script.
Reference: 1: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson
4.4: Pre-Post Commands, slide 5
2: Nutanix Database Automation (NCP-DB) course, Module 4: Database Cloning, Lesson 4.4: Pre-Post Commands, slide 7

Q85. How can HA drivers for a Database VM be upgraded?

One-click software upgrade

Database VM OS patching

LCM driver upgrade

Database software patching

HA drivers are software components that enable high availability features for database VMs, such as failover, fencing, and heartbeat. HA drivers can be upgraded using the Life Cycle Management (LCM) feature of Nutanix Prism. LCM can detect the available updates for HA drivers and apply them to the database VMs in a non-disruptive manner. LCM can also perform health checks and pre-upgrade validations to ensure the successful completion of the upgrade process. One-click software upgrade is a feature of Nutanix Era that allows you to upgrade the Era software itself, not the HA drivers. Database VM OS patching is a feature of Nutanix Era that allows you to patch the operating system of the database VMs, not the HA drivers. Database software patching is a feature of Nutanix Era that allows you to patch the database software of the database VMs, not the HA drivers.
Reference: Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 3: Configuring NDB High Availability, Slide 9: HA Driver Upgrade Nutanix Certified Professional – Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.4: Upgrade databases

Q86. What is the terminology used for registering an existing database with Era?

Greenfield Database

Brownfield Database

Cloned Database

Source Database

In the context of Nutanix Era, the term “Brownfield Database” is used to refer to an existing database that is registered with Era1. This process allows Era to bring Database as a Service (DBaaS) capabilities to your existing database2. It’s important to note that before you register a database with Era, certain prerequisites must be met3.

Loading …