To verify that all in-scope tasks for a new cluster deployment have been completed, the consultant should refer to the:
* Deployment Checklist: This document typically lists all tasks required for a successful deployment, making it a suitable tool for ensuring that nothing has been overlooked.
References:
* Nutanix Bible (https://www.nutanixbible.com), where the importance of deployment documentation is discussed.
* Nutanix Deployment Guide, which includes detailed checklists for ensuring thorough project completion.

https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_10:wc-protection-do

The command ncli pd deactivate_and__destroy_vms name=<protection_domain_name> is a critical operation in managing Nutanix environments, particularly in scenarios involving disaster recovery and replication.
* This command deactivates the protection domain and deletes all VMs associated with that protection domain from the source site (Site A in this case). This operation is generally part of a planned migration or failover process where the VMs are intended to be run from the remote site (Site B).
* After this operation, the protection domain at Site A is no longer active, meaning it has been effectively removed along with its associated VMs, thus clearing the way for Site B to take over operations without conflict from the original site.
References:This action and its implications are covered under Nutanix disaster recovery and high availability strategies, detailed in both the Nutanix Bible and official Nutanix NCS-Core training materials, which discuss the management of protection domains and replication processes.

The customer is experiencing VM performance issues characterized by excessive read/write I/Os on CVMs and excessive motion of VMs due to the Distributed Resource Scheduler (DRS) in an ESXi-based Nutanix cluster. This is likely caused by the DRS migration threshold being set to Aggressive, which leads to frequent rebalancing of workloads across the cluster, causing high I/O and VM motion. Adjusting this setting to a less aggressive level can help reduce unnecessary VM motions and stabilize performance.References: Nutanix Bible, Nutanix University NCS-Core 6.8 learning materials

The issue where users can mount all three storage containers despite the intention to restrict access to just container-1 typically stems from a Global whitelist entry. A global whitelist allows all entities to access all containers unless more specific restrictions are applied at the container level. To correct this, specific whitelist entries need to be configured for each container to define and restrict access appropriately.References: Nutanix NCS-Core 6.8 training resources, the Nutanix Bible, and Nutanix technical documentation on storage container management.

Ref: https://hyperhci.com/2019/11/09/nutanix-ahv-enable-vlan-trunk-mode-on-guest-vm/