Explanation:
The correct task order for creating an object store is:
* Select ObjectStore Service and click Enable
* Click Create Object Store to start creating the first Object store
* Click Download Creation Checklist to download the list of prerequisites for deploying an Object store The first step is to enable the ObjectStore Service, which is a service that allows users to create and manage object storage clusters on a Nutanix cluster. The second step is to create an Object store, which is an object storage cluster that provides S3-compatible access to buckets and objects for various applications and users.
The third step is to download the Creation Checklist, which is a document that lists the prerequisites and configurations that are required for deploying an Object store, such as cluster details, network details, storage details, etc. The administrator should review and complete the Creation Checklist before proceeding with the deployment of the Object store.

Nutanix Volumes is a feature that allows users to create and manage block storage devices (volume groups) on a Nutanix cluster. Volume groups can be accessed by external hosts using the iSCSI protocol. To secure volume groups from unauthorized access, Nutanix recommends configuring CHAP (Challenge-Handshake Authentication Protocol) for each volume group in Prism Element. CHAP is a security feature that authenticates iSCSI initiators and targets before allowing access to a volume group. CHAP requires both the initiator and the target to have a shared secret (a password) that is used to generate a challenge and a response during the authentication process. CHAP can prevent unauthorized access to volume groups and protect data from malicious attacks. References: Nutanix Volumes Administration Guide, page 25; Nutanix Volumes Security Guide Nutanix's best practices for Volumes security emphasize securing iSCSI connections through authentication.
Configuring Volume Groups to use CHAP ensures that only authorized initiators can access the storage, preventing unauthorized access and aligning with security compliance requirements. This is a direct and mandatory step for securing Volumes, making it the best choice among the options.
Exact Extract from Nutanix Documentation:
From the Nutanix Volumes Administration Guide (available on the Nutanix Portal):
"To align with Nutanix best practices for security, configure Volume Groups to use CHAP (Challenge- Handshake Authentication Protocol) for iSCSI authentication. This ensures that only authorized initiators can access the Volume Group, protecting against unauthorized access and enhancing security."
:
Nutanix Volumes Administration Guide, Version 6.0, Section: "Security Best Practices for Nutanix Volumes" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Volumes Security Configuration".

Anti-affinity rules ensure FSVMs are distributed across hosts for HA, but during a one-click hypervisor upgrade, these rules can prevent FSVMs from being migrated to other hosts when a host enters maintenance mode. Disabling the anti-affinity rules temporarily allows the upgrade to proceed by permitting FSVMs to reside on the same host during the migration process, ensuring a smooth and non-disruptive upgrade.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Administration Guide (available on the Nutanix Portal):
"When performing a one-click hypervisor upgrade on ESXi hosts hosting Nutanix Files, temporarily disable the anti-affinity rules for FSVMs. This allows FSVMs to be migrated to other hosts during the upgrade process without violating placement constraints, ensuring a non-disruptive upgrade. Re-enable the anti- affinity rules after the upgrade is complete."
:
Nutanix Files Administration Guide, Version 4.0, Section: "Upgrading Hypervisors in a Files Environment" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files Upgrade Considerations".

The two network requirements for a four-node FSVM deployment are five available IP addresses on the Client network and five available IP addresses on the Storage network. The Client network is used for communication between the FSVMs and the clients, while the Storage network is used for communication between the FSVMs and the CVMs. For each FSVM, one Client IP and one Storage IP are required. Additionally, one extra Client IP is required for the file server VIP (Virtual IP), which is used as a single point of access for all shares and exports on the file server. Reference: Nutanix Files Administration Guide, page 28; Nutanix Files Solution Guide, page 7

Nutanix File Analytics is a feature that provides insights into the usage and activity of file data stored on Nutanix Files. File Analytics consists of a File Analytics VM (FAVM) that runs on a Nutanix cluster and communicates with the File Server VMs (FSVMs) that host the file shares. The FAVM collects metadata and statistics from the FSVMs and displays them in a graphical user interface (GUI). The FAVM must be deployed on the same network as the FSVMs, which is the Client-side network. This network is used for communication between File Analytics and FSVMs, as well as for accessing the File Analytics UI from a web browser. The Client-side network must have DHCP enabled and must be routable from the external hosts that access the file shares and File Analytics UI. References: Nutanix Files Administration Guide, page 93; Nutanix File Analytics Deployment Guide