A company requires that all data in an Azure Blob Storage account remain in the archive tier. How can you ensure that data copied into the account is immediately placed into the archive tier?

A lifecycle policy is the correct Azure Blob Storage feature for managing tiering. By setting the action to tierToArchive and daysAfterModificationGreaterThan to 0, you ensure that any blob copied or uploaded to the storage account is immediately moved to the archive tier. This configuration applies to newly created or modified blobs as soon as the policy runs, effectively placing them directly into archive. Using Put Block List or Put Blob operations with immutability policy headers (x-ms-immutability-policy-mode or x-ms-immutability-policy-until-date) is incorrect because these headers are for setting immutability, not for defining the initial access tier of a blob. While immutability can be applied to blobs, it doesn't control their tiering. Configuring a lifecycle policy with blobIndexMatch is incorrect because blobIndexMatch is used to filter blobs based on their index tags, not to define their initial tiering behavior based on creation or modification time. While it can be part of a lifecycle rule, it doesn't achieve immediate archive tiering for all new data.