Category: DP-900

Practice Questions: Identify use cases for Azure Cosmos DB (DP-900 Exam Prep)

Practice Questions


Question 1

Which scenario is BEST suited for Azure Cosmos DB?

A. Running complex SQL joins across multiple tables
B. Storing structured financial transactions with strict relational constraints
C. Supporting a globally distributed mobile application with low latency
D. Hosting a traditional on-premises file share

Answer: C

Explanation:
Cosmos DB is ideal for globally distributed applications requiring low latency.


Question 2

Which type of application benefits MOST from Cosmos DB’s global distribution capabilities?

A. Local desktop application
B. Single-region reporting system
C. Global e-commerce website
D. Batch processing system

Answer: C

Explanation:
Global applications benefit from multi-region replication and low latency.


Question 3

Which use case is BEST suited for Cosmos DB?

A. Data warehouse for historical reporting
B. IoT application collecting real-time sensor data
C. Relational database with complex joins
D. File storage for images

Answer: B

Explanation:
Cosmos DB is optimized for high-ingestion, real-time data scenarios like IoT.


Question 4

Why is Cosmos DB suitable for real-time personalization scenarios?

A. It enforces strict relational schemas
B. It supports high-latency operations
C. It provides low-latency read/write performance
D. It requires predefined schemas

Answer: C

Explanation:
Low latency enables instant updates and responses for personalization.


Question 5

Which application would MOST benefit from Cosmos DB?

A. Payroll system requiring strict ACID compliance across multiple tables
B. Static website hosting images
C. Gaming application storing player state globally
D. Spreadsheet-based reporting system

Answer: C

Explanation:
Gaming apps require low latency, high throughput, and global availability.


Question 6

Which scenario is NOT a good fit for Cosmos DB?

A. Global content management system
B. Real-time analytics dashboard
C. Complex relational reporting with joins
D. Social media application

Answer: C

Explanation:
Cosmos DB is not ideal for complex relational queries or joins.


Question 7

Which feature of Cosmos DB makes it ideal for microservices architectures?

A. Fixed schema design
B. Independent scalability for each service
C. Requirement for relational constraints
D. Limited throughput options

Answer: B

Explanation:
Each microservice can scale independently using Cosmos DB.


Question 8

Which use case involves storing flexible, evolving data structures?

A. Financial ledger system
B. Product catalog with changing attributes
C. Relational reporting system
D. Fixed-schema inventory system

Answer: B

Explanation:
Cosmos DB’s schema-less design supports evolving data models.


Question 9

Which scenario best demonstrates Cosmos DB’s high-throughput capabilities?

A. Processing monthly reports
B. Handling millions of real-time user requests
C. Archiving old documents
D. Storing backup files

Answer: B

Explanation:
Cosmos DB is designed for high-throughput, real-time workloads.


Question 10

Which Azure service would you choose for a globally distributed application requiring millisecond response times?

A. Azure Blob Storage
B. Azure Files
C. Azure Cosmos DB
D. Azure Table Storage

Answer: C

Explanation:
Cosmos DB is specifically designed for low-latency, globally distributed applications.


✅ Quick Exam Takeaways

✔ Cosmos DB = global, low-latency NoSQL database

✔ Best for:

  • Global web/mobile apps
  • IoT and telemetry
  • Gaming
  • Real-time personalization
  • Microservices

✔ Key strengths:

  • Global distribution
  • Massive scalability
  • Flexible schema
  • High throughput

✔ Not ideal for:

  • Complex joins
  • Strict relational workloads

✔ Exam tip:
👉 If you see “global + real-time + high scale” → think Cosmos DB


Go to the DP-900 Exam Prep Hub main page.

Describe Azure Table storage (DP-900 Exam Prep)

This post is a part of the DP-900: Microsoft Azure Data Fundamentals Exam Prep Hub. 
This topic falls under these sections:
Describe considerations for working with non-relational data on Azure (15–20%)
--> Describe capabilities of Azure storage
--> Describe Azure Table storage


Note that there are 10 practice questions (with answers and explanations) for each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available on the hub below the exam topics section.

Azure Table Storage is a scalable, low-cost storage solution designed to store large amounts of structured, non-relational data.

For the DP-900 exam, you should understand what Table Storage is, how it is structured, and when to use it compared to other Azure storage options.


What Is Azure Table Storage?

Azure Table Storage is a NoSQL key-value store that:

  • Stores data in tables (but not relational tables)
  • Does not enforce a fixed schema
  • Is optimized for fast access using keys

✔ Despite the name “table,” it is not a relational database.


Key Characteristics


1. Schema-less Design

  • Each record (entity) can have different properties
  • No fixed columns required across all records

