Nutanix NCP-DB-6.5 Test Engine Dumps Training With 148 Questions [Q84-Q102]

NCP-DB-6.5 Nutanix

admin -

November 30, 2024

Rate this post

Nutanix NCP-DB-6.5 Test Engine Dumps Training With 148 Questions

NCP-DB-6.5 Questions Pass on Your First Attempt Dumps for Nutanix Certified Professional (NCP) Certified

Nutanix NCP-DB-6.5 Exam Syllabus Topics:

Topic	Details
Topic 1	Apply procedural concepts to provision databases Create, delete, and modify SLA retention policies
Topic 2	Given a scenario, troubleshoot NDB operations Determine the correct method to apply Linux OS patches
Topic 3	Given business requirements, perform a database clone Apply procedural concepts to register database server VMs and databases
Topic 4	Apply procedural concepts to test and publish database patches Protect NDB-managed Databases Using Time Machine
Topic 5	Deploy and Configure an NDB Solution Apply procedural concepts to restore source databases
Topic 6	Monitor Alerts and Storage Usage Within an NDB Implementation Apply procedural concepts to add Nutanix clusters to NDB
Topic 7	Apply procedural concepts to create Data Access Management (DAM) policies Operate and Maintain an NDB Environment

NEW QUESTION 84
A developer with RBAC privileges in Era needs to refresh an existing DB Clone.
What steps must the developer take to perform the refresh?

Navigate to Databases > Sources, Select the appropriate Database from the table and Refresh Clone from the Database Actions menu.

Navigate to Databases > Clones, Select the appropriate clone from the table, click Refresh, select the desired Point In Time or Snapshot and click Refresh

Navigate to Time Machines Select the appropriate Database Time Machine from the table end Refresh Clone from the Actions menu.

Navigate to Databases > Clones, Select the appropriate clone from the table, choose

According to the Nutanix Database Automation (NCP-DB) learning documents, to refresh an existing DB Clone, a developer with RBAC privileges in Era needs to navigate to Databases > Clones. From there, they select the appropriate clone from the table, click Refresh, select the desired Point In Time or Snapshot, and then click Refresh12. This process allows the developer to update the cloned database3.

NEW QUESTION 85
Which policies define Time Machine data availability across multiple registered clusters in NDB?

Recovery Plans

Data Access Management

Data Protection

Service Level Agreements

The recovery plans policy defines the Time Machine data availability across multiple registered clusters in NDB. The recovery plans policy allows the database administrator to specify the source and target clusters, the frequency and retention of the cross-cluster snapshots, and the network and compute profiles for the recovery operations. The recovery plans policy helps to ensure the disaster recovery and business continuity of the NDB-managed databases in case of a cluster failure or outage.
The data access management policy defines the access permissions and roles for the NDB users and groups. The data access management policy allows the database administrator to grant or revoke access to the NDB instance, the database server VMs, the databases, and the database operations. The data access management policy helps to ensure the security and compliance of the NDB-managed databases and users.
The data protection policy defines the backup and restore settings for the NDB-managed databases. The data protection policy allows the database administrator to specify the frequency, retention, and compression of the database snapshots, and the backup location and encryption for the database backups. The data protection policy helps to ensure the backup and recovery of the NDB-managed databases within the same cluster.
The service level agreements policy defines the performance and availability metrics for the NDB- managed databases. The service level agreements policy allows the database administrator to monitor and enforce the database uptime, latency, throughput, and IOPS. The service level agreements policy helps to ensure the quality of service and performance of the NDB-managed databases.
Reference: Nutanix Database Management & Automation Training Course, Module 4: Nutanix Era Configuration, Lesson 4.1: Nutanix Era Configuration, slide 9.
Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slides 8, 12, 16, 20.
Nutanix Database Management & Automation Training Course, Module 6: Nutanix Era Disaster Recovery, Lesson 6.1: Nutanix Era Disaster Recovery, slides 5-7.

NEW QUESTION 86
An administrator needs to provide the least-privilege access to a newly-hired engineer whose task is to add new VLANs or IP Pools in NDB.
Which role should the administrator select to complete this task?

Database Administrator

Super Administrator

Database Infrastructure Administrator

Infrastructure Administrator

An Infrastructure Administrator is a role in NDB that has the permission to manage network and storage resources, such as VLANs, IP Pools, and Storage Containers. This role is suitable for the engineer who needs to add new VLANs or IP Pools in NDB. The other roles have either more or less privileges than required for this task. A Database Administrator can manage databases and database server VMs, but not network and storage resources. A Super Administrator can manage all aspects of NDB, but this is more than the least-privilege access needed. A Database Infrastructure Administrator can manage both databases and network and storage resources, but this is also more than the least-privilege access needed.
Reference: Nutanix Support & Insights, section “NDB Roles and Permissions”

