Soru

Zorluk: OrtaData Lifecycle Management and Retention

An enterprise architecture team is designing a data retention strategy for database transaction backups stored in an Azure Blob Storage General-purpose v2 (GPv2) account. The backups must be managed according to the following requirements:

* Backups must be immediately available for recovery operations for the first 45 days after creation, with sub-second retrieval times.
* Between 46 days and 365 days, the backups are occasionally needed for testing and must be retrievable within a few seconds.
* After 365 days, the backups must be retained for an additional 4 years to meet regulatory compliance. They are rarely accessed, and a retrieval latency of up to 15 hours is acceptable.
* The design must minimize storage and retrieval costs.

Which two actions should you include in the lifecycle management policy?

  1. Transition the backups to the Cool tier 45 days after creation.Cevap
  2. Transition the backups to the Archive tier 365 days after creation.Cevap
  3. C
    Transition the backups to the Archive tier 45 days after creation.
  4. D
    Transition the backups to the Archive tier 15 days after creation.

Cevap

Include the actions to transition the backups to the Cool tier 45 days after creation and transition the backups to the Archive tier 365 days after creation.
Transitioning the backups to the Cool tier 45 days after creation ensures they remain online with sub-second retrieval speeds for the subsequent compliance checks up to day 365. Transitioning the backups to the Archive tier after 365 days minimizes storage costs for the remaining 4 years of regulatory retention, where standard rehydration latency (up to 15 hours) is acceptable.

Adım Adım Çözüm

1
Evaluate the access requirements for the first 45 days.
The backups must remain in the Hot tier (the default tier upon upload) for 45 days to support immediate, sub-second retrieval times for recovery operations.
Moving backups to Cool or Archive prior to 45 days would either incur higher early transaction costs or violate the immediate availability requirement.
2
Evaluate the access requirements between 46 and 365 days.
Transition the backups to the Cool tier 45 days after creation. Cool tier supports millisecond-level retrieval times (a few seconds) at a reduced storage cost compared to the Hot tier.
This satisfies the requirement for occasional retrieval within a few seconds while optimizing storage costs.
3
Evaluate the access requirements after 365 days.
Transition the backups to the Archive tier 365 days after creation.
After one year, the backups are rarely accessed and can tolerate a retrieval latency of up to 15 hours. The Archive tier is the most cost-effective tier for this pattern, and standard rehydration times fall within the 15-hour threshold.

Anahtar Kavram

Azure Blob Storage lifecycle management policies automate the transition of data between Hot, Cool, and Archive tiers based on age and access patterns, balancing retrieval latency and storage costs.
Bu soruyu puanla