✔ Enables flexibility for evolving data models.


2. Key-Based Access

Each entity is uniquely identified by:

  • Partition Key → groups related data
  • Row Key → uniquely identifies an entity within a partition

✔ These keys are critical for performance and query efficiency.


3. Massive Scalability

  • Can store billions of entities
  • Automatically scales to handle large workloads

4. High Performance

  • Optimized for fast read/write operations
  • Best performance when querying by Partition Key and Row Key

5. Cost-Effective

  • Low storage cost compared to relational databases
  • Pay-per-use pricing model

Table Storage Structure

Azure Table Storage is organized as:

  • Storage Account → top-level container
  • Table → collection of entities
  • Entity → a row of data
  • Properties → attributes of an entity

💡 Example:

PartitionKeyRowKeyNameAge
Sales001John30
Sales002Jane28

✔ Entities in the same table can have different properties.


Core Concepts


Partition Key

  • Determines how data is distributed
  • Improves scalability and performance
  • Groups related data together

Row Key

  • Unique identifier within a partition
  • Used for fast lookups

Entity

  • Equivalent to a row
  • Contains key-value pairs (properties)

Common Use Cases

Azure Table Storage is ideal for:

  • Storing large volumes of structured data
  • User profiles or metadata
  • IoT device data
  • Application configuration data
  • Log or telemetry data

✔ Best when simple, fast key-based access is needed.


Azure Table Storage vs Azure Cosmos DB (Table API)

This distinction is important for DP-900:

FeatureAzure Table StorageAzure Cosmos DB (Table API)
PerformanceStandardHigher performance
Global DistributionLimitedMulti-region replication
SLABasicEnterprise-grade
CostLowerHigher

✔ Cosmos DB is often used when global scale and advanced features are required.


When to Use Azure Table Storage

Use Table Storage when:

  • You need NoSQL key-value storage
  • Your data is structured but non-relational
  • You require high scalability at low cost
  • You can design around Partition Key / Row Key access patterns

When NOT to Use It

Avoid Table Storage when:

  • You need complex queries or joins
  • You require relational integrity
  • You need advanced analytics capabilities

Why This Matters for DP-900

On the exam, you may be asked to:

  • Identify Table Storage as a NoSQL key-value store
  • Understand Partition Key and Row Key concepts
  • Choose it for simple, scalable data storage scenarios
  • Compare it with Blob Storage, Azure Files, or Cosmos DB

Summary — Exam-Relevant Takeaways

✔ Azure Table Storage = NoSQL key-value storage
✔ Stores structured, non-relational data

✔ Structure:

  • Storage Account → Table → Entity → Properties

✔ Key concepts:

  • Partition Key (grouping & scaling)
  • Row Key (unique identifier)

✔ Benefits:

  • Scalable
  • Fast
  • Cost-effective

✔ Best for:

  • Large datasets with simple access patterns
  • Key-based lookups

✔ Not suitable for:

  • Complex queries or relational workloads

Go to the Practice Exam Questions for this topic.

Go to the DP-900 Exam Prep Hub main page.

Practice Questions: Describe Azure Table storage (DP-900 Exam Prep)

Practice Questions


Question 1

What type of storage is Azure Table Storage?

A. Relational database
B. Object storage
C. NoSQL key-value store
D. Graph database

Answer: C

Explanation:
Azure Table Storage is a NoSQL key-value store designed for structured, non-relational data.


Question 2

Which two properties uniquely identify an entity in Azure Table Storage?

A. Primary Key and Foreign Key
B. Table Name and Column Name
C. Partition Key and Row Key
D. Index and Constraint

Answer: C

Explanation:
Each entity is uniquely identified by a combination of Partition Key and Row Key.


Question 3

What is the purpose of the Partition Key?

A. To encrypt the data
B. To define relationships between tables
C. To group related data and improve scalability
D. To enforce schema rules

Answer: C

Explanation:
The Partition Key determines how data is grouped and distributed for performance.


Question 4

Which statement best describes the schema in Azure Table Storage?

A. All entities must have identical columns
B. A fixed schema is required
C. Entities can have different properties
D. Only numeric data types are supported

Answer: C

Explanation:
Azure Table Storage is schema-less, so entities can have different properties.


Question 5

Which scenario is BEST suited for Azure Table Storage?

A. Running complex SQL joins
B. Storing relational transactional data
C. Storing large volumes of user profile data
D. Hosting a data warehouse

Answer: C

Explanation:
Table Storage is ideal for large-scale, simple, structured data with key-based access.


Question 6

Which operation is most efficient in Azure Table Storage?

A. Joining multiple tables
B. Querying by Partition Key and Row Key
C. Running aggregate functions
D. Performing full table scans

