Curriculum Overview: Azure Storage Accounts and Data Types

This curriculum provides a comprehensive deep-dive into the core storage offerings within Microsoft Azure, specifically aligned with the AZ-900: Azure Fundamentals certification. It covers the structural foundation (Storage Accounts), the nature of data handled (Blobs, Files, Disks), and the strategic configurations (Tiers and Redundancy) required for cloud-scale solutions.

Prerequisites

Before starting this module, students should have a baseline understanding of the following:

• Cloud Computing Fundamentals: Familiarity with IaaS, PaaS, and SaaS models.
• Azure Core Infrastructure: Understanding of Regions and Availability Zones.
• Resource Management: Knowledge of how to create and manage resources in the Azure Portal.
• Basic Data Concepts: A general understanding of structured vs. unstructured data.

Module Breakdown

Learning Objectives per Module

Module 1: The Storage Account Foundation

• Define the Storage Account as the primary container for all Azure Storage data objects.
• Explain why the storage account name must be globally unique.
• Describe the relationship between a storage account and an Azure Subscription/Resource Group.

Module 2: Storage Services & Data Types

• Distinguish between Azure Blob Storage (unstructured data like images/videos) and Azure Files (managed SMB/NFS file shares).
• Describe Azure Disk Storage and its role in persistent VM data.
• Understand Page Blobs and their specific use cases for random read/write operations.

Module 3: Performance Tiers & Account Types

• Compare Standard General-purpose v2 with Premium storage account types.
• Identify the appropriate usage for Hot, Cool, and Archive access tiers.
• Understand that storage account types cannot be changed once created.

Module 4: Redundancy & High Availability

• Describe Locally Redundant Storage (LRS) and Zone Redundant Storage (ZRS).
• Compare local redundancy with regional redundancy (GRS and GZRS).

\begin{tikzpicture} % LRS Representation \draw[thick] (0,0) rectangle (2,2); \node at (1,2.3) {Datacenter (LRS)}; \draw[fill=blue!20] (0.5,0.5) circle (0.2) node{1}; \draw[fill=blue!20] (1,1) circle (0.2) node{2}; \draw[fill=blue!20] (1.5,1.5) circle (0.2) node{3};

% Arrow indicating separation \draw[->, ultra thick] (2.5,1) -- (3.5,1);

% ZRS Representation \draw[dashed] (4,-0.5) rectangle (10,2.5); \node at (7,2.8) {Region (ZRS)};

\draw (4.2,0) rectangle (5.8,2) node[pos=0.5] {Zone 1}; \draw[fill=green!20] (5,1) circle (0.2) node{A};

\draw (6.2,0) rectangle (7.8,2) node[pos=0.5] {Zone 2}; \draw[fill=green!20] (7,1) circle (0.2) node{B};

\draw (8.2,0) rectangle (9.8,2) node[pos=0.5] {Zone 3}; \draw[fill=green!20] (9,1) circle (0.2) node{C}; \end{tikzpicture}

Module 5: Data Migration & Tools

• Identify when to use AzCopy for command-line data transfers.
• Understand the visual interface benefits of Azure Storage Explorer.
• Describe Azure File Sync for caching Azure Files on-premises.

Success Metrics

To achieve mastery of this curriculum, the learner should be able to:

1. Select the correct storage service given a scenario (e.g., "Which service should store 5TB of log files?" -> Blob Storage).
2. Calculate cost-efficiency by correctly assigning data to Hot, Cool, or Archive tiers based on access frequency.
3. Architect for Resilience by choosing between LRS, ZRS, or GRS based on a recovery point objective (RPO).
4. Execute a data move using the AzCopy utility to transfer a local directory to a cloud container.

Real-World Application

• Cost Optimization: A company saves thousands of dollars monthly by moving legacy backup data from Standard Hot storage to the Archive tier.
• Disaster Recovery: By selecting Geo-Redundant Storage (GRS), a business ensures that even if an entire Azure region goes offline due to a natural disaster, their data remains accessible in a secondary region.
• Hybrid Cloud: Using Azure File Sync, a branch office maintains the performance of a local file server while automatically backing up all files to Azure for centralized management and cloud-tiering.