Standard tiering policies for Nutanix Unified Storage are managed inNutanix Data Lens. Nutanix Data Lens is a cloud-based service that provides data lifecycle management, analytics, and tiering capabilities for Nutanix Files and Objects. It enables administrators to define and manage tiering policies to move data between different storage tiers (e.g., from Nutanix storage to cloud storage like AWS S3) based on access patterns, age, or other criteria.
According to theNutanix Unified Storage Administration (NUSA)course, "Nutanix Data Lens is used to configure and manage standard tiering policies for Nutanix Files and Objects, allowing data to be tiered to cost-effective storage based on predefined rules." This includes setting policies to archive infrequently accessed data to cloud storage, optimizing storage costs while maintaining accessibility.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further clarifies that "Data Lens provides a centralized interface for managing tiering policies, enabling automated data movement to secondary storage tiers, such as cloud-based object stores." Administrators can access Data Lens to define rules for data tiering, monitor tiering activities, and ensure compliance with organizational data management requirements.
The other options are incorrect:
* Prism Central Admin Dashboard: Prism Central is used for cluster management, monitoring, and orchestration but does not provide specific interfaces for managing tiering policies.
* Prism Element Data Protection Dashboard: Prism Element focuses on individual cluster management and data protection tasks (e.g., snapshots, replication), not tiering policies.
* Nutanix Files Console: The Nutanix Files Console is used for configuring and managing file servers and shares, but tiering policies are managed externally through Data Lens.
The NUSA course documentation emphasizes that "Nutanix Data Lens integrates with Nutanix Files to provide tiering capabilities, allowing administrators to manage data placement across on-premises and cloud storage tiers seamlessly." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Data Lens: "Configuring tiering policies for Nutanix Files and Objects." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Data lifecycle management with Nutanix Data Lens." Nutanix Documentation (https://www.nutanix.com), Nutanix Data Lens Guide: "Managing standard tiering policies."

The error message explicitly references anobject-lock enabled bucketand restrictions onmodifying/deleting objects. This points directly to theWORM (Write Once Read Many)feature being enabled on the S3 bucket.
WORM (Object Lock):
* Object Lock (also called WORM)prevents objects from being deleted or modifiedfor a retention period set by the bucket's policy.
* The error states:
"An object from the object-lock enabled bucket can not be modified or deleted unless the retention period is elapsed."
* This directly matches the behavior of an S3 bucket withWORM retention.
The other options:
* A. Bucket name incorrect: Would result in a "NoSuchBucket" or "Not Found" error, not "Method Not Allowed."
* C. Object-Level permissions: Insufficient permissions would cause "Access Denied" or "Forbidden," not WORM-specific errors.
* D. API key misconfiguration: Would typically produce authentication errors ("SignatureDoesNotMatch," etc.), not a WORM policy restriction.
The NUSA course discusses WORM behavior:
"If WORM is enabled on a bucket, objects cannot be deleted or modified until the retention period expires.
Attempting to do so will generate 'Method Not Allowed' errors."
Thus, the error here is directly caused byWORM retention(Object Lock) being active on the S3 bucket.

When deploying Nutanix Files, the client network requiresone additional IP address than the number of File Server Virtual Machines (FSVMs). Nutanix Files uses a distributed architecture where each FSVM handles file services for clients via protocols like SMB or NFS. The client network is used for client-facing traffic, and it requires one IP address per FSVM plus an additional virtual IP address (VIP) that serves as the primary access point for clients.
According to theNutanix Unified Storage Administration (NUSA)course, "Nutanix Files requires one IP address per FSVM on the client network for client communication, plus one additional VIP that provides a unified endpoint for accessing file shares." The VIP is load-balanced across the FSVMs, ensuring high availability and seamless client access even if an FSVM fails.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide further clarifies that "the client network for Nutanix Files must be configured with one IP address for each FSVM and an additional VIP, resulting in a total of N+1 IP addresses, where N is the number of FSVMs." For example, a deployment with three FSVMs requires four IP addresses: three for the FSVMs and one for the VIP.
The other options are incorrect:
* The same number of IP addresses as the number of FSVM nodes: This does not account for the additional VIP required for client access, which is essential for load balancing and failover.
* One less IP address as the number of FSVMs: This is not feasible, as each FSVM requires its own IP address, and the VIP adds an additional requirement.
* Twice as many IP addresses as the number of FSVMs: This overestimates the IP address needs, as only one additional VIP is required, not double the number of FSVMs.
The NUSA course documentation emphasizes that "the client network VIP simplifies client access to Nutanix Files by providing a single IP address that abstracts the underlying FSVMs, requiring one additional IP address beyond the FSVM count." References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Network configuration for client access and VIP setup." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 1: Deploy and Upgrade Nutanix Unified Storage, Subtopic: "Nutanix Files client network IP address requirements." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Client network configuration for Nutanix Files."

The maximum number of snapshots that can be configured for a Nutanix Files snapshot schedule is100.
Nutanix Files supports snapshot schedules to automate the creation of point-in-time snapshots for file shares, which are useful for data protection, recovery, and backup purposes. The snapshot schedule defines how frequently snapshots are taken and how many are retained.
According to theNutanix Unified Storage Administration (NUSA)course, Nutanix Files allows administrators to configure snapshot schedules with a maximum retention of100 snapshotsper share. The course states, "Nutanix Files snapshot schedules can be configured to retain up to 100 snapshots, providing flexible data protection for file shares." This limit ensures that administrators can maintain a sufficient number of recovery points while managing storage efficiency.
TheNutanix Certified Professional - Unified Storage (NCP-US)study guide reinforces this by noting that
"the snapshot schedule for Nutanix Files supports a maximum of 100 snapshots per share, allowing for granular recovery options." Administrators can configure the frequency (e.g., hourly, daily) and retention period, but the total number of snapshots retained cannot exceed 100 per share.
The other options (25, 50, 75) underestimate the maximum snapshot limit for Nutanix Files, as the system supports up to 100 snapshots to accommodate various data protection needs.
References:
Nutanix Unified Storage Administration (NUSA) Course, Section on Nutanix Files: "Configuring snapshot schedules and retention policies." Nutanix Certified Professional - Unified Storage (NCP-US) Study Guide, Topic 2: Configure and Utilize Nutanix Unified Storage, Subtopic: "Snapshot management for Nutanix Files." Nutanix Documentation (https://www.nutanix.com), Nutanix Files Administration Guide: "Snapshot schedules and maximum retention limits."

In Nutanix Objects,bucket management permissionsare granularly controlled. TheEdit Bucketspermission allows a user tomodify bucket configurations(such as policy changes, tagging, and settings), but it doesnot grant the ability todeletethe bucket.
From the NUSA training:
"The Delete Buckets permission is separate from Edit Buckets. Users with Edit Buckets can change configurations but cannot remove the bucket itself." Thus, the user's inability to delete buckets stems fromlacking the explicit Delete Buckets permission.