You must protect business-critical blobs so they cannot be modified or deleted for a customer-defined retention period, prevent overwrites and deletes, and support write-once/read-many behavior. Which two actions should you take on the storage account?

To meet the requirements of preventing modification or deletion for a defined retention period and supporting write-once/read-many (WORM) behavior, you need to implement immutability. A time-based retention policy allows you to specify a duration during which blobs cannot be modified or deleted. Enabling version-level immutability support extends this protection to individual blob versions, ensuring that once a version is written, it remains immutable. Creating an account or service shared-access signature (SAS) provides delegated access to resources but does not enforce immutability. Enabling the blob change feed tracks changes to blobs but doesn't prevent them. Enabling point-in-time restore allows restoring data to an earlier state but doesn't enforce WORM compliance.