An administrator is troubleshooting an automated script designed to analyze security logs stored in an Azure Blob Storage account. The logs are stored in a container that has its access tier set to Archive to minimize storage costs. The script, which runs on an Azure Virtual Machine, fails with an error when attempting to read the log files directly. What is the cause of this script failure?
- The log files are in the Archive access tier, which requires the data to be rehydrated to the Hot or Cool tier before it can be read.Cevap
- BThe virtual machine hosting the script is an Infrastructure as a Service (IaaS) resource, meaning Microsoft is responsible for managing the internal file system configurations and storage client libraries required to access the archived data.
- CThe Archive access tier only allows direct read operations for files smaller than a specific size limit, and the script failed because the security log files exceeded this threshold.
- DThe Archive access tier is designed for offline storage and requires a manual key rotation event to unlock direct read access for API-based scripts.
Cevap
The log files are in the Archive access tier, which requires the data to be rehydrated to the Hot or Cool tier before it can be read.
The correct option is correct because the Archive access tier is an offline storage tier designed for data that is rarely accessed. Data in the Archive tier cannot be read or modified directly. To read the data, the blobs must first be rehydrated to an online tier (Hot or Cool) by either changing the tier of the blob or copying it to a new blob in an online tier.
Adım Adım Çözüm
Anahtar Kavram
Azure Blob Storage access tiers (Hot, Cool, Cold, Archive) and their access patterns, specifically the requirement to rehydrate archived blobs before they can be read.