Examkin

Soru

Zorluk: OrtaData Lifecycle Management and Retention

A healthcare provider ingests patient monitoring telemetry into an Azure Blob Storage account. The storage solution must remain resilient against a primary datacenter outage. The data lifecycle and access patterns are defined as follows:

* The telemetry is highly active and requires sub-second retrieval latency for the first 1414 days.
* From day 1515 through day 9090, the telemetry is accessed infrequently but must be available for immediate, sub-second querying.
* After 9090 days, the telemetry is only accessed for regulatory compliance audits that tolerate a retrieval latency of up to 1515 hours.
* All telemetry must be retained for 77 years (2,5552,555 days) and then deleted.

You need to design a storage and lifecycle management strategy that meets these requirements at the lowest possible cost.

Which strategy should you recommend?

  1. A
    Configure a Zone-Redundant Storage (ZRS) account. Create a lifecycle policy to transition blobs from the Hot tier to the Archive tier after 14 days, and delete them after 2555 days.
  2. B
    Configure a Locally Redundant Storage (LRS) account. Create a lifecycle policy to transition blobs from the Hot tier to the Cool tier after 14 days, transition them to the Archive tier after 90 days, and delete them after 2555 days.
  3. Configure a Zone-Redundant Storage (ZRS) account. Create a lifecycle policy to transition blobs from the Hot tier to the Cool tier after 14 days, transition them to the Archive tier after 90 days, and delete them after 2555 days.Cevap
  4. D
    Configure a Zone-Redundant Storage (ZRS) account. Create a lifecycle policy to transition blobs from the Hot tier to the Archive tier after 30 days, and delete them after 2555 days.

Cevap

Configure a Zone-Redundant Storage (ZRS) account. Create a lifecycle policy to transition blobs from the Hot tier to the Cool tier after 14 days, transition them to the Archive tier after 90 days, and delete them after 2555 days.
The correct strategy uses Zone-Redundant Storage (ZRS) to protect against a primary datacenter outage by replicating data across three availability zones. It uses the Cool tier from day 15 to day 90 to meet the requirement for immediate, sub-second query access at a lower storage cost compared to the Hot tier. Moving the telemetry to the Archive tier after 90 days achieves the lowest storage cost while satisfying the regulatory audit requirement, which tolerates the latency associated with Archive rehydration. Deleting the data after 2555 days satisfies the 7-year retention limit.

Adım Adım Çözüm

1
Analyze the redundancy requirement to ensure survival during a primary datacenter outage.
Eliminate Locally Redundant Storage (LRS) options as they replicate data within a single datacenter, and select Zone-Redundant Storage (ZRS) which replicates data across three separate zones in the region.
This guarantees data availability even if a primary datacenter experiences an outage.
2
Evaluate access frequency and retrieval latency constraints for each timeline window.
Determine that the first 1414 days require Hot tier, days 1515 to 9090 require Cool tier (since sub-second query latency is needed and Cool tier keeps the data online), and after 9090 days the data can transition to Archive tier.
Archive tier data is offline and cannot be queried with sub-second latency, meaning the transition to Archive must be deferred until day 9191 when the 1515-hour latency limit for compliance audits applies.
3
Calculate retention and deletion constraints.
Configure the final action to delete the blobs after 2,5552,555 days (77 years).
This minimizes long-term storage costs once the compliance retention period expires.

Anahtar Kavram

Selecting Azure storage redundancy and lifecycle management transition policies based on redundancy needs, latency constraints, and cost optimization.
Bu soruyu puanla

Konular

Data Lifecycle Management and Retention

Bu konudan daha fazla soru