Answer: B

Explanation:
Queries using Partition Key and Row Key are the most efficient.


Question 7

What is an entity in Azure Table Storage?

A. A database
B. A column
C. A row of data
D. A storage account

Answer: C

Explanation:
An entity represents a single record (row) in a table.


Question 8

Which Azure service provides enhanced global distribution and performance compared to Table Storage?

A. Azure Blob Storage
B. Azure Files
C. Azure Cosmos DB (Table API)
D. Azure SQL Database

Answer: C

Explanation:
Azure Cosmos DB offers global distribution, lower latency, and higher SLAs.


Question 9

Which of the following is NOT a characteristic of Azure Table Storage?

A. Schema-less design
B. Key-based access
C. Support for complex joins
D. High scalability

Answer: C

Explanation:
Table Storage does not support joins or complex relational queries.


Question 10

Which hierarchy correctly represents Azure Table Storage?

A. Storage Account → Table → Entity → Properties
B. Table → Entity → Storage Account → Properties
C. Entity → Table → Storage Account → Properties
D. Storage Account → Entity → Table → Properties

Answer: A

Explanation:
The correct structure is Storage Account → Table → Entity → Properties.


✅ Quick Exam Takeaways

✔ Azure Table Storage = NoSQL key-value store
✔ Stores structured, non-relational data

✔ Key concepts:

  • Partition Key → grouping & scalability
  • Row Key → unique identifier

✔ Best for:

  • Large datasets
  • Fast key-based lookups
  • Simple access patterns

✔ Not suitable for:

  • Joins
  • Complex queries
  • Relational workloads

✔ Compare with:

  • Cosmos DB → more advanced, globally distributed

Go to the DP-900 Exam Prep Hub main page.

Describe Azure Blob storage (DP-900 Exam Prep)

This post is a part of the DP-900: Microsoft Azure Data Fundamentals Exam Prep Hub. 
This topic falls under these sections:
Describe considerations for working with non-relational data on Azure (15–20%)
--> Describe capabilities of Azure storage
--> Describe Azure Blob storage


Note that there are 10 practice questions (with answers and explanations) for each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available on the hub below the exam topics section.

Azure Blob Storage is a core Azure service used to store large amounts of unstructured data such as text, images, videos, backups, and logs.

For the DP-900 exam, you should understand what Blob Storage is, how it is structured, and when to use it.


What Is Azure Blob Storage?

Azure Blob Storage is an object storage solution designed for:

  • Massive scalability
  • High durability and availability
  • Storing unstructured data

“Blob” stands for Binary Large Object, meaning it can store virtually any type of file.


Key Characteristics

1. Optimized for Unstructured Data

  • Does not require a predefined schema
  • Supports files such as images, videos, JSON, logs, and backups

2. Massively Scalable

  • Can store petabytes of data
  • Handles high-throughput workloads

3. Highly Durable and Available

  • Data is replicated automatically
  • Supports multiple redundancy options (LRS, GRS, etc.)

4. Cost-Effective Storage

  • Pay only for what you use
  • Multiple storage tiers for cost optimization

Blob Storage Structure

Blob Storage is organized hierarchically:

1. Storage Account

  • Top-level container
  • Required to use Azure storage services

2. Containers

  • Similar to folders
  • Organize blobs into groups

3. Blobs (Objects)

  • Actual data files (e.g., images, documents)

💡 Hierarchy:
Storage Account → Container → Blob


Types of Blobs


1. Block Blobs

  • Store text and binary data
  • Ideal for files, images, and documents

✔ Most commonly used type


2. Append Blobs

  • Optimized for append operations
  • Ideal for logging scenarios

3. Page Blobs

  • Used for random read/write operations
  • Commonly used for virtual machine disks

Access Tiers

Azure Blob Storage offers different tiers based on access frequency:

TierDescriptionUse Case
HotFrequently accessed dataActive applications
CoolInfrequently accessedShort-term backup
ArchiveRarely accessedLong-term storage

✔ Lower cost comes with higher access latency.


Common Use Cases

Azure Blob Storage is used for:

  • Storing images, videos, and documents
  • Backup and disaster recovery
  • Data lakes and analytics workloads
  • Log and telemetry storage
  • Static website hosting

Security Features

Blob Storage includes:

  • Encryption at rest and in transit
  • Role-based access control (RBAC)
  • Shared Access Signatures (SAS)
  • Private endpoints

✔ Ensures secure access to data.


Integration with Azure Services

Blob Storage integrates with:

  • Analytics platforms (e.g., Azure Synapse)
  • Big data processing tools
  • Machine learning workflows
  • Data ingestion pipelines

When to Use Azure Blob Storage

