A.   On the Era Dashboard Database Summary Table under Source Database.

C.   On the Databases > Sources table.

Option A: On the Era Dashboard Database Summary Table under Source Database. The dashboard provides a summary of the databases, including their sizes1.
Option B: Under the Capacity widget on the Database Server VMS > List database summary page. While this might provide information about the capacity, it does not specifically provide the size of a Source Database.
Option C: On the Databases > Sources table. This table provides detailed information about the databases, including their sizes1.
Option D: On the Profiles > Database Parameters list for the assigned DB Parameter Profile. This list provides parameters for the database but does not provide the size of a Source Database.

B.   Update the Network Profile to include the new VLANs.

Explanation:
A Network Profile is a collection of network settings that are used to provision database server VMs in NDB. A Network Profile can include one or more VLANs, IP ranges, and DNS servers. To make new VLANs available when provisioning an Oracle cluster database, you need to update the Network Profile to include the new VLANs. You can do this by editing the existing Network Profile or creating a new one with the new VLANs. You do not need to create or update the VLANs in Prism Element, as NDB can discover the VLANs configured in AHV1.

C.   Select the built-in NONE SLA that is configured for no snapshot or log backup.

Explanation:
Nutanix Database Automation (NCP-DB) allows administrators to manage Service Level Agreements (SLAs) for databases. These SLAs define the data protection policies for databases. In this case, to minimize storage usage for a test database, the administrator should select the built-in NONE SLA. This SLA is configured for no snapshot or log backup, thus minimizing storage usage1.

C.   The VLAN is stretched

Explanation:
The correct answer is C because a stretched VLAN is a VLAN that spans across multiple Nutanix clusters, which may cause network conflicts or latency issues when starting the database server. Option A is incorrect because a DHCP VLAN is a VLAN that uses dynamic IP address allocation, which does not affect the database server startup. Option B is incorrect because a static VLAN is a VLAN that uses fixed IP address allocation, which also does not affect the database server startup. Option D is incorrect because IPAM is not a type of VLAN, but a feature of NDB that allows managing IP addresses for database servers and databases.

C.   Base-64 encoded X 509

Explanation:
According to the Nutanix Database Automation (NCP-DB) learning documents, Nutanix Era supports x509 certificates in Base-64 encoded PEM format1. This format is used when an administrator needs to replace the default Nutanix self-signed certificates in Era1.

B.   Japanese

Explanation:
The NDB user interface supports multiple languages, including English, Chinese, and Japanese. You can change the language preference in the NDB settings page. The NDB user interface does not support Korean, French, or German languages at this time.

A.   Tags

Explanation:
Nutanix Era allows custom metadata to be assigned to entities (clones, time machines, databases, and database servers) by using Tags. Tags are a component of Nutanix Era that allows users to assign custom metadata to various entities, enhancing the ability to organize, search, and manage these entities within the Era platform1.

D.   Cluster VIP end I Listener IP on the local site
1 Cluster VIP and 1 Listener IP on the remote site
2 IPs in the local site and 1 on the remote site for the database server nodes

Explanation:
The correct answer is D. When setting up a 3-node MSSQL Server AG with two database server VMs on a local site and a third database server VM on a remote site, the network at each site will require the following IP addresses:

• 1 Cluster VIP and 1 Listener IP on the local site123.
• 1 Cluster VIP and 1 Listener IP on the remote site123.
• 2 IPs in the local site and 1 on the remote site for the database server nodes123.

This configuration ensures that each node in the cluster has a unique IP address, and each cluster and listener also has a unique IP address. This is necessary for the proper functioning of the cluster and to ensure that all nodes can communicate with each other and with clients123.

A.   vCPUs, cores per vCPU, and the amount of memory for the database server VM.

Explanation:
An NDB compute profile defines the CPU and memory resources for the database server VMs that are provisioned using NDB. It does not include any information about the network, domain, or software of the database server VMs. Those are specified in separate profiles, such as network profile, domain profile, and software profile.

C.   5

Explanation:
The log frequency in the Era IJI for log catchup operation can be configured to as low as 5 minutes. This allows the system to capture changes to the database at a high frequency, enabling more precise point-in-time recovery options. However, it’s important to note that a higher frequency of log catchup operations can lead to increased system load. Therefore, the optimal frequency may vary depending on the specific requirements and capabilities of your system12. Please refer to the Nutanix Database Automation (NCP-DB) Learning documents for more detailed information.

B.   The size of all snapshots and/or transaction logs maintained by Era

Explanation:
The Nutanix Era platform provides a feature called Time Machine, which is designed to manage the lifecycle of database copies and clones1. When a new table is added to the source database, the administrator should perform a Log Catch-up using the source database’s Time Machine. This action ensures that the Time Machine captures the latest state of the source database, including the newly added table1. After performing the Log Catch-up, the administrator should refresh the clone database. The refresh operation updates the clone with the latest state captured by the Time Machine, thereby publishing the new table to the clone1.

C.   Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: To complete the request the database must be re-registered in NDB, this thaws the Time Machine and it resumes operation so the clone can be refreshed.

Explanation:
A Time Machine is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention. When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de-registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze.