For supported Linux based database VM's managed by NDB, how would an administrator keep software profiles updated for provisioning new database VMs?
For supported Linux-based database VMs managed by NDB, keeping software profiles updated for provisioning new database VMs requires a structured process. The administrator must first apply the necessary patches (e.g., OS updates and database engine patches) to an existing database VM for each supported database engine (e.g., PostgreSQL, Oracle). Then, a new software profile version must be created using the updated VM as the source. This new version captures the patched configuration and can be used to provision new VMs, ensuring they are deployed with the latest updates.
Option A (Create a Maintenance window under the policy menu, then under Database VM, add the database VMs to that maintenance window and check both Database and Operating system updates) is incorrect because a Maintenance Window schedules updates for existing VMs, not for updating software profiles for new provisions.
Option B (Apply patches to a database VM for each supported database engine, then create a new software profile version for each supported database VM for each one using the updated database VM as the source) is correct as it follows the standard NDB process for profile updates.
Option C (Associate the newly provisioned database VMs with a maintenance window so they are kept updated) is incorrect because this applies to ongoing maintenance, not initial profile updates for provisioning.
Option D (In the Administrator menu drop down, go the Maintenance tab and choose Download Upgrade) is incorrect because downloading upgrades is part of the patch process, not the profile creation step.
This method ensures new VMs are provisioned with the latest software configurations.
Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Updating Software Profiles
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles
An administrator wants to manage an additional database on an existing database server VM.
What field should the administrator look in for this new database?
When an administrator wants to manage an additional database on an existing database server VM in NDB, the first step is to identify if the database is already recognized by NDB. The 'Unregistered Databases' field or section within the NDB interface lists databases that are present on a registered database server VM but have not yet been registered with NDB. This allows the administrator to discover and register the new database, enabling full management capabilities (e.g., provisioning, cloning, or patching). Once registered, the database will move to the 'Registered Databases' section.
Option A (Unregistered Databases) is correct as it is the initial field to check for new, unmanaged databases on the VM.
Option B (Database Server VM) is incorrect because this refers to the VM itself, not the databases it hosts.
Option C (Registered Databases) is incorrect because this lists only databases already managed by NDB, not new ones.
Option D (Database Name in NDB) is incorrect as it is not a specific field but a general Reference:, lacking a defined location.
The administrator should use the Unregistered Databases section to proceed with registration.
Nutanix Database Service (NDB) User Guide, Chapter 2: Deploying and Configuring an NDB Solution, Section: Registering Additional Databases
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 2: Deploy and Configure an NDB Solution
An administrator needs to distribute NDB management plane components.
Which NDB HA VM needs to be deployed on the same L2 network?
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
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 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
An administrator has been tasked with OS and database patching in a Nutanix NDB environment. The administrator wishes to automate these activities.
What should the administrator configure to accomplish this task?
To automate OS and database patching in a Nutanix NDB environment, the administrator should configure a Maintenance Window. A Maintenance Window in NDB allows the administrator to schedule automated patching tasks (e.g., OS updates and database software updates) during specified time periods, minimizing disruption to production workloads. This feature integrates with software profiles and can be set to run periodically or on-demand, ensuring patches are applied efficiently and consistently across the environment.
Option A (Access Control) is incorrect because Access Control manages user permissions, not automation of patching.
Option B (Pulse) is incorrect because Pulse is a monitoring tool, not a scheduling mechanism for patching.
Option C (Maintenance Window) is correct as it provides the scheduling and automation framework for patching activities.
Option D (SMTP Server) is incorrect because SMTP is for email notifications, not patching automation.
This configuration enhances operational efficiency and reliability.
Nutanix Database Service (NDB) User Guide, Chapter 4: Managing Software Profiles, Section: Scheduling Maintenance Windows
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 4: Manage Database Software Profiles
Stephen Harris
2 hours agoBarbara Murphy
13 days agoKimberly Parker
25 days agoMichael Bell
1 month agoCharles Wilson
28 days agoKimberly Flores
20 days agoRyan Carter
15 days agoKaren Peterson
1 month agoAnthony Howard
1 month agoJolanda
2 months agoSamira
2 months agoGracia
2 months agoKimberely
3 months agoJettie
3 months agoKeshia
3 months agoTiffiny
3 months agoCarin
4 months agoMurray
4 months agoYaeko
4 months agoLinsey
5 months agoBilly
5 months agoAsha
5 months agoViola
5 months agoTrina
6 months agoTarra
6 months agoRose
6 months agoPete
6 months agoJosefa
7 months agoTarra
7 months agoPa
7 months agoDelisa
8 months agoLettie
8 months agoKyoko
8 months agoOretha
8 months agoGail
9 months agoJanella
9 months agoNathalie
11 months agoCatarina
1 year agoCornell
1 year agoHyman
1 year agoChau
1 year agoAlverta
1 year agoEleonore
1 year agoKimbery
1 year agoLauran
1 year agoGeorgeanna
1 year agoNieves
1 year agoDona
1 year agoMignon
1 year agoGerald
1 year agoRegenia
1 year agoTommy
1 year agoFatima
1 year agoAmina
1 year agoCaitlin
2 years agoAfton
2 years agoNettie
2 years agoSanda
2 years agoKimi
2 years agoWillis
2 years agoWhitney
2 years agoTran
2 years agoGerman
2 years agoStefanie
2 years agoYesenia
2 years agoTanesha
2 years agoTimothy
2 years agoFredric
2 years agoSabra
2 years agoNadine
2 years agoSimona
2 years agoGlennis
2 years agoVal
2 years agoValentin
2 years agoNikita
2 years agoGeraldine
2 years agoValentine
2 years agoRueben
2 years ago