Use Blob Storage when:

  • You need to store unstructured data
  • You require high scalability and durability
  • You want low-cost storage options
  • You are building data lake or analytics solutions

Why This Matters for DP-900

On the exam, you may be asked to:

  • Identify Blob Storage as an object storage service
  • Understand its structure (account → container → blob)
  • Choose it for unstructured data scenarios
  • Recognize storage tiers and use cases

Summary — Exam-Relevant Takeaways

✔ Azure Blob Storage = object storage for unstructured data
✔ Stores files like images, videos, logs, and backups

✔ Structure:

  • Storage Account → Container → Blob

✔ Blob types:

  • Block (most common)
  • Append (logging)
  • Page (VM disks)

✔ Storage tiers:

  • Hot, Cool, Archive

✔ Key benefits:

  • Scalable
  • Durable
  • Cost-effective
  • Secure

Go to the Practice Exam Questions for this topic.

Go to the DP-900 Exam Prep Hub main page.

Describe Azure File storage (DP-900 Exam Prep)

This post is a part of the DP-900: Microsoft Azure Data Fundamentals Exam Prep Hub. 
This topic falls under these sections:
Describe considerations for working with non-relational data on Azure (15–20%)
--> Describe capabilities of Azure storage
--> Describe Azure File storage


Note that there are 10 practice questions (with answers and explanations) for each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available on the hub below the exam topics section.

Azure Files is a cloud-based file storage solution that enables organizations to create shared file systems accessible via standard file protocols.

For the DP-900 exam, you should understand what Azure Files is, how it works, and when to use it compared to other storage options like Blob Storage.


What Is Azure File Storage?

Azure File Storage (Azure Files) is a fully managed file share service that allows you to:

  • Store files in the cloud
  • Access them using familiar file system protocols
  • Share files across multiple machines and applications

It is designed to behave like a traditional network file share, but hosted in Azure.


Key Characteristics


1. File Share Access via SMB and NFS

Azure Files supports:

  • SMB (Server Message Block) → Common in Windows environments
  • NFS (Network File System) → Common in Linux environments

✔ This allows applications to interact with Azure Files just like a local file share.


2. Fully Managed Service (PaaS)

  • No infrastructure to manage
  • Azure handles maintenance, patching, and availability

✔ Simplifies deployment and management.


3. Shared Access Across Multiple Systems

  • Multiple users or applications can access the same files simultaneously
  • Supports cloud and on-premises integration

✔ Ideal for collaboration and shared storage scenarios.


4. Persistent Storage for Applications

  • Maintains data even if applications or VMs restart
  • Commonly used with cloud applications and containers

Azure File Storage Structure

Azure Files is organized as:

  • Storage Account → top-level container
  • File Share → holds directories and files
  • Directories and Files → hierarchical file system

💡 Similar to a traditional file server:

  • File Share = network drive
  • Directories = folders
  • Files = actual data

Common Use Cases

Azure Files is commonly used for:

  • Lift-and-shift file shares to the cloud
  • Shared storage for applications
  • Configuration file storage
  • User home directories
  • Persistent storage for containers (e.g., Kubernetes)

✔ Best when you need file system semantics in the cloud.


Azure File Sync

Azure File Sync extends Azure Files by enabling:

  • Synchronization between on-premises servers and Azure
  • Local caching for faster access
  • Hybrid cloud scenarios

✔ Allows gradual migration to the cloud.


Security Features

Azure Files includes:

  • Encryption at rest and in transit
  • Identity-based authentication (e.g., Active Directory integration)
  • Role-based access control (RBAC)
  • Network restrictions (firewalls, private endpoints)

Performance Tiers

Azure Files offers performance options:

TierDescription
StandardBacked by HDD, cost-effective
PremiumBacked by SSD, high performance

Azure Files vs Azure Blob Storage

Understanding this comparison is important for DP-900:

FeatureAzure FilesAzure Blob Storage
Data TypeFile-basedObject-based
Access MethodSMB / NFSREST API
StructureHierarchical (folders/files)Flat (containers/blobs)
Use CaseFile shares, lift-and-shiftUnstructured data, media, backups

When to Use Azure File Storage

Use Azure Files when:

  • You need a shared file system in the cloud
  • Applications require file system protocols (SMB/NFS)
  • Migrating existing file servers
  • Supporting hybrid environments

Why This Matters for DP-900

On the exam, you may be asked to:

  • Identify Azure Files as a file share service
  • Compare it with Blob Storage
  • Choose the correct storage solution for a scenario
  • Understand protocols like SMB and NFS

Summary — Exam-Relevant Takeaways

✔ Azure Files = managed file share service
✔ Provides cloud-based file system access

