Summary of "AZ-204 Exam EP 12: Blob Storage Lifecycle"

This lesson covers managing the lifecycle of Azure Blob Storage, focusing on storage tiers, pricing, and lifecycle management policies to optimize cost and performance.

Main Ideas and Concepts

Azure Blob Storage Tiers Azure offers multiple storage tiers designed to balance cost and access performance based on data usage patterns:
- Premium Storage
  - Performance tier optimized for mission-critical, high-performance applications
  - Available only for block blob storage
- Standard Performance Tier (General Purpose v2 accounts)
  - Hot Tier: For frequently accessed data
  - Cool Tier: For infrequently accessed data, stored at least 30 days
  - Archive Tier: For rarely accessed data, stored at least 180 days, with flexible latency (hours)
- Tier-specific considerations:
  - Archive Tier is available only at the blob level, not the entire storage account
  - Cool Tier offers slightly lower availability but high durability and similar access/throughput as Hot Tier
Storage Pricing Overview
- Premium and Hot tiers have the highest cost per GB/month but lowest cost per 10,000 read operations, suitable for transactional workloads
- Cool and Archive tiers have lower storage costs but higher transaction costs, optimized for large volumes of less frequently accessed data
Lifecycle Management in Azure Blob Storage
- Supports rule-based policies for General Purpose v2 and Blob Storage accounts
- Policies automate transitioning blobs between tiers or deleting blobs at the end of their lifecycle
- Rules run once per day at the storage account level
- Lifecycle management helps optimize costs by moving data to cheaper tiers as it ages
- Example workflow:
  - Hot Tier for new/active data
  - Cool Tier for occasional access after some time
  - Archive Tier for long-term storage after data ages beyond a month
- Policies can have:
  - At least one rule, up to 100 rules per policy
  - Rule names are unique, case-sensitive, up to 256 alphanumeric characters
  - Each rule consists of a filter set (to select blobs) and an action set (to define transitions or deletions)

Methodology / Instructions for Lifecycle Management Policy

Define a lifecycle management policy at the storage account level
Include one or more rules (up to 100) per policy
Each rule must have:
- A unique, case-sensitive name (up to 256 alphanumeric characters)
- A filter set to select the blobs the rule applies to (e.g., by blob type, prefix, or age)
- An action set specifying what to do (e.g., transition to a cooler tier or delete)
Schedule rules to run once per day automatically
Use age-based transitions to move data from Hot → Cool → Archive tiers to reduce costs
Optionally, configure rules to delete blobs at the end of their lifecycle

Speakers / Sources Featured

The lesson appears to be delivered by a single instructor or presenter (name not specified) who guides through the concepts and examples related to Azure Blob Storage lifecycle management.

End of Summary