The lifecycle management policy lets you:
Delete blobs, blob versions, and blob snapshots at the end of their lifecycles
[Reference:, https://docs.microsoft.com/en-us/azure/storage/blobs/storage-lifecycle-management-concepts, , , , , , , , Basic Concept: This question tests plan and configure a high availability and disaster recovery (ha/dr) environment in the DP-300 exam context. The correct choice is determined by the exact service boundary and operational requirement stated in the scenario., Why C is Correct: lifecycle management matches the expected DP-300 administration action. lifecycle management is part of the availability or recovery design space, but the correct choice must satisfy the specified failover, restore, quorum, RPO, or RTO requirement. The question is not asking for a general Azure capability; it is asking for the feature that produces this result: You need to design a data retention solution for the Twitter feed data records., Why A is Wrong: time-based retention is part of the availability or recovery design space, but the correct choice must satisfy the specified failover, restore, quorum, RPO, or RTO requirement. It does not meet the failover, restore, quorum, or cross-region continuity target stated in the question, even if it is valid in a different availability design., Why B is Wrong: change feed is part of the availability or recovery design space, but the correct choice must satisfy the specified failover, restore, quorum, RPO, or RTO requirement. It handles a different resilience pattern and would not deliver the failover or recovery behavior required here., Why D is Wrong: soft delete is part of the availability or recovery design space, but the correct choice must satisfy the specified failover, restore, quorum, RPO, or RTO requirement. It does not meet the failover, restore, quorum, or cross-region continuity target stated in the question, even if it is valid in a different availability design., ]
