Refer to the exhibit.

An administrator needs to deploy a new PostgreSQL instance but limit the amount of Max Connections to the DB after it goes live in production.
Which profile should the administrator configure in order to meet the requirement?
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?
Based on the exhibit, the administrator is logged in with the Database Admin account (bsmith@ntnxlab.local), which does not have the permission to create local users on NDB. Only the Super Admin account (bsmith) has this permission, as indicated by the User type column. Therefore, the administrator needs to log out and log in again with the Super Admin account to add a new database admin as a local user to NDB.Reference::Nutanix Database Automation (NCP-DB) Course Details,Nutanix Database Automation (NCP-DB) Certification Details,Nutanix Database Automation (NCP-DB) YouTube Playlist,Nutanix Database Automation User Guide.
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
Adam Murphy
12 days agoGary Taylor
1 month agoKevin Johnson
1 month agoBarbara Nguyen
2 months agoJoseph Rodriguez
2 months agoStephen Harris
3 months agoBarbara Murphy
3 months agoKimberly Parker
4 months agoMichael Bell
4 months agoCharles Wilson
4 months agoKimberly Flores
4 months agoRyan Carter
4 months agoKaren Peterson
4 months agoAnthony Howard
4 months agoJolanda
5 months agoSamira
5 months agoGracia
5 months agoKimberely
6 months agoJettie
6 months agoKeshia
6 months agoTiffiny
7 months agoCarin
7 months agoMurray
7 months agoYaeko
7 months agoLinsey
8 months agoBilly
8 months agoAsha
8 months agoViola
8 months agoTrina
9 months agoTarra
9 months agoRose
9 months agoPete
10 months agoJosefa
10 months agoTarra
10 months agoPa
10 months agoDelisa
11 months agoLettie
11 months agoKyoko
11 months agoOretha
11 months agoGail
12 months agoJanella
12 months agoNathalie
1 year agoCatarina
1 year agoCornell
1 year agoHyman
1 year agoChau
1 year agoAlverta
2 years agoEleonore
2 years agoKimbery
2 years agoLauran
2 years agoGeorgeanna
2 years 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