✔ Key features:

  • SMB and NFS support
  • Shared access across systems
  • Fully managed (PaaS)
  • Persistent storage

✔ Structure:

  • Storage Account → File Share → Directories → Files

✔ Use cases:

  • File sharing
  • Lift-and-shift migrations
  • Hybrid cloud storage

✔ Key difference:

  • Azure Files = file storage
  • Blob Storage = object storage

Go to the Practice Exam Questions for this topic.

Go to the DP-900 Exam Prep Hub main page.

Practice Questions: Describe Azure File storage (DP-900 Exam Prep)

Practice Questions


Question 1

What is the primary purpose of Azure Files?

A. Store relational data
B. Provide a cloud-based file share
C. Run virtual machines
D. Perform analytics queries

Answer: B

Explanation:
Azure Files provides shared file storage accessible via standard file system protocols.


Question 2

Which protocols are supported by Azure Files?

A. HTTP and HTTPS only
B. SQL and T-SQL
C. SMB and NFS
D. FTP and SMTP

Answer: C

Explanation:
Azure Files supports SMB (Windows) and NFS (Linux) protocols.


Question 3

Which scenario is BEST suited for Azure Files?

A. Storing large video archives for streaming
B. Hosting a NoSQL database
C. Migrating a traditional file server to the cloud
D. Running complex SQL queries

Answer: C

Explanation:
Azure Files is ideal for lift-and-shift file share migrations.


Question 4

How is Azure Files structured?

A. Database → Table → Row
B. Storage Account → Container → Blob
C. Storage Account → File Share → Directory → File
D. Server → Disk → Partition

Answer: C

Explanation:
Azure Files uses a hierarchical structure similar to traditional file systems.


Question 5

Which feature allows synchronization between on-premises file servers and Azure Files?

A. Azure Blob Sync
B. Azure File Sync
C. Azure Data Factory
D. Azure Backup Vault

Answer: B

Explanation:
Azure File Sync enables hybrid scenarios and local caching.


Question 6

Which type of storage is Azure Files considered?

A. Object storage
B. File storage
C. Key-value storage
D. Graph storage

Answer: B

Explanation:
Azure Files is a file-based storage service.


Question 7

Which Azure Files tier provides high-performance storage using SSDs?

A. Archive
B. Cool
C. Standard
D. Premium

Answer: D

Explanation:
Premium tier uses SSDs for higher performance.


Question 8

Which statement best describes Azure Files compared to Azure Blob Storage?

A. Azure Files is used only for structured data
B. Azure Files uses file system protocols like SMB
C. Azure Files cannot be accessed from on-premises systems
D. Azure Files requires a predefined schema

Answer: B

Explanation:
Azure Files supports file system protocols, unlike Blob Storage which uses REST APIs.


Question 9

Which feature ensures that Azure Files data remains available even if a virtual machine restarts?

A. Ephemeral storage
B. Persistent storage
C. Temporary storage
D. Local disk storage

Answer: B

Explanation:
Azure Files provides persistent storage independent of compute resources.


Question 10

Which scenario would NOT be appropriate for Azure Files?

A. Sharing configuration files across applications
B. Hosting a shared drive for users
C. Storing large unstructured data for analytics
D. Migrating on-premises file shares

Answer: C

Explanation:
Large-scale unstructured analytics data is better suited for Azure Blob Storage or Data Lake, not Azure Files.


✅ Quick Exam Takeaways

✔ Azure Files = cloud-based file share service
✔ Supports SMB and NFS protocols

✔ Structure:

  • Storage Account → File Share → Directory → File

✔ Key features:

  • Shared access
  • Persistent storage
  • Hybrid support (Azure File Sync)
  • Fully managed

✔ Tiers:

  • Standard (HDD)
  • Premium (SSD)

✔ Best for:

  • File shares
  • Lift-and-shift migrations
  • Shared application storage

Go to the DP-900 Exam Prep Hub main page.

Practice Questions: Describe Azure Blob storage (DP-900 Exam Prep)

Practice Questions


Question 1

What type of data is best suited for Azure Blob Storage?

A. Highly structured relational data
B. Unstructured data such as images and videos
C. Data requiring complex joins
D. Transactional financial records

Answer: B

Explanation:
Blob Storage is optimized for unstructured data like media files, documents, and logs.


Question 2

What is the correct hierarchy in Azure Blob Storage?

A. Blob → Container → Storage Account
B. Container → Blob → Storage Account
C. Storage Account → Container → Blob
D. Storage Account → Blob → Container

Answer: C

Explanation:
The hierarchy is Storage Account → Container → Blob.


Question 3

Which type of blob is BEST suited for storing log files that are continuously appended?

A. Block blob
B. Page blob
C. Append blob
D. Archive blob

