After enabling Nutanix Objects in a Nutanix cluster, the next action before starting the deployment is to create an Object Store . Enabling Nutanix Objects activates the object storage service on the cluster, but the actual deployment involves creating an object store instance, which defines the storage resources, network settings, and other configurations needed for object storage operations.

The Nutanix Unified Storage Administration (NUSA) course states, “After enabling Nutanix Objects, the administrator must create an Object Store to deploy the object storage service, specifying parameters such as storage capacity, network settings, and domain name.” The object store is the primary entity in Nutanix Objects, and creating it sets up the infrastructure for buckets, S3-compatible APIs, and other object storage features. Only after the object store is created can buckets be added and used for storing objects.

The Nutanix Certified Professional - Unified Storage (NCP-US) study guide further elaborates that “the deployment of Nutanix Objects begins with creating an Object Store, which initializes the service and prepares it for bucket creation and data storage.” This step is necessary to operationalize Nutanix Objects after enabling the feature in the cluster.

The other options are incorrect:

Create a Container : Containers in Nutanix refer to storage pools or logical containers for VMs and volumes, not for Nutanix Objects. In the context of Objects, the equivalent is a bucket, which is created after the object store.

Perform an LCM inventory : An LCM inventory is relevant for upgrades, not for the initial deployment of Nutanix Objects after enabling the feature.

Create a Volume Group : Volume groups are used for Nutanix Volumes (block storage), not Nutanix Objects (object storage).

The NUSA course documentation emphasizes that “creating an Object Store is the first step after enabling Nutanix Objects, ensuring the service is deployed and ready for use.”

Changing the name of a Nutanix Files cluster involves updating the DNS name resolution for its FSVMs and VIPs. When the cluster’s name changes:

The underlying IP addresses (CVMs, FSVMs, VIPs) do not change .

However, DNS entries associated with the old cluster name become 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 the unreachability issue, the administrator must:

???? Delete old DNS entries for the previous cluster name.

???? Add new DNS entries mapping 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.

The administrator is attempting to scale out a Nutanix Files deployment by adding more File Server Virtual Machines (FSVMs) to a multi-node FSVM deployment on a three-node AHV cluster, but the operation has failed. The first step the administrator should take is to expand the AHV cluster . Nutanix Files requires a minimum number of nodes in the cluster to support a scale-out operation, and a three-node cluster may not have sufficient resources (nodes) to accommodate additional FSVMs.

The Nutanix Unified Storage Administration (NUSA) course states, “Nutanix Files scale-out operations require sufficient cluster nodes to host additional FSVMs, and a minimum of four nodes is recommended for scaling out a multi-node FSVM deployment.” In a three-node cluster, each node typically hosts one FSVM (for a total of three FSVMs), and scaling out to add more FSVMs requires additional nodes to distribute the new FSVMs. If the cluster does not have enough nodes, the scale-out operation will fail, as there are no available nodes to host the new FSVMs.

The Nutanix Certified Professional - Unified Storage (NCP-US) study guide further elaborates that “when a Nutanix Files scale-out operation fails on a small cluster, the first step is to verify the cluster size and expand the AHV cluster by adding more nodes to support the additional FSVMs.” Expanding the cluster to at least four nodes provides the necessary capacity to host a new FSVM, allowing the scale-out operation to succeed.

The other options are incorrect:

Add RAM to the physical hosts : While insufficient RAM could cause issues, the failure of a scale-out operation is more likely due to a lack of nodes rather than RAM, especially since FSVMs have specific node placement requirements.

Failover to secondary site : Failover to a secondary site is relevant for disaster recovery (e.g., using Smart DR), not for resolving a scale-out failure within the primary cluster.

Add DNS entries : DNS entries may be needed for client access to Nutanix Files, but they are not directly related to the scale-out operation of FSVMs within the cluster.

The NUSA course documentation emphasizes that “a common cause of Nutanix Files scale-out failures in small clusters is insufficient nodes; expanding the AHV cluster to at least four nodes is the first step to ensure successful scaling.”

The workload type that describes I/O sizes for read and write operations that are less than or equal to 16 KB while file sizes are 10 MB or more is Random . 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.

The Nutanix 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.

The Nutanix 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.”

The scenario involves upgrading an S3-compatible bucket (Nutanix Objects) using Prism Central’s Lifecycle Manager (LCM). The LCM upgrade process failed because outbound traffic to the Internet was restricted, and the administrator needs to identify which components require Internet access for a successful upgrade. The correct answer is that the CVM IP address/port must be provided to the security team, as the Controller Virtual Machines (CVMs) are responsible for downloading upgrade artifacts from Nutanix’s external repositories during an LCM upgrade.

The Nutanix Unified Storage Administration (NUSA) course explains that “LCM upgrades require the CVMs to access external Nutanix repositories to download software and firmware updates, typically over HTTPS (port 443).” The CVMs initiate the download of upgrade packages for components like Nutanix Objects, which includes the S3-compatible bucket infrastructure. The course further notes that “outbound traffic from CVM IP addresses to the Internet must be allowed on ports such as TCP 80 (HTTP) and TCP 443 (HTTPS) for LCM to successfully retrieve upgrade files.”

