Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
Scrum
All Vendors
  2. Home
  3. Exams
  4. Nutanix
  5. NCP-DB-6.5

Free NCP-DB-6.5 Exam Braindumps (page: 17)

Page 16 of 38
PDF with 251 Questions

When provisioning an PostgreSQL HA Instance, what are the minimum and maximum number of DB server VMs that can be deployed in a cluster?

  1. Min 2, Max 6
  2. Min 2, Max 4
  3. Min 1. Max 3
  4. Min 3, Max 5

Answer(s): B

Explanation:

When provisioning a PostgreSQL HA Instance using NDB, the minimum and maximum number of DB server VMs that can be deployed in a cluster are 2 and 4, respectively. A PostgreSQL HA Instance is a database instance that provides high availability and fault tolerance for PostgreSQL databases using the Patroni framework. Patroni is a Python-based tool that manages PostgreSQL configuration and performs automatic failover and switchover operations. Patroni relies on a distributed consensus store, such as etcd, Consul, or ZooKeeper, to store and synchronize the cluster state and leader information. NDB supports etcd as the consensus store for PostgreSQL HA Instances. NDB allows the administrator to provision PostgreSQL HA Instances with different sizes and configurations, such as small, medium, large, or custom. The size of the PostgreSQL HA Instance determines the number of DB server VMs, the number of etcd nodes, the CPU, memory, and disk resources, and the replication factor of the database. The minimum number of DB server VMs for a PostgreSQL HA Instance is 2, which corresponds to a small size instance. This configuration provides one leader and one follower DB server VM, and one etcd node. The maximum number of DB server VMs for a PostgreSQL HA Instance is 4, which corresponds to a large size instance. This configuration provides one leader and three follower DB server VMs, and three etcd nodes. The other options are not valid for a PostgreSQL HA Instance, as they either do not provide enough redundancy or exceed the supported limit of DB server VMs.


Reference:

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 2 - Deploy and Configure an NDB Solution, Objective 2.2: Configure an NDB Instance Nutanix Database Management & Automation (NDMA) Course, Module 3: Nutanix Database Service

(NDB) Installation and Configuration, Lesson 3.2: Configuring NDB, Topic: Provisioning PostgreSQL HA Instances
Nutanix Database Service (NDB) User Guide, Chapter 4: Provisioning Databases, Section: Provisioning PostgreSQL HA Instances
[PostgreSQL High Availability: Under the Hood ­ Nutanix.dev], Section: PostgreSQL HA Architecture and Components



Refer to the exhibit.



An administrator is receiving critical NDB email alerts regarding storage for the DBA database, which is a member of a database group.
How would the administrator remediate the issue within NDB?

  1. From the Database Summary page for the DBA database, use the Scale option to grow the storage accordingly.
  2. From the Databases page, select the Database group and Scale the storage from the Database Actions menu.
  3. From Prism Central, add additional storage to the VM, then expand the log storage via the database tools.
  4. From the Alerts page, select the alert, choose Set Status to Resolved, and Scale the storage via the Resolve Now dialogue box.

Answer(s): A

Explanation:

The administrator can remediate the issue of critical storage alerts by scaling up the storage directly from the Database Summary page for that specific DBA database. This action allows for an increase in storage capacity to alleviate space constraints and prevent future critical alerts related to storage space1. The other options are not correct, as they either involve scaling the entire database group, which may not be necessary or desired, or require additional steps outside of NDB, which may not be feasible or efficient.


Reference:

1: Nutanix Database Automation (NCP-DB) course, Module 2: Database Provisioning, Lesson 2.4:
Database Scaling, slide 5



Which action should be completed before updating Oracle Database software?

  1. Verify CVMs have the required memory allocated.
  2. Perform rolling reboots of the Oracle Database VMs.
  3. Verify the Oracle OS version is supported on AHV.
  4. Download the PSU from Oracle support.

Answer(s): D

Explanation:

Before updating Oracle Database software, you need to download the Patch Set Update (PSU) from Oracle support. A PSU is a collection of critical and security patches for Oracle products. You need to have a valid Oracle account and access to the My Oracle Support portal to download the PSU. You also need to check the compatibility and prerequisites of the PSU before applying it to your Oracle Database software. NDB uses out-of-place patching for Oracle, which means you need to create a new software profile version with the patched Oracle software and use it to update your existing databases.


Reference:

Patch Oracle Database Software, Nutanix Support & Insights Nutanix Certified Professional - Database Automation (NCP-DB), Section 4 - Operate and Maintain an NDB Environment
Nutanix Database Management & Automation (NDMA) course, Module 4, Lesson 4.4 - Patching Databases



An administrator has been tasked with restoring an Oracle database that has recently failed. The administrator must restore the database to the prior day's state.
Which two restore options could be used? (Choose two.)

  1. Most Recent Time Available
  2. Snapshot
  3. Tail Logs Backup
  4. Point in Time

Answer(s): B,D

Explanation:

The correct answer is B and D because they are the two restore options that can be used to restore an Oracle database to the prior day's state using Nutanix Era. A snapshot is a point-in-time copy of a database that is stored in the Era Time Machine, which is a distributed file system that collects logs and snapshots from databases. A point in time is a specific moment in time within the retention period of the SLA policy that is applied to the database. By using either of these options, the administrator can select the snapshot or the point in time that corresponds to the prior day's state and restore the database from it. The other options are not correct because they are not restore options that are available in Nutanix Era. Option A is not correct because Most Recent Time Available is not a restore option, but a clone option that creates a clone of the database from the most recent snapshot or log backup. Option C is not correct because Tail Logs Backup is not a restore option, but a backup option that captures the transaction logs of the database that have not been backed up by the SLA policy.


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 Database Services: Database modernization with Era - Now available]






Post your Comments and Discuss Nutanix NCP-DB-6.5 exam with other Community members:

Exam Discussions & Posts