Answer: C

Explanation:
Append blobs are optimized for append operations, such as logging.


Question 4

Which access tier is MOST cost-effective for data that is rarely accessed?

A. Hot
B. Cool
C. Archive
D. Premium

Answer: C

Explanation:
The Archive tier is designed for rarely accessed data at the lowest cost.


Question 5

Which Blob Storage feature ensures data is replicated to improve durability?

A. Indexing
B. Data redundancy options
C. Query optimization
D. Schema enforcement

Answer: B

Explanation:
Blob Storage uses redundancy options (e.g., LRS, GRS) to ensure durability.


Question 6

Which blob type is typically used for storing virtual machine disks?

A. Block blob
B. Append blob
C. Page blob
D. Archive blob

Answer: C

Explanation:
Page blobs support random read/write operations and are used for VM disks.


Question 7

Which scenario is BEST suited for Azure Blob Storage?

A. Running complex SQL queries
B. Storing large volumes of images for a website
C. Managing transactional order data
D. Performing real-time analytics

Answer: B

Explanation:
Blob Storage is ideal for storing large volumes of unstructured data like images.


Question 8

What is a container in Azure Blob Storage?

A. A type of blob
B. A virtual machine
C. A logical grouping of blobs
D. A database schema

Answer: C

Explanation:
Containers are used to organize blobs, similar to folders.


Question 9

Which feature allows secure, temporary access to Blob Storage resources?

A. SQL authentication
B. Shared Access Signature (SAS)
C. Primary key constraint
D. Indexing

Answer: B

Explanation:
SAS tokens provide secure, time-limited access to storage resources.


Question 10

Which statement best describes Azure Blob Storage?

A. It requires a predefined schema
B. It is used only for relational data
C. It is an object storage solution for unstructured data
D. It is a transactional database system

Answer: C

Explanation:
Blob Storage is an object storage service designed for unstructured data.


✅ Quick Exam Takeaways

✔ Blob Storage = unstructured/object storage
✔ Structure:

  • Storage Account → Container → Blob

✔ Blob types:

  • Block → general files
  • Append → logs
  • Page → VM disks

✔ Access tiers:

  • Hot (frequent access)
  • Cool (infrequent)
  • Archive (rare)

✔ Key features:

  • Scalable
  • Durable (replication)
  • Secure (SAS, RBAC)
  • Cost-optimized

Go to the DP-900 Exam Prep Hub main page.

Identify Azure Database Services for open-source database systems (DP-900 Exam Prep)

This post is a part of the DP-900: Microsoft Azure Data Fundamentals Exam Prep Hub. 
This topic falls under these sections:
Identify considerations for relational data on Azure (20–25%)
--> Describe relational Azure data services
--> Identify Azure database services for open-source database systems


Note that there are 10 practice questions (with answers and explanations) for each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available on the hub below the exam topics section.

In addition to the Azure SQL family, Microsoft Azure provides fully managed database services for popular open-source relational database systems. These services allow organizations to run familiar technologies like PostgreSQL and MySQL in the cloud without managing infrastructure.

For the DP-900 exam, you should understand which services are available, what they support, and when to use them.


What Are Open-Source Database Systems?

Open-source database systems are relational databases whose source code is publicly available and widely used across industries.

Common examples include:

  • PostgreSQL
  • MySQL
  • MariaDB

These systems are known for flexibility, cost-effectiveness, and strong community support.


Azure Services for Open-Source Databases

Azure offers managed services for these databases, allowing you to run them in a Platform as a Service (PaaS) model.


1. Azure Database for PostgreSQL

Azure Database for PostgreSQL

A fully managed PostgreSQL database service.

Key Features

  • Automated backups and patching
  • Built-in high availability
  • Scaling options for compute and storage
  • Security features (encryption, network isolation)
  • Support for PostgreSQL extensions

Deployment Options

  • Flexible Server (most commonly used)

Use Cases

  • Web and mobile applications
  • Analytics workloads
  • Applications already using PostgreSQL

Best for: PostgreSQL-based applications moving to Azure


2. Azure Database for MySQL

Azure Database for MySQL

A fully managed MySQL database service.

Key Features

  • Automated backups and patching
  • High availability options
  • Scaling for performance
  • Built-in security features
  • Compatible with popular MySQL tools

Use Cases

  • Web applications (e.g., LAMP stack)
  • E-commerce platforms
  • Content management systems

Best for: Applications built on MySQL


3. Azure Database for MariaDB (Legacy Note)

Azure Database for MariaDB

  • Previously offered as a managed service
  • Now being retired (important exam awareness point)

💡 DP-900 Tip:
Know that MariaDB exists, but focus primarily on PostgreSQL and MySQL.


