Nutanix NCP-DB Practice Test - Questions Answers, Page 5

List of questions
Question 41

What is causing this issue?
The VLAN is DHCP
The VLAN is static
The VLAN is stretched
The VLAN is IPAM
The correct answer is C because a stretched VLAN is a VLAN that spans across multiple Nutanix clusters, which may cause network conflicts or latency issues when starting the database server. Option A is incorrect because a DHCP VLAN is a VLAN that uses dynamic IP address allocation, which does not affect the database server startup. Option B is incorrect because a static VLAN is a VLAN that uses fixed IP address allocation, which also does not affect the database server startup. Option D is incorrect because IPAM is not a type of VLAN, but a feature of NDB that allows managing IP addresses for database servers and databases.
Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Configuring NDB High Availability
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Knowledge Objectives, Section 2 - Deploy and Configure an NDB Solution
Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section 2.4: Configuring NDB High Availability
Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.5: Managing Networks in NDB
Nutanix Database Service (NDB) User Guide, Chapter 8: Administering an NDB Environment, Section 8.6: Managing IP Addresses in NDB
Question 42

An administrator is trying to register a database server VM with NDB.
Which file types will prevent the registration from being successful if located in the C:\ drive?
Page
System
Database
Backup
Page files are temporary files that Windows uses to store data that does not fit in the physical memory. Page files can interfere with the registration of a database server VM with NDB, as they can cause errors or performance issues. Therefore, page files should be located in a separate drive or partition from the C:\ drive, where the NDB agent and other files are installed. System, database, and backup files do not prevent the registration of a database server VM with NDB, as long as they are not corrupted or incompatible with the NDB requirements.Reference::
Nutanix Database Management & Automation Training Course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2: Configuring an NDB Instance, Slide 13: Registering Database Server VMs
Nutanix Certified Professional - Database Automation (NCP-DB) 5 Exam, Section 4: Operate and Maintain an NDB Environment, Objective 4.1: Apply procedural concepts to register database server VMs and databases
Question 43

Which statement is true regarding the NDB alert retention feature?
NDB supports alert retention globally.
NDB supports retention at the individual policy.
NDB supports retention at the grouped policy.
NDB supports retention at the registered cluster.
The NDB alert retention feature allows the database administrator to configure the duration for which the NDB alerts are stored and displayed in the NDB instance. The NDB alert retention feature supports alert retention globally, meaning that the same retention period applies to all the alerts generated by the NDB instance, regardless of the source cluster, policy, or operation. The database administrator can set the alert retention period from 1 day to 365 days, or choose to retain the alerts indefinitely. The NDB alert retention feature helps to manage the storage space and the visibility of the NDB alerts.
The NDB alert retention feature does not support retention at the individual policy, grouped policy, or registered cluster level. The NDB alert retention feature applies to all the alerts uniformly, and does not allow the database administrator to specify different retention periods for different policies or clusters.
Nutanix Database Management & Automation Training Course, Module 3: Nutanix Era Deployment, Lesson 3.2: Nutanix Era Deployment, slide 11.
Nutanix Database Management & Automation Training Course, Module 5: Nutanix Era Operations, Lesson 5.1: Nutanix Era Operations, slide 6.
Question 44

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 when the database is de-registered without removing the Time Machine. Resolution: To complete the request the database must be re-registered in NDB, this thaws the Time Machine and it resumes operation so the clone can be refreshed.
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
Question 45

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
The error message in the exhibit indicates that the operation failed during the ''Create and Register Database Server VMs'' step because ''Provisioning of all the observers simultaneously took more than two hours.'' This type of error is associated with MySQL, as it involves observers which are a part of MySQL Group Replication, used for ensuring high availability1. The other options are not related to the error message, as they do not use observers or Group Replication for clustering.Reference::
1: Nutanix Database Automation (NCP-DB) course, Module 5: Database High Availability, Lesson 5.2: MySQL Group Replication, slide 7
Question 46

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
Question 47

Which NDB feature collects logs and snapshots from databases?
Database Restore
Time Machine
SLA
One-click Patching
The correct answer is B because the Time Machine feature of NDB collects logs and snapshots from databases and stores them in a distributed file system. The Time Machine enables the administrator to protect, clone, and restore databases using the SLA policies and the NDB UI or API. The Time Machine also manages the replication of database snapshots in an NDB multicluster environment. The other options are not correct because they describe different features or functions of NDB. Option A is not correct because Database Restore is an operation that uses the Time Machine to restore a source database or a clone to a previous point in time. Option C is not correct because SLA is a policy that defines the frequency and retention of database snapshots and logs. Option D is not correct because One-click Patching is a feature that allows the administrator to test, publish, and apply database patches using the NDB UI or API.Reference::Nutanix Database Management & Automation (NDMA) course,Nutanix Certified Professional - Database Automation (NCP-DB) certification,Nutanix NCP-DB Certification Exam Syllabus and Study Guide,Nutanix Support & Insights
Question 48

What happens to the primary member in a MongoDB Server Cluster during the NDB patching process?
It is patched last and is restored to its original state.
It becomes a read-only member during the patching process.
It is skipped during the patching process to ensure no downtime.
It is patched first and then becomes a secondary member.
According to the NDB documentation, the NDB patching process for MongoDB Server Cluster follows these steps1:
NDB identifies the primary member of the MongoDB Server Cluster and patches it first.
NDB triggers a failover to elect a new primary member from the remaining secondary members.
NDB patches the former primary member, which becomes a secondary member after the failover.
NDB patches the remaining secondary members one by one.
NDB verifies the patching status and the cluster health.
This process ensures that the MongoDB Server Cluster always has a primary member available to handle write operations, while minimizing the downtime and the impact on the cluster performance.
Question 49

Refer to the exhibit.
A request is received to provision a new Oracle SIHA DB & VM to test ASMLIB on OEL79 and Oracle 19c. When walking through the provisioning workflow, only ASMFD is available in the ASM Driver drop down.
What is necessary to provision the requested SIHA DB and DB VM with ASMLIB?
Update the software profile to include the ASMLIB driver.
Install ASMLIB on the NDB server.
Update the NDB driver config to enable ASMLIB for Oracle.
Install ASMLIB on the database server.
In the context of Nutanix Database Automation (NCP-DB), when provisioning a new Oracle SIHA DB & VM, if only ASMFD is available in the ASM Driver drop-down, it indicates that ASMLIB is not included in the current software profile. To provision the requested SIHA DB and DB VM with ASMLIB, it's essential to update the software profile to include the ASMLIB driver. This action will enable ASMLIB as an option in the ASM Driver drop-down during the provisioning workflow.
Nutanix Database Automation (NCP-DB) Course Details, Section 2.3: Provisioning Oracle Databases
Nutanix Database Automation (NCP-DB) Certification Details, Objective 2.3: Provision Oracle Databases
Nutanix Database Automation (NCP-DB) YouTube Playlist, Video 2.3: Provisioning Oracle Databases
[Nutanix Database Automation (NCP-DB) User Guide], Section 2.3: Provision Oracle Databases
Question 50

Refer to the exhibit.
An administrator, whose accounts are shown in the exhibit, is trying to add a new database admin as a local user to NDB, but is unable to complete the task.
What is most likely the cause of the issue?
Question