NEW QUESTION 87
An administrator has applied an Oracle security patch to a database server VM registered in Era.
How do you make this change available to other existing database instances?

Create a n.. software profile version from the patched VM.

Merge the changes into an existing software profile.

Create a new software profile in Era from the patched VM.

Nutanix Database Service (NDB) uses software profiles for database patching to keep your databases secure and optimized1. When a new database is provisioned, it will be on your current environment’s database version to maintain consistency and stop version sprawl1. Therefore, after an administrator has applied an Oracle security patch to a database server VM registered in Era, the change can be made available to other existing database instances by creating a new software profile in Era from the patched VM1.

NEW QUESTION 88
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

NEW QUESTION 89
An administrator wants to enable Multi-Cluster management on an Era installation.
Which prerequisites must be satisfied to complete this task?

AOS version supported, static VLAN setup in Era Networks

Database Server VMS version supported. Network Profiles setup

Hardware version supported, DHCP Network enabled on Nutanix cluster

Hypervisor version supported, port 9440 open between Era VM and clusters

For enabling Multi-Cluster management on an Era installation, the hypervisor version must be supported and port 9440 must be open between the Era VM and clusters. This ensures that the Era VM can communicate with the clusters for management tasks1.

NEW QUESTION 90
Which two options can NDB leverage to refresh a database clone? (Choose two.)

Cerebro logs

Snapshots

Transaction logs

Templates

NDB can leverage snapshots and transaction logs to refresh a database clone to the latest state of the source database. Snapshots are point-in-time copies of the database that are stored on the Nutanix cluster. Transaction logs are records of the changes made to the database after the snapshot was taken.
NDB can use either snapshots or transaction logs, or a combination of both, to refresh a database clone.
Cerebro logs and templates are not used for refreshing database clones. Cerebro logs are used for log catch-up operations, which are different from refresh operations. Templates are used for provisioning new databases, not for refreshing existing ones.
Reference: Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.3 – Refreshing Clones Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Clone Database Management

NEW QUESTION 91
When registering a new Nutanix Cluster with Era, what component is installed on the target Nutanix cluster via the Register Nutanix Cluster workflow?

Era Sewer

Era Agent

API Server

Repository Server

When registering a new Nutanix Cluster with Era, the Era Agent is installed on the target Nutanix cluster via the Register Nutanix Cluster workflow1. This agent is crucial for the functioning of the Nutanix Database Service (NDB) as it helps in managing and optimizing database workloads2. It also enables the application of procedural concepts to add Nutanix clusters to NDB2.

NEW QUESTION 92
An administrator needs to perform LCM upgrades on an AHV cluster registered with NDB. The cluster hosts NDB-provisioned database server VMs that are part of a database server cluster.
What should the administrator do to allow the DB Server VMs to stay available while the cluster is being upgraded?

Update Nutanix Cluster

Set VM-Host Affinity

Remove Nutanix Cluster

Unset VM-Host Affinity

The correct answer is B because setting VM-Host affinity ensures that the DB Server VMs are not migrated to another host during the LCM upgrade process. This way, the DB Server VMs can continue to serve the database requests without interruption. Option A is incorrect because updating the Nutanix cluster does not prevent the DB Server VMs from being moved to another host. Option C is incorrect because removing the Nutanix cluster from NDB will make the DB Server VMs unmanaged by NDB and lose the benefits of NDB features. Option D is incorrect because unsetting VM-Host affinity will allow the DB Server VMs to be migrated to another host during the LCM upgrade process, which may cause downtime or performance degradation.
Reference: The following sources provide more information about the LCM upgrades and VM-Host affinity in NDB:
Nutanix Database Management & Automation (NDMA) course, Module 6: Administering an NDB Environment, Lesson 6.3: Performing NDB Software Upgrades Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 6 – Administer an NDB Environment Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section
8.3: Performing NDB Software Upgrades
Nutanix Support & Insights, Your guide to the Upgrades, LCM Design
Nutanix Life Cycle Manager Guide, Chapter 3: Upgrading Software and Firmware, Section 3.2:
Preparing for an Upgrade, VM-Host Affinity

NEW QUESTION 93
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.

A Network Profile is a collection of network settings that are used to provision database server VMs in NDB. A Network Profile can include one or more VLANs, IP ranges, and DNS servers. To make new VLANs available when provisioning an Oracle cluster database, you need to update the Network Profile to include the new VLANs. You can do this by editing the existing Network Profile or creating a new one with the new VLANs. You do not need to create or update the VLANs in Prism Element, as NDB can discover the VLANs configured in AHV1.
Reference: Nutanix Database Management & Automation (NDMA) course, Module 2, Lesson 2.4 – Network Profiles Nutanix Support & Insights, Nutanix NDB User Guide v2.5, Network Profiles Nutanix Certified Professional – Database Automation (NCP-DB), Section 2 – Deploy and Configure an NDB Solution

