An existing Object bucket was created for backups with these requirements: * WORM policy of one year * Versioning policy of one year * Lifecycle policy of three years A recent audit has reported a compliance failure. Data that should be retained for three years has been deleted prematurely. How should the administrator resolve the compliance failure within Objects?

The core issue is a compliance failure where data is deleted before its required three-year retention period. The WORM (Write Once, Read Many) policy is the feature that enforces data immutability and prevents deletion for a specified duration. The current WORM policy is set to one year, which is shorter than the three-year requirement. After one year, the WORM lock expires, making the data eligible for deletion. To resolve the compliance failure, the administrator must extend the WORM policy to three years, ensuring the data remains immutable for the entire required retention period.

A. Modifying the versioning policy protects against overwrites by keeping previous versions, but it does not enforce the mandatory retention period against deletion of the current object version.
B. Recreating the bucket is a disruptive and unnecessary action. Nutanix Objects allows an administrator to increase the WORM retention period on an existing bucket.
D. A tiering policy is used to move data between different storage tiers (e.g., hot to cold) for cost optimization; it does not prevent data deletion or enforce immutability.

1. Nutanix Objects 4.0 User Guide, WORM (Write Once Read Many) > Enabling WORM on a Bucket: "You can configure the WORM settings for a new bucket or an existing bucket... You can only increase the retention period. You cannot decrease the retention period." This confirms that modifying the existing bucket's WORM policy is the correct and supported procedure.

2. Nutanix University, Nutanix Unified Storage Administration (NUSA) v6.5 Courseware, Module 5: Managing Nutanix Objects > Lesson 2: Creating and Managing Buckets: The course explains that WORM is used to meet compliance requirements for data retention by making objects immutable for a defined period. This directly links the WORM feature to solving the described compliance problem.

3. Nutanix Bible, Objects Section, by Steven Poitras. While not a formal vendor document, it is a widely respected resource authored by a Nutanix Principal Technical Marketing Engineer. The section on WORM clarifies its purpose: "WORM is a data protection feature that prevents data from being modified or deleted for a certain period of time. This is useful for compliance and regulatory purposes." This supports the rationale that the WORM policy is the correct setting to adjust for compliance retention.