A single AOS cluster supports a maximum of 4 Nutanix Object Stores. Each object store is an independent instance with dedicated resources.
Reference:Nutanix Objects Planning Guide:
"A cluster supports up to four Object Stores, each capable of hosting multiple buckets and scaling independently."(Chapter: "Deployment Limits")Nutanix NUSA Course:"The hard limit of 4 Object Stores per cluster ensures resource isolation and performance stability."(Module: "Objects Sizing and Scaling") According to the Nutanix Unified Storage documentation and the Nutanix Unified Storage Administration (NUSA) course materials, each AOS (Acropolis Operating System) cluster can support a maximum of4 object stores. This maximum number ensures stability, scalability, and performance consistency within the cluster environment.
The object store in Nutanix Unified Storage is implemented using Nutanix Objects, which leverages a distributed, scale-out architecture. When deploying object stores within an AOS cluster, the system assigns storage resources and metadata handling roles across the cluster nodes to maintain high availability and data protection.
The limitation of4 object stores per clusteris defined to optimize resource utilization and prevent excessive load on cluster services that manage object metadata and data replication. Each object store is backed by Nutanix's robust storage fabric, which ensures performance and reliability while maintaining strict isolation between different object stores.
In the Nutanix Unified Storage Administration course, the topic of deploying object stores covers:
Deployment Limits:Each AOS cluster is capable of hosting up to 4 object stores, which allows for flexibility while maintaining performance boundaries.
Design Considerations:The 4-object store limit is recommended to avoid resource contention, as object stores have significant metadata and data handling overhead that can impact cluster stability if limits are exceeded.
Scalability:While 4 object stores can be deployed per cluster, Nutanix's architecture allows for horizontal scaling by deploying additional object stores across multiple clusters as needed for different use cases or tenant isolation.
Management of Object Stores:Unified Storage leverages Prism Central and Prism Element to configure and monitor object stores, ensuring easy management of deployed object services within the cluster's limit.
This information is consistently emphasized in the official NCP-US study guide and the NUSA course presentations to ensure administrators and architects understand these design and deployment limitations.

Storage Containers are mandatory for Nutanix Files because:
* They provide the underlying storage pool for file shares.
* Define replication factor, compression, and encryption settings.
Other options are incorrect:
* A: vCPUs are per-File-Server-VM specs (#4 vCPUs required).
* B: Prism Central is needed for management but not core deployment.
* D: iSCSI IPs relate to Nutanix Volumes, not Files.
Reference:Nutanix Files Deployment Guide:
"Before deploying Files, create a Storage Container to host share data. This container must have RF#2 and erasure coding disabled."(Chapter: "Prerequisites") Nutanix Unified Storage Administration (NUSA) Course:
"Storage Containers are foundational prerequisites; all file data resides in these logical pools."(Module: "Files Installation Fundamentals")

The workload type that describes I/O sizes for read and write operations that areless than or equal to 16 KB while file sizes are10 MB or moreisRandom. In Nutanix Files, workload types are used to optimize share performance based on I/O patterns. Small I/O sizes (#16 KB) indicate a random access pattern, as opposed to sequential, even if the files themselves are large (#10 MB). This is common in workloads like databases or virtual desktops, where small, non-contiguous I/O operations are performed on larger files.
TheNutanix Unified Storage Administration (NUSA)course states, "A Random workload type in Nutanix Files is characterized by small I/O sizes, typically 16 KB or less, regardless of file size, as it reflects random access patterns rather than sequential ones." The Random workload type optimizes the share for such patterns by adjusting caching, prefetching, and data placement to handle frequent small I/O operations efficiently, even when the files are large.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further elaborates that
"workloads with I/O sizes of 16 KB or less, even on large files (e.g., 10 MB or more), are classified as Random, as the small I/O size indicates non-sequential access patterns." Large file sizes do not necessarily imply sequential I/O; the I/O size itself determines the workload type, and 16 KB or less is typical of random access.
The other options are incorrect:
* Sequential: Sequential workloads involve larger I/O sizes (typically >64 KB) and contiguous access patterns, such as those seen in media streaming or backups, not small I/O sizes like 16 KB or less.
* Asynchronous: Asynchronous is not a workload type in Nutanix Files; it may refer to replication or I/O handling methods but is not relevant here.
* Default: The Default workload type applies a balanced configuration but does not specifically optimize for small I/O sizes like the Random type does.
The NUSA course documentation emphasizes that "I/O sizes of 16 KB or less, even with large file sizes, indicate a Random workload type in Nutanix Files, ensuring optimal performance for random access patterns." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Understanding workload types based on I/O patterns." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Defining workload types for Nutanix Files shares." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Workload type definitions for share optimization."

Changing thename of a Nutanix Files clusterinvolves updating theDNS name resolutionfor its FSVMs and VIPs. When the cluster's name changes:
The underlying IP addresses (CVMs, FSVMs, VIPs)do not change.
However,DNS entriesassociated with the old cluster namebecome outdated, causing clients (including management interfaces and file share connections) to fail to resolve the new name to the correct IP addresses.
From the NUSA course troubleshooting section:
"After renaming a Files cluster, update the DNS entries to reflect the new name. Otherwise, clients and administrators will be unable to reach the cluster resources." Restarting CVMs or FSVMs does not update DNS entries.
Deleting active user sessions won't fix the DNS resolution problem.
Therefore, to resolve theunreachabilityissue, the administrator must:
#Delete old DNS entriesfor the previous cluster name.
#Add new DNS entriesmapping the new cluster name to the same IPs of the FSVMs and VIP.
This ensures that all systems can properly resolve the new cluster name and reach the Nutanix Files services.

Access Based-Enumeration (ABE)is a feature in Nutanix Files that controls whether users cansee folders and filesfor which they do not have access permissions. When ABE is enabled:
* Users will only see the folders/files they are authorized to access.
* Items for which they have no permissions will be hidden from view.
The NUSA course describes this feature:
"Access Based-Enumeration (ABE) ensures that users browsing a share will only see folders and files that they have permission to access, improving security and minimizing confusion." Thus,ABEis the precise feature for controllinguser visibilityof SMB shares based on permissions.