How should a patch be downloaded to perform a One-Click Upgrade of an NDB Environment with access to the Internet?
For a One-Click Upgrade of an NDB environment with internet access, the patch should be downloaded directly within the NDB interface. The 'Administrator > Maintenance' section of NDB provides an option to connect to the Nutanix download repository (e.g., https://download.nutanix.com) and download the latest patch or upgrade bundle automatically. This streamlined process ensures compatibility and simplifies the upgrade workflow. The One-Click Upgrade feature then applies the downloaded patch to update NDB components efficiently.
Other options are incorrect:
A . Download the patch from the Nutanix Support Portal and upload via the NDB CLI: This is suitable for dark sites but unnecessary with internet access, as NDB can download directly.
C . Open Prism Central and deploy the current version of NDB from the Apps and Marketplace section: This is for initial deployment, not upgrading an existing NDB instance.
D . Open Prism Element and use LCM to update the software: Lifecycle Manager (LCM) is for Nutanix cluster updates, not NDB-specific upgrades.
Thus, the verified answer is B, leveraging NDB's built-in maintenance capabilities.
Official Nutanix Database Automation Reference:
Nutanix Database Management & Automation (NDMA) course, Module 2: Deploying and Configuring an NDB Solution, Lesson 2.4: Updating NDB with Internet Access.
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 2: Deploy and Configure an NDB Solution, Objective 2.3: Perform NDB Updates (applicable to v6.10).
Nutanix NDB Administration Guide: 'One-Click Upgrade Process' section.
An administrator has been asked to patch several Nutanix database server VMs. Prior to patching, what should the administrator configure?
Before patching several Nutanix database server VMs using the 'Patch OS now' feature in NDB, the administrator must configure a Repository. A repository (e.g., a custom patch repository or Nutanix-provided source) contains the OS updates or patches (e.g., for Windows or Red Hat-based systems). NDB requires this repository to be specified to fetch and apply the patches, ensuring the database VMs are updated from a validated source.
Other options are unrelated to patching:
B . Active Directory Access: Used for authentication, not patching.
C . pulse: Refers to Nutanix Pulse for support, not patch configuration.
D . An SMTP Server: Configured for alerts, not patching.
Thus, the verified answer is A, reflecting the patching prerequisite.
Official Nutanix Database Automation Reference:
Nutanix Database Management & Automation (NDMA) course, Module 6: Maintenance and Patching, Lesson 6.3: Creating Maintenance Plans.
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Knowledge Objectives, Section 6: Optimize NDB Solutions, Objective 6.3: Manage Maintenance Plans (applicable to v6.10).
Nutanix NDB Administration Guide: 'Configuring Patch Repositories' section.
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
Barbara Nguyen
15 days agoJoseph Rodriguez
28 days agoStephen Harris
2 months agoBarbara Murphy
2 months agoKimberly Parker
2 months agoMichael Bell
3 months agoCharles Wilson
2 months agoKimberly Flores
2 months agoRyan Carter
2 months agoKaren Peterson
3 months agoAnthony Howard
3 months agoJolanda
3 months agoSamira
4 months agoGracia
4 months agoKimberely
4 months agoJettie
4 months agoKeshia
5 months agoTiffiny
5 months agoCarin
5 months agoMurray
6 months agoYaeko
6 months agoLinsey
6 months agoBilly
6 months agoAsha
7 months agoViola
7 months agoTrina
7 months agoTarra
7 months agoRose
8 months agoPete
8 months agoJosefa
8 months agoTarra
9 months agoPa
9 months agoDelisa
9 months agoLettie
9 months agoKyoko
10 months agoOretha
10 months agoGail
10 months agoJanella
10 months agoNathalie
1 year 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
2 years agoDona
2 years agoMignon
2 years agoGerald
2 years agoRegenia
2 years agoTommy
2 years agoFatima
2 years agoAmina
2 years 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