Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
General-Purpose v2 for Unified Azure Storage
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
A company is deploying new cloud workloads to Microsoft Azure and requires a centralized storage solution. The solution must support multiple core storage models, including unstructured files (Blob Storage), file shares (Azure Files), message queues (Azure Queue Storage), and NoSQL key-value records (Azure Table Storage), while providing access to tiering features.
Which Azure storage account type should the company select?
Explanations
Classic Azure Storage account (General-purpose v1)
Classic Azure Storage account (General-purpose v1)
What Classic / GPv1 Storage Accounts Are
General-purpose v1 (GPv1), often associated with legacy or classic storage configurations, represents the older generation of Azure Storage accounts created prior to GPv2.
Why It Doesn't Meet the Requirement
- Missing Access Tiers: GPv1 accounts do not support blob access tiers (Hot, Cool, Cold, and Archive), meaning all data is billed at a flat rate without lifecycle tiering.
- Higher Capacity Costs: GPv1 accounts typically incur higher per-gigabyte data storage costs compared to GPv2 accounts.
- Limited Modern Integrations: Many newer Azure capabilities and integration features do not support classic or GPv1 architectures.
Key Characteristics and Limitations
- Legacy Design: Predecessor to GPv2 that lacks the newest feature updates.
- Flat Pricing Model: Does not provide tiered pricing options for infrequently accessed or archived data.
- No Native Lifecycle Management: Cannot automatically move aged blobs to colder tiers.
This Answer Would Be Correct If
This choice would be appropriate only when maintaining legacy cloud architectures that have specific dependency constraints on older API versions or where account upgrade is temporarily blocked.
Additional Context
Organizations are strongly advised to upgrade existing GPv1 accounts to General-purpose v2 to take advantage of lower storage rates and access tier capabilities.
General-purpose v2 (GPv2)
General-purpose v2 (GPv2)
What General-purpose v2 Is
General-purpose v2 (GPv2) is the default, standard storage account type recommended by Microsoft for most cloud scenarios. It provides access to all fundamental Azure Storage services within a single administrative container, including Azure Blobs, Azure Files, Azure Queues, and Azure Tables.
How It Meets the Requirements
- Unified Multi-Service Support: GPv2 provides simultaneous native access to blobs, file shares, queues, and tables within the same storage account.
- Access Tier Management: GPv2 natively supports all blob access tiers (Hot, Cool, Cold, and Archive), allowing organizations to optimize storage expenditure based on data lifecycle patterns.
- Modern Feature Set: It incorporates the latest Azure capabilities, including granular role-based access control (RBAC), advanced encryption, soft delete, and data lifecycle management policies.
Key Advantages and Capabilities
- Comprehensive Service Integration: Delivers complete support for Block Blobs, Page Blobs, Append Blobs, Azure Files, Queues, and Tables.
- Cost Optimization: Features competitive per-gigabyte storage pricing along with tiered storage options.
- Flexible Redundancy: Supports locally redundant storage (LRS), zone-redundant storage (ZRS), geo-redundant storage (GRS), and geo-zone-redundant storage (GZRS).
- Lifecycle Automation: Enables automated data movement between access tiers using configured lifecycle management rules.
Why This Is Optimal
General-purpose v2 is the standard, modern deployment choice for Azure storage workloads. Unlike legacy Blob Storage accounts or legacy GPv1 accounts, GPv2 includes modern pricing models and access tier support across all primary Azure storage data services.
Legacy Blob Storage account
Legacy Blob Storage account
What Legacy Blob Storage Accounts Are
A Blob Storage account is a legacy, specialized account type that was dedicated exclusively to storing unstructured object data as block blobs and append blobs.
Why It Doesn't Meet the Requirement
- Lack of Multi-Service Support: Legacy Blob Storage accounts cannot host Azure Files, Azure Queues, or Azure Tables. They are limited solely to object (blob) data.
- Superseded by GPv2: Microsoft has deprecated the creation of new standalone Blob Storage accounts in favor of General-purpose v2, which provides the same blob functionality alongside the other three storage services.
Key Characteristics and Limitations
- Single Service Focus: Restricts storage strictly to Block Blobs and Append Blobs.
- No File, Queue, or Table Support: Incapable of supporting SMB file shares or message queues.
- Legacy Status: Considered legacy architecture; existing accounts should be upgraded to GPv2 to leverage newer features.
This Answer Would Be Correct If
This choice would only be relevant in historical maintenance scenarios where an existing deployment exclusively stores blob data and has not yet been upgraded to General-purpose v2.
Additional Context
Upgrading a legacy Blob Storage account to a General-purpose v2 account can be performed seamlessly without downtime or data migration.
Premium Block Blob storage account
Premium Block Blob storage account
What Premium Block Blob Storage Is
A Premium Block Blob storage account is a high-performance storage option optimized for workloads requiring high transaction rates, low latency, and consistent single-digit millisecond response times.
Why It Doesn't Meet the Requirement
- Restricted Service Scope: Premium block blob accounts do not support Azure Files, Azure Queues, or Azure Tables.
- No Access Tier Support: Unlike standard GPv2 accounts, Premium block blob storage accounts do not support blob access tiers such as Hot, Cool, Cold, or Archive.
- Cost Inefficiency: Data is stored exclusively on high-speed solid-state drives (SSDs), which is unnecessary and cost-prohibitive for standard queues, tables, and general file storage.
Key Characteristics and Limitations
- SSD-Backed Storage: Delivers ultra-low latency for demanding analytical and telemetry workloads.
- No Tiering Options: Omits support for access tiers; all data resides on the premium performance tier.
- Blob-Only Workloads: Specialized only for block and append blobs.
This Answer Would Be Correct If
This option would be ideal for specialized applications that process large numbers of small transactions rapidly (such as real-time video editing or telemetry streaming) and require low-latency SSD performance without needing file shares, queues, or tables.
Additional Context
When copying data between premium accounts and standard GPv2 accounts using tools like AzCopy, access tier flags must be omitted because premium accounts do not use access tiers.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Blob Storage Archive Tier
Describe storage account options and storage types
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Files
Describe storage account options and storage types
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Geo-Redundant Storage (GRS)
Describe storage account options and storage types
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Storage Customer-Managed Keys
Describe storage account options and storage types
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Virtual Network Subnets
Describe virtual networking, including the purpose of Azure virtual networks, subnets, peering, Azure DNS, Azure VPN Gateway, and ExpressRoute
ExpertAZ-500 Microsoft Azure Security Technologies Exam
Application Permissions vs Delegated Permissions
Configure app registration permission scopes
Last updated Validated