Key Characteristics of Azure Open-Source Database Services

These services share common benefits:

Platform as a Service (PaaS)

  • No infrastructure management
  • Azure handles patching, backups, and updates

High Availability

  • Built-in redundancy
  • Automatic failover options

Scalability

  • Scale compute and storage independently

Security

  • Encryption at rest and in transit
  • Network security (firewalls, private endpoints)

When to Use Open-Source Database Services in Azure

Choose these services when:

  • You are already using PostgreSQL or MySQL
  • You want to migrate existing applications with minimal changes
  • You prefer open-source technologies
  • You want a managed service without infrastructure overhead

Comparison with Azure SQL Family

FeatureAzure SQL ServicesOpen-Source Azure Services
Database EngineSQL ServerPostgreSQL / MySQL
LanguageT-SQLPostgreSQL SQL / MySQL SQL
Use CaseMicrosoft ecosystemOpen-source ecosystem
ManagementPaaS / IaaS optionsPrimarily PaaS

Why This Matters for DP-900

On the exam, you may be asked to:

  • Identify Azure services for PostgreSQL or MySQL
  • Choose the correct service for an open-source workload
  • Understand the benefits of managed database services
  • Compare Azure SQL vs open-source options

Summary — Exam-Relevant Takeaways

✔ Azure supports open-source relational databases:

  • Azure Database for PostgreSQL
  • Azure Database for MySQL

✔ These are PaaS services:

  • Azure manages infrastructure, backups, and patching

✔ Key benefits:

  • High availability
  • Scalability
  • Security

✔ Use them when:

  • Migrating existing open-source applications
  • Building apps using PostgreSQL or MySQL

✔ Be aware:

  • MariaDB support exists but is being phased out

Go to the Practice Exam Questions for this topic.

Go to the DP-900 Exam Prep Hub main page.

Practice Questions: Identify Azure Database Services for open-source database systems (DP-900 Exam Prep)

Practice Questions


Question 1

Which Azure service is used to host a managed PostgreSQL database?

A. Azure SQL Database
B. Azure Database for PostgreSQL
C. Azure Cosmos DB
D. Azure Synapse Analytics

Answer: B

Explanation:
Azure Database for PostgreSQL is the managed service for PostgreSQL workloads.


Question 2

Which Azure service is BEST suited for hosting a MySQL-based web application?

A. Azure SQL Managed Instance
B. Azure Database for MySQL
C. Azure Data Lake Storage
D. Azure Blob Storage

Answer: B

Explanation:
Azure Database for MySQL is designed for MySQL workloads, commonly used in web apps.


Question 3

What type of service are Azure Database for PostgreSQL and Azure Database for MySQL?

A. Infrastructure as a Service (IaaS)
B. Platform as a Service (PaaS)
C. Software as a Service (SaaS)
D. On-premises solutions

Answer: B

Explanation:
These services are PaaS offerings, meaning Azure manages infrastructure and maintenance.


Question 4

Which task is handled by Azure in open-source database PaaS services?

A. Writing SQL queries
B. Managing application code
C. Performing backups and patching
D. Designing database schema

Answer: C

Explanation:
Azure handles operational tasks like backups, patching, and updates.


Question 5

Which scenario is BEST suited for Azure Database for PostgreSQL?

A. Running a NoSQL database
B. Migrating an existing PostgreSQL application to Azure
C. Storing unstructured files
D. Running machine learning models

Answer: B

Explanation:
This service is ideal for migrating or running PostgreSQL workloads in Azure.


Question 6

Which of the following is an open-source relational database supported by Azure?

A. Microsoft SQL Server
B. Oracle Database
C. PostgreSQL
D. Azure Cosmos DB

Answer: C

Explanation:
PostgreSQL is a widely used open-source relational database supported by Azure.


Question 7

Which Azure database service for open-source systems is being retired?

A. Azure Database for PostgreSQL
B. Azure Database for MySQL
C. Azure Database for MariaDB
D. Azure SQL Database

Answer: C

Explanation:
Azure Database for MariaDB is being phased out.


Question 8

Which feature is commonly provided by Azure open-source database services?

A. Manual scaling only
B. No security features
C. Built-in high availability
D. No backup support

Answer: C

Explanation:
These services include built-in high availability and redundancy.


Question 9

Which is a key benefit of using Azure Database for MySQL instead of installing MySQL on a VM?

A. Full OS control
B. Reduced management overhead
C. No support for scaling
D. Limited security features

Answer: B

Explanation:
PaaS reduces administrative tasks like maintenance and patching.


Question 10

Which factor is MOST important when choosing Azure Database for PostgreSQL or MySQL?

