An administrator enables NDB Multi-Cluster on Cluster A. Cluster B is then registered with NDB. What are the different NDB Service VMs present in each Nutanix cluster?
A. Cluster A: 1 NDB Server
Cluster B: 1 NDB Agent
B. Cluster A: 1 NDB Agent
Cluster B: 1 NDB Server, 1 NDB Agent
C. Cluster A: 1 NDB Server, 1 NDB Agent
Cluster B: 1 NDB Agent
D. Cluster A: 1 NDB Agent
Cluster B: 1 NDB Server
Explanation:
NDB Multi-Cluster is a feature that allows multiple Nutanix clusters to share a common NDB service for
database management and automation. NDB service consists of two components: NDB Server and NDB
Agent. NDB Server is the central component that provides the web UI, REST API, and database orchestration
logic. NDB Agent is the component that runs on each Nutanix cluster and communicates with the NDB
Server to perform database operations.
When NDB Multi-Cluster is enabled on Cluster A, it becomes the primary cluster that hosts the NDB Server
VM. Cluster B, which is registered with NDB, becomes a secondary cluster that hosts only the NDB Agent
VM. Therefore, Cluster A has both NDB Server and NDB Agent, while Cluster B has only NDB Agent. This
configuration allows Cluster B to leverage the NDB service running on Cluster A for database management
and automation.
How long is the default continuous recovery for the Gold SLA in Era Time Machine?
A. 30 days
B. 15 days
C. 60 days
D. 90 days
Explanation: The default continuous recovery for the Gold SLA in Era Time Machine is 30 days1. This means that the system keeps a continuous recovery point for the last 30 days, allowing you to restore your database to any point within this period1.
An administrator wants to enable Multi-Cluster management on an Era installation. Which prerequisites must be satisfied to complete this task?
A. AOS version supported, static VLAN setup in Era Networks
B. Database Server VMS version supported. Network Profiles setup
C. Hardware version supported, DHCP Network enabled on Nutanix cluster
D. Hypervisor version supported, port 9440 open between Era VM and clusters
Explanation: For enabling Multi-Cluster management on an Era installation, the hypervisor version must be supported and port 9440 must be open between the Era VM and clusters. This ensures that the Era VM can communicate with the clusters for management tasks1.
An administrator needs to migrate a large 1/0-intensive database that doesn't support multi-disk layout. How should the storage be provisioned with Era to support the database while optimizing performance?
A. Volume Group
B. Volume Group with Load Balancing
C. Storage Spaces
D. vDisk based provisioning
Explanation:
In Nutanix Era, a Volume Group is the recommended storage provisioning method for a large I/O-intensive
database that doesn’t support a multi-disk layout1. A Volume Group in Nutanix Era is a collection of disks
that can be managed as a single entity, providing a way to aggregate the storage capacity of multiple disks
into a larger storage unit1. This allows for better performance optimization as it enables the database to
leverage the combined I/O capabilities of all the disks in the group1. It’s important to note that while other
options like Load Balancing, Storage Spaces, and vDisk based provisioning can also be used in certain
scenarios, a Volume Group is specifically designed for situations where a single, high-performance storage
unit is required1.
An Era-managed production MSSQL database crashed during a busy holiday weekend and the administrator has to restore the database to the most recent timestamp with an objective to reduce the restore time and minimize data loss. What option should the administrator do to achieve this objective?
A. Perform Restore Source Database by selecting Restore time just before the database crash.
B. Perform Restore Source Database by selecting most recent and include Tail log Backup
C. Perform Restore Source Database by selecting the available snapshot.
D. Perform Restore Source Database by selecting the current time.
Explanation:
Nutanix Era is a database management solution that automates and simplifies database administration tasks
such as provisioning, patching, cloning, and backup. In the event of a database crash, the most effective way
to minimize data loss and reduce restore time is to perform a restore of the source database by selecting the
most recent point in time and including the Tail log Backup12.
The Tail log Backup includes all the transactions that have occurred since the last transaction log backup,
which helps to minimize data loss. By selecting the most recent point in time for the restore, the administrator
ensures that the database is restored to the state it was in just before the crash, thereby reducing the amount of
data that needs to be reprocessed or reentered12. This approach aligns with the Nutanix Era’s capabilities and
best practices for database recovery12.
Page 1 out of 30 Pages |