The customer's requirements for automatic failover and resource balancing in a new Hyper-V cluster can be met with the use of Failover Clustering and High Availability. Failover Clustering allows VMs to automatically failover to another host in the event of a host failure, fulfilling the requirement for resilience.
High Availability ensures that VMs restart on available hardware in the cluster, maintaining service continuity and balancing CPU and memory resources across the hosts.References: Microsoft Hyper-V documentation, Nutanix Bible, and NCS-Core 6.8 course materials on virtualization platforms.

If the administrator observes that the snapshot intervals have changed from the initially configured 5-minute intervals to 15-minute intervals, it indicates a potential issue with the setup. Option C, "Fix a connectivity issue because the protection domain reverted to Async," addresses the likely cause-a connectivity problem that caused the system to revert to longer, asynchronous DR snapshot intervals.
NearSync typically allows for very frequent snapshots, but if there is a connectivity or configuration issue, it might fall back to less frequent asynchronous DR settings. Identifying and resolving any connectivity issues would allow the NearSync configuration to operate as initially intended.
References:The mechanics of NearSync and its behavior under connectivity issues are discussed in detail in Nutanix's documentation and troubleshooting guides, which describe how the system handles fallback scenarios and how to rectify them.

To ensure the new application is securely deployed without affecting existing applications, the administrator should create new categories for the VMs hosting the new application. This approach allows for targeted application of security policies without impacting other applications. After creating these new categories, the administrator should then create new security policies that incorporate these categories and specify the unique, non-standard ports used by the application, ensuring that security is tailored specifically to the new application's needs.References: Nutanix Prism Central Guide, Nutanix Security Configuration Best Practices.

In a Nutanix environment, if the Foundation VM is not discovering the hardware, it could be due to issues with the IPMI (Intelligent Platform Management Interface) settings. IPMI is a set of computer interface specifications for an autonomous computer subsystem that provides management and monitoring capabilities independently of the host system's CPU, firmware (BIOS or UEFI), and operating system.
In this scenario, the consultant should connect a crash cart to each node, log in to the pre-installed AHV hypervisor, and run the IPMITool commands to set the IPMI IP Address, subnet, and gateway for each node.
After setting the IPMI settings, the consultant should run Foundation using the configured IPMI addresses that were just set.
This will ensure that the Foundation VM can communicate with the nodes via IPMI and discover the hardware, allowing the installation to proceed.
References:
* [Nutanix Support & Insights]
* [Nutanix Community]
* [Nutanix Documentation]
* [Nutanix Certified services - core (NCS-Core) 6.8 - Nutanix University]
* [Nutanix Bible]
* [Nutanix Certified services - core (NCS-Core) 6.8 Playlist - YouTube]

Ref: https://portal.nutanix.com/page/documents/details?targetId=Files-v3_6:fil-files-high-availability-c.html