AZ-900 Describe Azure architecture and services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Azure Blob Storage (Cool tier)

  Why it's wrong here

  Blob Storage provides highly scalable object storage with a flat namespace, and the Cool access tier optimizes for long-lived, infrequently accessed data such as backups and archived media—offering lower storage costs but higher access charges and lower availability. While ADLS Gen2 is built on the same blob platform, the Cool tier lacks the hierarchical namespace, POSIX permissions, and directory-optimized throughput that analytical engines require. Frequent reads and complex scans in analytics workloads would incur excessive access costs and latency, making the Cool tier a poor fit for big data processing.

• ✓

  Azure Data Lake Storage Gen2

  Why this is correct

  Azure Data Lake Storage Gen2 (ADLS Gen2) is purpose-built for big data analytics, combining the massive scalability of Azure Blob Storage with a hierarchical file system. The hierarchical namespace enables directory-level operations, atomic rename, and POSIX-style access control lists, which are essential for maximizing throughput in massively parallel analytics engines such as Apache Spark, Azure Synapse, and Databricks. This design also reduces the number of rename/delete operations needed when executing job coordinators, directly improving analytics performance versus flat object storage.

• ✗

  Azure Files Premium

  Why it's wrong here

  Azure Files Premium is a fully managed file share service that supports SMB and NFS protocols and is engineered for low-latency, high-IOPS scenarios such as database applications and Windows Virtual Desktop. Although it offers strong performance, it lacks a hierarchical namespace optimized for query-plan-driven, sequential scans and does not natively integrate with big data tools like Azure Synapse or Spark, making it unsuitable for big data analytics.

• ✗

  Azure Queue Storage

  Why it's wrong here

  Azure Queue Storage is an asynchronous message-queue service that decouples application components by storing small messages (up to 64 KB) that are retrieved with HTTP/S calls. It provides at-least-once delivery and is designed for lightweight workloads like task scheduling or inter-service messaging, not for storing or analyzing large datasets. It has no query engine, no indexing for analytical access patterns, and no hierarchical namespace, so it cannot serve as a data lake for big data analytics.

Go deeper

Related to this question