The Nutanix Certified Professional - Unified Storage (NCP-US) study guide elaborates that “during an LCM upgrade, CVMs communicate with external Nutanix servers (e.g., download.nutanix.com) to fetch upgrade bundles, requiring outbound Internet access from the CVM IP addresses on TCP ports 80 and 443.” Additionally, DNS resolution (TCP/UDP port 53) is needed to resolve the external repository URLs, and NTP (UDP port 123) ensures time synchronization, both of which are already allowed in the outbound traffic configuration provided. However, the failure suggests that the specific outbound traffic from CVMs to the Internet on port 443 (or 80) was blocked, preventing the download of the Nutanix Objects upgrade package.

The other options are incorrect:

Pod network : The pod network (e.g., 10.100.0.0/16) is typically an internal network range for containerized workloads and does not require Internet access for LCM upgrades.

Prism Central IP address/port : While Prism Central orchestrates the LCM upgrade, it is the CVMs that perform the actual download of upgrade artifacts from the Internet. Prism Central communicates with CVMs internally and does not directly access the Internet for this task.

LCM : LCM is a software component, not a network entity with an IP address or port. It runs on Prism Central and relies on CVMs to fetch the necessary files.

To resolve the issue, the administrator should provide the security team with the CVM IP addresses and ensure that outbound traffic to the Internet is allowed on TCP port 443 (HTTPS) and optionally TCP port 80 (HTTP) for accessing Nutanix’s external repositories (e.g., download.nutanix.com). The NUSA course documentation emphasizes that “ensuring CVMs have Internet access on the required ports is critical for LCM upgrades to complete successfully, especially for components like Nutanix Objects.”

When deploying Nutanix Objects, internal communication and data flow between Object services are isolated using internal overlay IP ranges to avoid collisions with existing customer networks.

The NCP-US and NUSA course materials state:

“Nutanix Objects requires two separate internal IP address ranges: 10.100.0.0/16 and 10.200.0.0/16. These ranges are used exclusively for internal communication within the Nutanix Objects deployment, such as for object metadata, S3 gateway, and load balancing services.”

These 10.x.x.x ranges must not overlap with existing client or management networks.

They provide fully isolated internal object service communication.

Smart DR (Disaster Recovery) for Nutanix Files ensures that the file server VMs (FSVMs) at the recovery site mirror the configuration of the primary site. Specifically, it requires that:

“The number of FSVMs deployed at the recovery site must match the number of FSVMs at the primary site.”

The primary site has 3 FSVMs .

Therefore, the recovery site must also have 3 FSVMs deployed to ensure consistency and proper operation of Smart DR for file services.

Self-Service Restore (SSR) in Nutanix Files is a feature that allows end users or administrators to restore previous file versions directly from share snapshots without requiring direct administrator intervention.

Key details from the NUSA training:

Does not require Nutanix Guest Tools (NGT):

“SSR operates entirely at the file server share level, leveraging share snapshots created by the Nutanix Files service. It does not depend on NGT or VM-level backups, which simplifies deployment and reduces dependencies.”

15-minute snapshots:

“While Nutanix supports snapshot intervals down to 1 hour, the minimum interval is not typically 15 minutes for standard file share snapshots.”

Windows and Linux:

“SSR is primarily supported for Windows SMB shares. NFS/Linux-based shares do not integrate with SSR in the same manner.”

Starter license support:

“SSR is part of advanced Nutanix Files functionality not included in the Starter license tier.”

Thus, the definitive statement: Does not require NGT on the VM .

When hardening the network for Nutanix Objects, the **S3 endpoint** is the only network endpoint that should be exposed to users. Nutanix Objects is an object storage solution that provides an S3-compatible API for accessing and managing objects. The S3 endpoint is the designated interface through which users and applications interact with Nutanix Objects, typically over HTTPS to ensure secure data transfer.

According to the **Nutanix Unified Storage Administration (NUSA)** course, network hardening for Nutanix Objects involves restricting access to only the necessary endpoints to minimize the attack surface. The S3 endpoint, which operates over port 443 (HTTPS) or port 80 (HTTP, though HTTPS is recommended for security), is the primary entry point for client interactions. Exposing only this endpoint ensures that users can access object storage services while other internal or management interfaces remain protected.

The **Nutanix Certified Professional - Unified Storage (NCP-US)** study guide emphasizes that Nutanix Objects is designed to segregate user-facing traffic from internal system traffic. The S3 endpoint is configured during the deployment of Nutanix Objects and is associated with a virtual IP address (VIP) or DNS name that resolves to the object store. To harden the network, administrators should configure firewalls and network security groups to allow traffic only to the S3 endpoint, blocking access to other interfaces such as management or internal network endpoints.

The other options are not suitable for user exposure:

- **virbr0**: This is a virtual bridge interface typically used for internal virtualization networking (e.g., in KVM-based environments). It is not a user-facing endpoint and should not be exposed, as it is used for internal communication between virtual machines or services.

- **eth0**: This refers to a physical Ethernet interface on a node, which may carry various types of traffic (e.g., storage, management, or VM traffic). Exposing eth0 directly to users would compromise security by allowing access to internal system communications.

- **OOB (Out-of-Band)**: This refers to out-of-band management interfaces, such as IPMI or iLO, used for hardware management. These are strictly for administrative purposes and must remain isolated from user access to prevent unauthorized control of the infrastructure.

The NUSA course documentation specifically notes that “Nutanix Objects network hardening requires exposing only the S3 endpoint to external users, typically through a load-balanced VIP, while ensuring all other interfaces, such as management or internal cluster networks, are isolated.” This is achieved by configuring network segmentation, firewalls, and access control lists (ACLs) to restrict traffic to the S3 endpoint.

A single AOS cluster supports a maximum of  4 Nutanix Object Stores . Each object store is an independent instance with dedicated resources.