NEW QUESTION 94
What are the three severity levels displayed under the Alert dashboard?

Critical. Waiting, Failed

Failed, Warning, Stopped

Critical, Warning Info

Failed, Warning, Error

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.

NEW QUESTION 95
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.

NEW QUESTION 96
An administrator needs to patch an Oracle Database Server VM and must ensure Grid home is allocated sufficient storage space.
At a minimum, how much space must be available for Grid home prior to completing this task?

5GB

10GB

15GB

20 GB

When patching an Oracle Database Server VM, it’s important to ensure that there is sufficient storage space allocated for the Grid home. A minimum of 10GB space is required for this purpose to accommodate the patching process without storage constraints.
Reference: Nutanix Database Automation documentation, particularly in the sections discussing Oracle database server VM management and patching requirements.

NEW QUESTION 97
An administrator needs to apply a minor version upgrade of the PostgreSQL software to an Era provisioned instance.
Which step should the administrator take before applying the patch?

Create a new software profile.

Put the database instance into maintenance mode.

Go to the Software Profile Version widget and click update.

Migrate a new software profile.

Nutanix Database Service (NDB) supports automated minor version upgrades for PostgreSQL1. Before applying the patch, the administrator should create a new software profile2. This is because the software profile contains the database engine binaries and other software required to run the database engine2.
Therefore, to apply a minor version upgrade, a new software profile with the updated binaries needs to be created2. Once the new software profile is created, it can be used to patch the PostgreSQL database2.

NEW QUESTION 98
A request is received to refresh a database clone from a new manual snapshot. When the administrator attempts to create the new snapshot from the Time Machine, it is in a Frozen state.
What causes a Time Machine to enter the Frozen state and what are the administrator’s options to complete the request?

Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: The Time Machine must be paused, then the database re-registered with a new Time Machine and a new clone created.

Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: To complete the request the database must be re-registered in NDB, create a new Time Machine and create a new clone.

Cause: The Time Machine enters a Frozen state after too many snapshot or log catchup failures.
Resolution: Remediate the snapshot or log catchup failures, this thaws the Time Machine, allowing normal operations to continue and the request can be completed.

A Time Machine is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention. When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de-registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze.
Reference: Nutanix Certified Professional – Database Automation (NCP-DB) v6.5, Section 5 – Protect NDB-managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: Time Machine Concepts Nutanix Support & Insights, TN-2101: Nutanix Database Service Time Machine Under the Hood, Section: Time Machine States and Transitions

NEW QUESTION 99
A customer has NDB configured to create snapshots of their production databases every 4 hours.
A developer requires a copy of the current production data at 7:00am of each day.
What is the most efficient way to meet this requirement?

Authorize the developer in RBAC to create clones as required.

Run a script which creates a clone from the latest snapshot at 7:00am.

Configure Time Machine to create a clone from a daily snapshot at 7:00am.

Configure a done with a daily Data Refresh Schedule at 7:00am.

NEW QUESTION 100
In an Oracle upgrade scenario using Era. if the source database is on a nor-Nutanix platform, is it possible to upgrade it with an Era workflow?

Yes, it is possible to upgrade database instance on a non-Nutanix platform.

Yes, only if the nan-Nutanix platform is big-endian platform,

No, the database instaru:e must be Era managed to Be upgraded

Yes, only if the nori-Nutanix platform is little-endian platform.

According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era is a database management tool that automates and simplifies database operations, including provisioning, patching, upgrading, and more1. However, for a database to be managed by Era, it must be registered with Era1. This means that if a database is on a non-Nutanix platform, it cannot be directly upgraded using an Era workflow. It must first be migrated to a Nutanix platform and registered with Era before it can be managed and upgraded using Era1.

NEW QUESTION 101
What does the Era I-Click Provisioning service do?

Cloning with security inserting pre and post masking scripts

Customizable recovery SLAs for continuous RPOs

Create space-efficient database snapshots

Create space-efficient clones and zero-byte database clones

The Era One-Click Provisioning service in Nutanix Database Automation (NCP-DB) simplifies and automates database administration. It brings one-click simplicity to database provisioning and life-cycle management. This service enables database administrators to provision, clone, and refresh the database clones to any point in time1. Specifically, it enables the creation of space-efficient clones and zero-byte database clones1. This is part of Era’s copy data management service, which includes components like Time Machine, one-click cloning and refresh, and one-click backup21.

NEW QUESTION 102
An administrator is adding a stretched VLAN in NDB.
Which VLAN type(s) will satisfy this task?

Only VLANs that are not managed in NDB

Only static VLANs that are managed in NDB

Only dynamic VLANs

Both static and dynamic VLANs

Loading …