A retention policy must move inactive objects and eventually delete expired versions automatically, but no immediate deadline is required. Which mechanism fits?

Choose the single best answer.

A.Versioning enabled without any policy to age out expired objects
B.A lifecycle rule used as a guaranteed real-time workflow callback
C.Blob lifecycle management with scoped supported rules and retention constraints
D.Manual tier changes with no scheduled or policy-driven version-expiration process

Show the answer and explanation

✓ Correct answer

Blob lifecycle management with scoped supported rules and retention constraints

Lifecycle asynchronously tiers/deletes eligible objects by supported rules. It is not a guaranteed immediate callback. Manual-only changes do not supply the requested automation, and versioning retains versions without itself defining their business expiration/tiering policy. Source guide: PDF page 28.

Read the source reference

This item is flagged for content review.

Read and review here, or open the app to practise and save your results on this device.

Practise in the app

Unofficial study aid; not affiliated with or endorsed by Microsoft. Original practice questions are not real examination questions and do not guarantee an exam result.