Courseiva
Describe Azure architecture and serviceseasyMultiple ChoiceObjective-mapped

AZ-900 Describe Azure architecture and services Practice Question

What type of data does Azure Table Storage store?

⚠ Common exam trap

Many candidates confuse Azure Table Storage with Blob Storage (for unstructured data) or Azure SQL Database (for relational data), overlooking that Table Storage is specifically designed for structured NoSQL key-attribute entities.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Structured NoSQL data in a key-attribute entity model

Azure Table Storage is a NoSQL key-attribute store that stores structured, schema-less data. Each entity is a set of properties (attributes) with a partition key and row key, enabling fast access to semi-structured data like user profiles or device metadata.

Answer analysis

Option-by-option breakdown

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

  • Unstructured binary data like images and videos

    Why it's wrong here

    Azure Blob Storage is the correct service for unstructured binary data such as images, videos, and documents. Table Storage, by contrast, is a NoSQL key-attribute store that requires every entity to conform to a row schema with a partition key, a row key, and user-defined properties. Binary data cannot be queried by those attributes and would instead be stored as a blob resource, typically with its own access tier and lifecycle management.

  • Structured NoSQL data in a key-attribute entity model

    Why this is correct

    Azure Table Storage is a NoSQL key-value store designed for structured data in a key-attribute model. Each entity is a collection of properties (attributes) with a required partition key and row key that together form the entity's primary key. This design supports efficient point queries and range scans on the row key while remaining schemaless, so entities in the same table can have different sets of properties—ideal for large-scale, flexible structured NoSQL workloads.

  • Relational data with complex joins and foreign keys

    Why it's wrong here

    Relational data that relies on foreign keys, normalization, and complex joins belongs in Azure SQL Database or SQL Managed Instance. Table Storage is intentionally non-relational: it offers no concept of foreign keys, cross-partition join operations, or transactions spanning multiple entities. While you could denormalize multi-table structures into entities, doing so would force you to manually handle consistency and duplicate data, forfeiting the core benefits of a relational database engine.

  • Files shared via SMB protocol across Windows machines

    Why it's wrong here

    SMB-based file sharing is provided by Azure Files, not Azure Table Storage. Azure Files exposes fully managed file shares that speak the Server Message Block protocol, allowing legacy Windows VMs and on-premises applications to mount them as standard network drives. Table Storage is an HTTP-based key-value service for tabular entities; it does not implement the SMB protocol or support file-level operations such as creating folders, file locking, or streaming file handles.

About these practice questions

This AZ-900 question is part of Courseiva's 981-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This AZ-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-900 exam.