The correct answer is D. Fewer than 30 I/Os and less than 1000 bytes per day of network traffic for the past 21 days.

A zombie VM is a type of inactive VM that is powered on but does very little activity. A zombie VM wastes host resources such as CPU, memory, disk, and network that could be used by other VMs. A zombie VM can be identified by using the VM Profile feature in Prism Central. The VM Profile feature analyzes the resource utilization of each VM and assigns it a profile based on its efficiency and impact on other VMs. The profiles are as follows1:

Efficient: The VM is well-provisioned and has optimal resource utilization.

Over-provisioned: The VM has more resources than it needs and has low resource utilization.

Constrained: The VM has less resources than it needs and has high resource utilization.

Inactive: The VM has no resource utilization and is idle or powered off.

Bully: The VM has high resource utilization and causes contention for other VMs.

A zombie VM is a subtype of an inactive VM that meets the following criteria2:

The VM is powered on for the past 21 days.

The VM does fewer than 30 read or write I/Os (total) per day for the past 21 days.

The VM receives or transfers fewer than 1000 bytes per day of network traffic for the past 21 days.

To identify a zombie VM, the administrator can use Prism Central to view the VM Profile dashboard and filter by profile type. The dashboard shows the number of VMs in each profile type, as well as their resource consumption and efficiency score. The administrator can also drill down into each VM to see its detailed metrics and recommendations for optimization.

A bully VM is a VM that consumes too many resources and causes other VMs to starve. A bully VM can affect the performance and availability of other VMs on the same host or cluster by hogging CPU, memory, disk, or network resources.A bully VM can be identified by using the VM Profile feature in Prism Central2. The VM Profile feature analyzes the resource utilization of each VM and assigns it a profile based on its efficiency and impact on other VMs.The profiles are as follows3:

Efficient: The VM is well-provisioned and has optimal resource utilization.

Over-provisioned: The VM has more resources than it needs and has low resource utilization.

Constrained: The VM has less resources than it needs and has high resource utilization.

Inactive: The VM has no resource utilization and is idle or powered off.

Bully: The VM has high resource utilization and causes contention for other VMs.

To identify a bully VM, the administrator can use Prism Central to view the VM Profile dashboard and filter by profile type. The dashboard shows the number of VMs in each profile type, as well as their resource consumption and efficiency score. The administrator can also drill down into each VM to see its detailed metrics and recommendations for optimization.

Nutanix supports two types of deduplication: post-process and inline. Post-process deduplication runs periodically on a schedule and can be enabled on any cluster. Inline deduplication runs in real time before data is written to disk and can be enabled only on all-flash clusters.

Therefore, by checking the type of storage and the type of deduplication, you can determine if you can enable inline deduplication on a storage container or not.

Nutanix inline deduplicationis a feature that reduces the stored size and avoids duplicate data on a storage container1.It is recommended only on some specific scenarios, such as when using Nutanix Files or virtual desktop infrastructure (VDI) workloads12.

According to the Nutanix Prism Central Guide, role-based access control (RBAC) in Prism Central allows you to create custom roles and assign them to users or groups based on the categories of the entities they need to manage1. Categories are key-value pairs that you can assign to entities such as VMs, hosts, clusters, images, etc.to group them logically2. For example, you can create a category key called ''OS'' and assign values such as ''Linux'' or ''Windows'' to different VMs based on their operating system.

In the exhibit, the Linux Admin role has been created with the following settings:

The role has the ''VM Admin'' permission, which allows the user to perform all actions on VMs3.

The role has been assigned to the admin1 user.

The role has been scoped to the entities that have the category key ''OS'' and the value ''Linux''.

However, the admin1 user does not have access to all Linux VMs in the environment. This means that some of the Linux VMs do not have the proper category assigned to them. To grant the proper access, the administrator should add the category key ''OS'' and the value ''Linux'' to each Linux VM that needs to be managed by the Linux Admin role.This can be done either individually or in bulk through Prism Central4. Once the categories are added, the admin1 user will be able to see and manage all Linux VMs in the environment.

According to the image description, the exhibit shows a screenshot of a computer screen with a table of data. The table has 6 columns and 4 rows. The columns are labeled ''Date'', ''Time'', ''Status'', ''Details'', ''Configuration'', and ''Duration''. The rows contain information about different configurations and their statuses. The background is a light blue color. There is a pop-up message on the bottom right corner of the screen that reads ''This question has been answered. Click here to enable the edit button.''

Based on the table data, it seems that the screenshot is taken from the Prism Central web console, showing the results of a cluster health check report.The report shows that there are four failed checks: Host Password Policy, CVM Password Policy, NTP Configuration, and Cluster Time Skew2. These checks indicate that some initial cluster configuration tasks were missed during the deployment process.

The Host Password Policy check verifies that the host passwords are not set to default values and are compliant with the password policy defined in Prism Central3.The CVM Password Policy check verifies that the CVM passwords are not set to default values and are compliant with the password policy defined in Prism Central4. These checks are important for ensuring the security and compliance of the cluster. Therefore, changing the host and CVM passwords from their default values and following the password policy guidelines are two initial cluster configuration tasks that were missed.