Start today's 10-question DP-900 set with source-backed explanations, local progress, and a fresh rotation every morning.
Microsoft Azure Data Fundamentals
Get 150 verified questions, every choice explained, Exam Mode, Practice Mode, random tests, readiness tracking, previous scores, and no ads.
Secure checkout by Stripe. Instant unlock on this page. No subscription.
Choose an unlock option to continue. We will confirm your site email in one quick checkout step.
Use this DP-900 practice test to review Microsoft Azure Data Fundamentals. Questions rotate daily and each explanation links to the source used to validate the answer.
150 verified questions are in the live bank. Free daily questions are selected from a rotating sample set. Unlock Pro to access the full question bank.
Azure Blob Storage is the ideal choice for storing unstructured data like photos and videos. It's designed for massive scalability, cost-effective storage of large binary files, and efficient content delivery through Azure CDN. Blob Storage offers different tiers (Hot, Cool, Archive) to optimize costs based on access frequency. The other options are unsuitable: Azure SQL Database is for relational data, Azure Cosmos DB is for NoSQL document databases requiring complex querying, and Azure Table Storage is for structured, semi-structured data and is not optimized for large binary files.
This scenario demands ACID (Atomicity, Consistency, Isolation, Durability) properties to ensure data integrity and prevent data loss during system failures, which is a hallmark of Online Transaction Processing (OLTP). Azure SQL Database is a fully managed relational database service that excels at handling these types of workloads. Relational databases enforce relationships between data, ensuring consistency, and provide mechanisms like transactions to guarantee data integrity. The requirement for real-time processing and guaranteed completion makes a relational database the ideal choice.
Azure Time Series Insights (Gen2) is specifically designed for ingesting, storing, and analyzing time-series data. It provides built-in capabilities for data aggregation, anomaly detection, and querying data based on time ranges, making it ideal for IoT telemetry workloads. The service automatically handles partitioning and indexing for efficient time-based queries. While other options can store data, they lack the specialized features and optimizations for time-series analysis that Time Series Insights offers. This service is optimized for this exact scenario, providing a managed solution for complex time-series workloads.
The most appropriate structure is two tables: one for account information and another for transaction details. This approach separates the account data from the transaction data, which is a common and efficient practice. The account table stores static account information, while the transaction table stores the dynamic transaction records. The foreign key relationship between the tables allows for efficient querying of transactions associated with specific accounts. This design balances data organization, query performance, and maintainability, which are crucial for a banking ledger application handling high transaction volumes. A single table would lead to performance issues with large datasets. Three tables would add unnecessary complexity for this relatively simple relationship. An aggregated table would lose the granularity of individual transactions.
The Hot tier is the correct choice for frequently accessed data. It offers the lowest latency and highest throughput, making it ideal for active user file downloads. The Hot tier is designed for data that is accessed frequently and is the most expensive access tier. Archive tier is for infrequently accessed data, Cool tier is for data accessed less frequently than Hot but more frequently than Archive, and Premium tier is for block blob storage that requires high performance and low latency for write operations, which isn't the primary requirement here.
A self-referencing table is the most appropriate solution for representing hierarchical data like an organizational structure. This design allows each employee record to directly link to their manager's record within the same table, creating a chain of reporting relationships. This structure is efficient for traversing the hierarchy and generating organizational charts. The recursive nature inherently supports multiple levels of management. The other options are less efficient or flexible for this specific scenario. Option 1 would be difficult to query for deep reporting lines. Option 2 introduces unnecessary complexity and joins. Option 4, while flexible, would be less performant for querying and reporting on the hierarchy.
Azure Cosmos DB for NoSQL (Key-value) is the optimal choice because it's designed for flexible schema and fast key-based lookups. The key-value model allows each product to have its own unique key (product ID) and a document containing its attributes. Changes to a product's attributes can be made directly without impacting other products, and the service provides low-latency reads and writes. Azure SQL Database is relational and requires a predefined schema, making it less flexible for frequently changing attributes. Azure Blob Storage is for storing unstructured data like images or videos, not structured configuration data. Azure Table Storage is a NoSQL option, but it has limitations in querying and schema flexibility compared to Cosmos DB, making it less ideal for this scenario.
The ACID properties are fundamental to database transactions. Durability specifically ensures that once a transaction is committed, the changes are permanent and survive even system failures like power outages. The database system will employ mechanisms like transaction logs and redundant storage to guarantee this. Atomicity ensures all parts of a transaction succeed or fail as a single unit. Consistency ensures data adheres to defined rules and constraints. Isolation prevents interference between concurrent transactions. In this scenario, the key concern is data persistence after a crash, which is directly addressed by the durability property.
JSON (JavaScript Object Notation) is the most appropriate choice for this scenario. JSON's flexible, schema-less nature allows for easy addition of new attributes to click events without requiring schema migrations. This aligns perfectly with the team's requirement for adaptability. Furthermore, Azure data services like Azure Data Lake Storage Gen2 and Azure Cosmos DB offer excellent support for querying JSON documents, enabling efficient analysis based on various combinations of attributes. While XML is also semi-structured, JSON is generally preferred for its simpler syntax and broader adoption in modern web applications. CSV and TSV are structured formats and lack the flexibility needed to accommodate evolving data attributes.
Azure SQL Database Point-in-Time Restore allows you to restore your database to a specific point in time, effectively recreating its state as it existed at that moment. This is crucial for auditing, data recovery, and ensuring data consistency after unexpected events. Elastic Pools manage resource allocation across databases, Geo-Replication provides disaster recovery and read-scale capabilities, and Transparent Data Encryption protects data at rest but doesn't provide point-in-time recovery. Therefore, Point-in-Time Restore is the only option that directly addresses the requirement of recreating a database's state at a specific time.
Unlock the full 150-question bank to keep practicing now.
Best if you only need this one certification and want the lower fundamentals price.
A 50-question DP-900 PDF for short review sessions. Questions come first, then the answer review and explanations later in the file.
Unlock Microsoft, Azure, Power Platform, Copilot, and AI practice exams.
We will ask for your site email in a quick checkout step, remember it on this browser, and use it again for restore.
Use the same email for checkout, restore, and the dashboard on this browser.
Your selected purchase will stay attached while you confirm the checkout email.
Choose an unlock option to continue. We will confirm your site email in one quick checkout step.
Choose the question count, question set, session mode, and timer for your full-bank practice.
Set a target once. We will keep the next study action visible before every Pro session.
Start Exam Mode or Practice Mode to build your readiness trend on this browser.
Box scores, domain breakdowns, and full answer explanations for Pro exam attempts on this browser.
Get the full bank, Exam Mode, Practice Mode, question sets, random tests, readiness tracking, saved box scores, and review tools for this exam.
The PDF versions keep questions first and move the answer review, explanations, and distractor notes to the back of the file.
You've answered 0/10 questions in today's set.
Locked: 140 more questions in the full bank.
Locked: exam simulation mode, practice mode, readiness tracking, and saved review history.
Checkout stays on this page, so you can keep practicing, unlock the full bank, and start Exam Mode or Practice Mode when you are ready.
Answer questions today and this will become a rolling 7-day scorecard.
Guest progress saves automatically on this device. Add an email later when you want a magic link that keeps your daily DP-900 practice in sync across browsers.
Guest progress saves on this device automatically
Use these official Microsoft resources alongside the daily practice set. They cover the provider's own exam page, study guide, or prep material.
Need adjacent Microsoft practice pages too? Microsoft practice hub.
The free daily DP-900 set includes crawlable question text, answer choices, the correct answer explanation, wrong-answer distractor explanations when the reviewed bank provides them, objective mapping, and source links. Pro-only bank questions stay locked; this section mirrors only the 10 free daily questions already shown on this page.
Azure Blob Storage
Azure Blob Storage is the ideal choice for storing unstructured data like photos and videos. It's designed for massive scalability, cost-effective storage of large binary files, and efficient content delivery through Azure CDN. Blob Storage offers different tiers (Hot, Cool, Archive) to optimize costs based on access frequency. The other options are unsuitable: Azure SQL Database is for relational data, Azure Cosmos DB is for NoSQL document databases requiring complex querying, and Azure Table Storage is for structured, semi-structured data and is not optimized for large binary files.
A relational database workload (OLTP) utilizing Azure SQL Database.
This scenario demands ACID (Atomicity, Consistency, Isolation, Durability) properties to ensure data integrity and prevent data loss during system failures, which is a hallmark of Online Transaction Processing (OLTP). Azure SQL Database is a fully managed relational database service that excels at handling these types of workloads. Relational databases enforce relationships between data, ensuring consistency, and provide mechanisms like transactions to guarantee data integrity. The requirement for real-time processing and guaranteed completion makes a relational database the ideal choice.
Azure Time Series Insights (Gen2)
Azure Time Series Insights (Gen2) is specifically designed for ingesting, storing, and analyzing time-series data. It provides built-in capabilities for data aggregation, anomaly detection, and querying data based on time ranges, making it ideal for IoT telemetry workloads. The service automatically handles partitioning and indexing for efficient time-based queries. While other options can store data, they lack the specialized features and optimizations for time-series analysis that Time Series Insights offers. This service is optimized for this exact scenario, providing a managed solution for complex time-series workloads.
Two tables: one for account information (account ID, account type, balance) and another for transaction details (transaction ID, account ID, date, time, type, amount).
The most appropriate structure is two tables: one for account information and another for transaction details. This approach separates the account data from the transaction data, which is a common and efficient practice. The account table stores static account information, while the transaction table stores the dynamic transaction records. The foreign key relationship between the tables allows for efficient querying of transactions associated with specific accounts. This design balances data organization, query performance, and maintainability, which are crucial for a banking ledger application handling high transaction volumes. A single table would lead to performance issues with large datasets. Three tables would add unnecessary complexity for this relatively simple relationship. An aggregated table would lose the granularity of individual transactions.
Hot tier
The Hot tier is the correct choice for frequently accessed data. It offers the lowest latency and highest throughput, making it ideal for active user file downloads. The Hot tier is designed for data that is accessed frequently and is the most expensive access tier. Archive tier is for infrequently accessed data, Cool tier is for data accessed less frequently than Hot but more frequently than Archive, and Premium tier is for block blob storage that requires high performance and low latency for write operations, which isn't the primary requirement here.
Create a recursive table with a self-referencing foreign key, where each employee record includes a 'managerEmployeeID' column referencing another employee record within the same table.
A self-referencing table is the most appropriate solution for representing hierarchical data like an organizational structure. This design allows each employee record to directly link to their manager's record within the same table, creating a chain of reporting relationships. This structure is efficient for traversing the hierarchy and generating organizational charts. The recursive nature inherently supports multiple levels of management. The other options are less efficient or flexible for this specific scenario. Option 1 would be difficult to query for deep reporting lines. Option 2 introduces unnecessary complexity and joins. Option 4, while flexible, would be less performant for querying and reporting on the hierarchy.
Azure Cosmos DB for NoSQL (Key-value)
Azure Cosmos DB for NoSQL (Key-value) is the optimal choice because it's designed for flexible schema and fast key-based lookups. The key-value model allows each product to have its own unique key (product ID) and a document containing its attributes. Changes to a product's attributes can be made directly without impacting other products, and the service provides low-latency reads and writes. Azure SQL Database is relational and requires a predefined schema, making it less flexible for frequently changing attributes. Azure Blob Storage is for storing unstructured data like images or videos, not structured configuration data. Azure Table Storage is a NoSQL option, but it has limitations in querying and schema flexibility compared to Cosmos DB, making it less ideal for this scenario.
Durability
The ACID properties are fundamental to database transactions. Durability specifically ensures that once a transaction is committed, the changes are permanent and survive even system failures like power outages. The database system will employ mechanisms like transaction logs and redundant storage to guarantee this. Atomicity ensures all parts of a transaction succeed or fail as a single unit. Consistency ensures data adheres to defined rules and constraints. Isolation prevents interference between concurrent transactions. In this scenario, the key concern is data persistence after a crash, which is directly addressed by the durability property.
JavaScript Object Notation (JSON)
JSON (JavaScript Object Notation) is the most appropriate choice for this scenario. JSON's flexible, schema-less nature allows for easy addition of new attributes to click events without requiring schema migrations. This aligns perfectly with the team's requirement for adaptability. Furthermore, Azure data services like Azure Data Lake Storage Gen2 and Azure Cosmos DB offer excellent support for querying JSON documents, enabling efficient analysis based on various combinations of attributes. While XML is also semi-structured, JSON is generally preferred for its simpler syntax and broader adoption in modern web applications. CSV and TSV are structured formats and lack the flexibility needed to accommodate evolving data attributes.
Azure SQL Database Point-in-Time Restore
Azure SQL Database Point-in-Time Restore allows you to restore your database to a specific point in time, effectively recreating its state as it existed at that moment. This is crucial for auditing, data recovery, and ensuring data consistency after unexpected events. Elastic Pools manage resource allocation across databases, Geo-Replication provides disaster recovery and read-scale capabilities, and Transparent Data Encryption protects data at rest but doesn't provide point-in-time recovery. Therefore, Point-in-Time Restore is the only option that directly addresses the requirement of recreating a database's state at a specific time.
dotCreds builds DP-900 practice questions from public exam objectives and Microsoft Learn and exam-objective references. The questions are written for realistic study practice, not copied from exam dumps.
Each question includes an explanation and, when available, a source link back to the provider documentation or reference used to validate the answer. That keeps the practice tied to study material you can actually review.
The page tracks today's answered count and accuracy for the 10-question daily set, then saves a 7-day score history on this device so you can see your recent practice trend.
The site is the fastest way to start DP-900 practice without installing anything. It is built for daily recall, quick weak-topic discovery, and source-backed explanations you can review immediately.
The web page is the quick daily practice layer. If a dotCreds app is available for DP-900, the app is better for larger banks, focused weak-domain drills, longer review sessions, and mobile study routines.
Unlock the full 150-question bank, Exam Mode, Practice Mode, random tests, readiness tracking, previous scores, and no ads.
Secure Stripe checkout opens next using the site email already entered above.
Flexible search understands AI-901, ai901, ai 901, 901, ai, network plus, and saa c03.