DP-900: Microsoft Azure Data Fundamentals

File Based Storage

Container Blob Storage

Azure Blob Storage provides a flat, internet-friendly namespace for managing files in the cloud. It’s the go-to solution for scalable object storage, offering robust security, tiered pricing, and rich data management features.

The image is a diagram titled "Container/Blob Storage" showing a structure with "Containers (Blobs)" at the top, followed by "Internet-friendly" and "Ubiquitous" in colored blocks.

Architecture and Namespace

Within an Azure Storage account, you organize data into containers—each holding an unlimited number of blobs (files). This flat namespace means:

  • Containers cannot be nested, ensuring concise URLs (e.g., https://<account>.blob.core.windows.net/<container>/<blob>).
  • Each blob can be up to 4 TB in size.
  • You can create as many containers as needed.

The image illustrates a storage structure with storage accounts leading to multiple containers and blobs, highlighting features like a flat structure, multiple blobs, and a maximum blob size of 4 TB.

Blob Types and Use Cases

Azure supports three blob types to optimize for different scenarios:

Blob TypeDescriptionCommon Use Case
Block blobsEfficient for uploading/downloading large files in blocks.Images, videos, documents
Page blobsRandom read/write on fixed-size pages (512 B pages).Virtual machine disks
Append blobsOptimized for append-only operations; ideal for continuous logs.Telemetry logging, audit trails

The image is an infographic describing three types of blobs: Block Blobs, Page Blobs, and Append Blobs, each with their specific uses and characteristics.

Access Tiers in Standard Storage Accounts

Optimize costs by selecting the right access tier:

TierStorage CostRead/Write CostBest For
HotHigherLowerFrequently accessed
CoolLowerHigherInfrequently accessed

The image compares "Hot" and "Cool" data storage accounts, highlighting that "Hot" accounts have more expensive storage but cheaper upload/download charges, while "Cool" accounts have cheaper storage but more expensive upload/download charges.

Archive Tier

For long-term retention of rarely accessed data:

  • Archive: Lowest storage cost, highest retrieval latency (up to 15 hours) and cost.

The image describes "Archive Accounts" as a storage solution for rarely used files, highlighting features like very high latency, very cheap storage, and high retrieval costs. It notes that retrieving data can take hours.

Storage Account Options at a Glance

Choose from these account types and tiers:

  • Premium: Low-latency, high-throughput workloads.
  • Standard Hot: Frequently accessed data.
  • Standard Cool: Infrequently accessed data.
  • Archive: Long-term storage for rarely accessed files.

The image is a diagram categorizing different types of storage accounts and their usage: Premium Accounts for critical low-latency files, Standard Account hot tier for frequently accessed files, Standard Account cool tier for less frequently accessed files, and Archive for rarely used files.

Pricing and Retention Policies

Billing factors include:

  • Data stored (GB/month)
  • Data operations (ingress/egress)

Standard cool and archive tiers have minimum retention periods:

TierMinimum Retention
Cool30 days
Archive180 days

Note

Early deletion in cool or archive tiers incurs an early deletion fee for any data removed before the minimum retention period.

The image shows a pricing and timing chart for two account types: "Standard Account, cool tier" with a 30-day minimum and "Archive" with a 180-day minimum.

Automating Data Lifecycle with Policies

Use Azure Blob Lifecycle Management to transition blobs between tiers or delete stale data automatically based on rules (e.g., age, last modified).

{
  "rules": [
    {
      "name": "move-to-cool",
      "type": "Lifecycle",
      "enabled": true,
      "definition": {
        "filters": { "blobTypes": ["blockBlob"] },
        "actions": {
          "baseBlob": { "tierToCool": { "daysAfterModificationGreaterThan": 30 } }
        }
      }
    }
  ]
}

The image illustrates a lifecycle management policy flowchart, showing data transitioning from "Standard Accounts" through "HOT" and "COOL" storage, to "Archive," and finally to "Deletion."

Change Tracking with Blob Change Feed

Enable Blob Change Feed to record every change (create, update, delete) in a durable, replayable log. This supports:

  • Point-in-time restores
  • Auditing and compliance
  • Data synchronization across accounts

The image is an infographic about "Blob Change Feed" in a storage account, highlighting features like automatic tracking of changes, record-keeping, backup plan restore, and file synchronization to external storage.

Watch Video

Watch video content

Previous
Demo Files Shares