The correct answer is Create a lifecycle management rule that uses the tierToArchive action and set daysAfterModificationGreaterThan to 1.

A lifecycle management rule using the tierToArchive action will automatically move blobs into the Archive tier after the configured waiting period and it works for blobs that are copied into the account. The daysAfterModificationGreaterThan setting lets you ensure the service only transitions blobs after they are stable for the specified number of days which is appropriate for copy operations.

Use a Put Block List request with the x-ms-immutability-policy-mode header is incorrect because the x-ms-immutability-policy-mode header relates to immutability and retention policies and it does not control access tiers. Immutability prevents modifications and deletions according to a policy but it does not automatically archive blobs.

Include the x-ms-access-tier header set to Archive on the Put Blob request is incorrect for this scenario because copying workflows often do not apply that header during server side copy operations and relying on the header does not guarantee every copied blob will end up in Archive. Lifecycle rules provide a reliable account level mechanism to transition copied blobs.

Create a lifecycle management rule with tierToArchive and apply a blobIndexMatch filter is incorrect because adding a blobIndexMatch filter limits the rule to blobs that match specific tags. The requirement is that each uploaded blob be placed in Archive so a filtered rule would not ensure all copied blobs are transitioned.

Full AWS Practitioner Certification Question