The administrator can achieve this request by deleting and recreating a new Objects store with the updated name. Objects is a feature that allows users to create and manage object storage clusters on a Nutanix cluster.
Objects clusters can provide S3-compatible access to buckets and objects for various applications and users.
Objects clusters can be created and configured in Prism Central. However, once an Objects cluster is created, its name cannot be changed or edited. Therefore, the only way to change the name of an Objects cluster is to delete the existing cluster and create a new cluster with the updated name. References: Nutanix Objects User Guide, page 9; Nutanix Objects Solution Guide, page 8

The most likely cause of this issue is that the file server has been cloned. Cloning a file server is not a supported operation and can cause various problems, such as Data Lens not being able to enable or disable for the cloned file server. To avoid this issue, the administrator should use the scale-out feature to add more FSVMs to an existing file server, or create a new file server from scratch. Reference: Nutanix Files Administration Guide, page 28; Nutanix Files Troubleshooting Guide, page 11

Nutanix Files, part of Nutanix Unified Storage (NUS), uses File Server Virtual Machines (FSVMs) to manage file services. A four-node FSVM deployment means four FSVMs are deployed, typically one per node in a four-node cluster. Nutanix Files requires two networks for FSVMs:
* Client Network: Used for client-facing communication (e.g., SMB, NFS access).
* Storage Network: Used for internal communication with the Nutanix cluster's storage pool.
Each FSVM requires one IP address on each network, as established in Question 1.
Analysis of Options:
* Option A (Four available IP addresses on the Client network): Correct. In a four-node FSVM deployment, each FSVM requires one IP address on the Client network for client communication (e.g., SMB, NFS). With four FSVMs, this means four IP addresses are needed on the Client network, one for each FSVM.
* Option B (Four available IP addresses on the Storage network): Correct. Each FSVM also requires one IP address on the Storage network for internal communication with the Nutanix cluster's storage pool. For four FSVMs, this means four IP addresses are needed on the Storage network, one for each FSVM.
* Option C (Five available IP addresses on the Storage network): Incorrect. Only four IP addresses are needed on the Storage network for a four-node FSVM deployment-one per FSVM. A fifth IP address is not required, as there is no additional entity (e.g., a virtual IP) needed for the Storage network in this context.
* Option D (Five available IP addresses on the Client network): Incorrect. Similarly, only four IP addresses are needed on the Client network for the four FSVMs. A fifth IP address might be needed in other scenarios (e.g., a virtual IP for load balancing in some configurations), but for a standard four- node FSVM deployment, four IPs suffice, as established in Question 1.
Selected Requirements:
* A: Four IP addresses on the Client network are required, one for each of the four FSVMs.
* B: Four IP addresses on the Storage network are required, one for each of the four FSVMs.
Why These Requirements?
Each FSVM in a Nutanix Files deployment requires one IP address on the Client network for client access and one on the Storage network for internal storage communication. For a four-node FSVM deployment, this translates to exactly four IP addresses on each network, matching the number of FSVMs.
Exact Extract from Nutanix Documentation:
From the Nutanix Files Deployment Guide (available on the Nutanix Portal):
"A Nutanix Files deployment with four FSVMs requires four available IP addresses on the Client network for client communication (SMB/NFS) and four available IP addresses on the Storage network for internal communication with the Nutanix cluster's storage pool."
:
Nutanix Files Deployment Guide, Version 4.0, Section: "Network Requirements for Files Deployment" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Files Network Configuration".

Nutanix Objects supports versioning, which is a feature that allows multiple versions of an object to be preserved in the same bucket. Versioning can be useful for developers who need to upload their code for testing API calls and retain older iterations as newer code is developed and tested. Versioning can also provide protection against accidental deletion or overwrite of objects. References: Nutanix Objects Administration Guide The development team needs a solution to upload code via API calls while retaining older versions of the code as newer versions are developed. This use case aligns with versioned object storage, which supports API- based uploads (e.g., S3 APIs) and automatic versioning.
Analysis of Options:
* Option A (Create a bucket in Objects with Versioning enabled): Correct. Nutanix Objects, part of Nutanix Unified Storage (NUS), provides S3-compatible object storage. It supports versioning, which allows multiple versions of an object to be retained when new versions are uploaded. The S3 API is ideal for programmatic uploads via API calls, meeting the developers' requirement to upload code for testing while retaining older iterations.
* Option B (Create an SMB Share with Files and enable Previous Versions): Incorrect. Nutanix Files supports SMB shares with the Previous Versions feature (via Self-Service Restore), which allows users to access earlier versions of files. However, SMB is not typically accessed via API calls-it's designed for file sharing over a network (e.g., Windows clients). This does not align with the requirement for API-based uploads.
* Option C (Provision a Volume Group and connect via iSCSI with MPIO): Incorrect. Nutanix Volumes provides block storage via iSCSI, which is suitable for applications requiring low-level storage access (e.g., databases). However, iSCSI does not support API-based uploads or versioning, making it unsuitable for the developers' needs.
* Option D (Create an NFS Share mounted on a Linux Server with Files): Incorrect. An NFS share in Nutanix Files allows file access over the NFS protocol, which can be mounted on a Linux server. While NFS supports file storage, it does not natively provide versioning, and NFS is not typically accessed via API calls for programmatic uploads.
Why Option A is the Best Solution:
* Nutanix Objects with Versioning: Objects supports S3 APIs, which are widely used for programmatic uploads in development workflows. Enabling versioning ensures that older versions of the code are retained automatically when new versions are uploaded, meeting the requirement to retain older iterations.
* API Support: The S3 API is a standard for API-based uploads, making it ideal for the developers' workflow.
* Scalability: Objects is designed for scalable object storage, suitable for development and testing environments.
Exact Extract from Nutanix Documentation:
From the Nutanix Objects Administration Guide (available on the Nutanix Portal):
"Nutanix Objects supports versioning for buckets, allowing multiple versions of an object to be retained.
When versioning is enabled, uploading a new version of an object preserves the previous versions, which can be accessed or restored via S3 API calls. This feature is ideal for development workflows where older iterations of files need to be retained."
:
Nutanix Objects Administration Guide, Version 4.0, Section: "Bucket Versioning" (Nutanix Portal).
Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Section: "Nutanix Objects Features".

The administrator should resolve this issue by using the Files MMC Snap-in and renaming the folders. The Files MMC Snap-in is a tool that allows administrators to manage Files shares and exports from a Windows machine. The administrator can use the Files MMC Snap-in to connect to a distributed share or export and rename the top-level directories that are hosted by different FSVMs. Renaming the directories from Windows Explorer will not work because Windows Explorer does not recognize the distributed nature of the share or export and will try to rename all directories on the same FSVM, which will fail. Reference: Nutanix Files Administration Guide, page 35; Nutanix Files MMC Snap-in User Guide