A. Whether the data is unstructured
B. The need for OS-level access
C. The existing database engine used by the application
D. The need for NoSQL capabilities

Answer: C

Explanation:
Choice is typically driven by the database engine already used (PostgreSQL vs MySQL).


✅ Quick Exam Takeaways

Azure Database for PostgreSQL → PostgreSQL workloads
Azure Database for MySQL → MySQL workloads
✔ Both are PaaS services (Azure manages infrastructure)

✔ Key benefits:

  • Automated backups
  • Patching and updates
  • High availability
  • Scalability

✔ Use when:

  • Migrating open-source databases
  • Building apps on PostgreSQL or MySQL

✔ Be aware:

  • MariaDB is being retired

Go to the DP-900 Exam Prep Hub main page.

Identify common database objects (DP-900 Exam Prep)

This post is a part of the DP-900: Microsoft Azure Data Fundamentals Exam Prep Hub. 
This topic falls under these sections:
Identify considerations for relational data on Azure (20–25%)
--> Describe relational concepts
--> Identify common database objects


Note that there are 10 practice questions (with answers and explanations) for each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available on the hub below the exam topics section.

Relational databases are composed of several key database objects that define how data is stored, accessed, secured, and optimized. For the DP-900 exam, you should understand the purpose of these objects and how they support relational data systems.


What Are Database Objects?

Database objects are logical structures within a database used to:

  • Store data
  • Organize data
  • Enforce rules
  • Improve performance
  • Control access

They are created and managed using Structured Query Language (SQL).


Core Database Objects You Need to Know


1. Tables

A table is the primary object used to store data.

  • Organized into rows (records) and columns (fields)
  • Each table represents an entity (e.g., Customers, Orders)
  • Data is physically stored in tables

Example:

CustomerIDNameCity
1JohnSeattle

✔ Tables are the foundation of relational databases.


2. Views

A view is a virtual table based on a SQL query.

  • Does not store data physically (in most cases)
  • Displays data from one or more tables
  • Simplifies complex queries
  • Can restrict access to sensitive data

Example Use Case:

  • Show only customer names and cities, hiding confidential columns

✔ Views provide abstraction and security.


3. Indexes

An index is used to improve query performance.

  • Speeds up data retrieval
  • Works like an index in a book
  • Created on one or more columns
  • Improves SELECT performance but may slightly slow writes

Example:

  • Index on CustomerID for fast lookups

✔ Indexes are critical for performance optimization.


4. Stored Procedures

A stored procedure is a saved collection of SQL statements.

  • Stored and executed in the database
  • Can accept parameters
  • Can include logic (conditions, loops)
  • Improves performance and reusability

Example Use Case:

  • Retrieve all orders for a specific customer

✔ Stored procedures enable automation and reusable logic.


5. Schemas

A schema is a logical container for database objects.

  • Organizes tables, views, and other objects
  • Helps manage permissions
  • Improves structure and maintainability

Example:

  • Sales.Customers
  • HR.Employees

✔ Schemas help with organization and security management.


6. Keys

Keys define relationships and ensure data uniqueness.

Primary Key

  • Uniquely identifies each row
  • Cannot contain NULL values

Foreign Key

  • Links one table to another
  • Enforces referential integrity

✔ Keys are essential for relationships and data integrity.


7. Constraints

Constraints enforce rules on data to maintain accuracy.

Common constraints include:

  • PRIMARY KEY → unique identifier
  • FOREIGN KEY → enforces relationships
  • NOT NULL → requires a value
  • UNIQUE → prevents duplicates
  • CHECK → enforces conditions

✔ Constraints ensure data validity and consistency.


How These Objects Work Together

In a typical relational database:

  • Tables store the data
  • Keys and constraints enforce rules
  • Indexes improve performance
  • Views simplify access
  • Stored procedures automate operations
  • Schemas organize everything

Database Objects in Azure

These objects are used in Azure relational services such as:

  • Azure SQL Database
  • Azure Database for PostgreSQL
  • Azure Database for MySQL

These platforms support standard SQL-based database objects and functionality.


Why This Matters for DP-900

On the exam, you may be asked to:

  • Identify different database objects
  • Match objects to their purpose
  • Distinguish between tables, views, and indexes
  • Understand how objects support performance, security, and organization

Summary — Exam-Relevant Takeaways

Tables → store data
Views → virtual representation of data
Indexes → improve query performance
Stored procedures → reusable SQL logic
Schemas → organize objects
Keys → define relationships
Constraints → enforce data rules

✔ Together, these objects ensure:

  • Efficient data storage
  • Fast data retrieval
  • Strong data integrity
  • Secure and organized systems

Go to the Practice Exam Questions for this topic.

Go to the DP-900 Exam Prep Hub main page.