cert
cert-1
cert-2

Pass Microsoft DP-900 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
DP-900 Exam - Verified By Experts
DP-900 Premium Bundle
$29.98

DP-900 Premium Bundle

$79.99
$109.97
  • Premium File 332 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 32 Video Lectures
  • Study Guide 672 Pages
 
$109.97
$79.99
accept 21 downloads in last 7 days
block-screenshots
Purchase Microsoft DP-900 Exam Training Products Individually
Microsoft DP-900 Premium File
Premium File 332 Q&A
$76.99$69.99
Microsoft DP-900 Video Training Course
Training Course 32 Lectures
$21.99 $19.99
Microsoft DP-900 PDF Study Guide
Study Guide 672 Pages
$21.99 $19.99
Microsoft DP-900 Practice Test 46

Question 450

Developers want to understand why cross-partition reads cost more than ID point reads. Which principle BEST explains the correct Cosmos DB Request Unit RU accounting design decision?

  1. Cosmos DB measures resource consumption in request units rather than only raw data size.
  2. Cosmos DB consistency levels trade freshness availability latency and throughput.
  3. Azure Storage services expose distinct data models even within one storage account.
  4. Versioning retains historical object states independently of overwriting current contents.

Explanation

Correct Answer

A:

Cosmos DB measures resource consumption in request units rather than only raw data size. In this case the applicable decision is to measure and budget provisioned or consumed request units for actual Cosmos operations.

Incorrect Answers

B:

Cosmos DB consistency levels trade freshness availability latency and throughput. That concept explains Cosmos DB consistency choices; the situation instead concerns Cosmos DB Request Unit RU accounting. Treating every query as equal-cost can overload provisioned throughput.

C:

Azure Storage services expose distinct data models even within one storage account. That concept explains Choosing Blob Files and Table for app needs; the situation instead concerns Cosmos DB Request Unit RU accounting. Treating every query as equal-cost can overload provisioned throughput.

D:

Versioning retains historical object states independently of overwriting current contents. That concept explains Blob versioning on overwrite; the situation instead concerns Cosmos DB Request Unit RU accounting. Treating every query as equal-cost can overload provisioned throughput.

Question 451

A retailer compares revenue across ten product families. If the relevant Column chart category comparison safeguard is skipped, which failure is MOST directly associated with that omission?

  1. Dropping raw inputs before validating transforms harms reproducibility.
  2. A line chart with arbitrary category connections may imply continuity.
  3. Grouping only by arrival time can put delayed events in the wrong period.
  4. Hard-coded manually copied totals become stale when filters change.

Explanation

Correct Answer

B:

A line chart with arbitrary category connections may imply continuity. Bar and column charts support comparisons across discrete categories. A suitable check is to check zero baselines and sort order for fairness.

Incorrect Answers

A:

Dropping raw inputs before validating transforms harms reproducibility. This failure is associated with ELT warehouse pushdown transforms; it is not the primary failure in the stated Column chart category comparison scenario. Bar and column charts support comparisons across discrete categories.

C:

Grouping only by arrival time can put delayed events in the wrong period. This failure is associated with Event time versus processing time; it is not the primary failure in the stated Column chart category comparison scenario. Bar and column charts support comparisons across discrete categories.

D:

Hard-coded manually copied totals become stale when filters change. This failure is associated with Power BI semantic model measures; it is not the primary failure in the stated Column chart category comparison scenario. Bar and column charts support comparisons across discrete categories.

Question 452

A report must let users explore category and region filters. What is the MOST appropriate next validation or correction?

  1. Inspect schema definitions and sample failed inserts against business requirements.
  2. Test dashboard comprehension using business questions.
  3. Verify drill-down totals against known granular records.
  4. Replace row-level data with one grand total and claim drill-down remains supported.

Explanation

Correct Answer

C:

Verify drill-down totals against known granular records. This tests the intended result: users move from aggregate to detail with correct filter behavior.

Incorrect Answers

A:

Inspect schema definitions and sample failed inserts against business requirements. It tests Structured records in a customer table rather than the critical Data analyst slicing and drill-down behavior. Drill-down and slicing reveal patterns across levels of analysis.

B:

Test dashboard comprehension using business questions. It tests Data analyst report design rather than the critical Data analyst slicing and drill-down behavior. Drill-down and slicing reveal patterns across levels of analysis.

D:

Replace row-level data with one grand total and claim drill-down remains supported. This unsafe shortcut leaves the Data analyst slicing and drill-down problem unresolved. Mixing different grains can double-count measures.

Question 453

An operator must find orders with status Shipped and amount above a threshold. What is the MOST appropriate next validation or correction?

  1. Inspect pages with identical timestamps and stable IDs.
  2. Sort by year and claim sorting is equivalent to a WHERE filter.
  3. Inventory SQL Agent jobs linked servers and supported features before migration.
  4. Check representative boundary values and query results.

Explanation

Correct Answer

D:

Check representative boundary values and query results. This tests the intended result: output contains only rows meeting every specified filter condition.

Incorrect Answers

A:

Inspect pages with identical timestamps and stable IDs. It tests SQL ORDER BY pagination stability rather than the critical SQL SELECT filtering WHERE behavior. WHERE restricts rows before grouping in a SQL query.

B:

Sort by year and claim sorting is equivalent to a WHERE filter. This unsafe shortcut leaves the SQL SELECT filtering WHERE problem unresolved. Missing a predicate may expose unrelated rows or inflate results.

C:

Inventory SQL Agent jobs linked servers and supported features before migration. It tests Azure SQL Managed Instance compatibility rather than the critical SQL SELECT filtering WHERE behavior. WHERE restricts rows before grouping in a SQL query.

Question 454

A travel app must decide what happens if writes conflict across distributed sites. Which principle BEST explains the correct Cosmos DB multi-region writes conflict handling design decision?

  1. Azure Table Storage supports nonrelational wide entities beyond fixed SQL columns.
  2. Immutability protects retained objects through enforceable storage policy.
  3. Multiple write regions add concurrency and conflict resolution concerns.
  4. Change feeds support incremental change-driven processing with defined change semantics.

Explanation

Correct Answer

C:

Multiple write regions add concurrency and conflict resolution concerns. In this case the applicable decision is to evaluate multi-region writes with a deliberate conflict resolution policy.

Incorrect Answers

A:

Azure Table Storage supports nonrelational wide entities beyond fixed SQL columns. That concept explains Table Storage schemaless properties; the situation instead concerns Cosmos DB multi-region writes conflict handling. Assuming global writes automatically merge arbitrary business transactions may lose updates.

B:

Immutability protects retained objects through enforceable storage policy. That concept explains Immutable blob retention and legal hold; the situation instead concerns Cosmos DB multi-region writes conflict handling. Assuming global writes automatically merge arbitrary business transactions may lose updates.

D:

Change feeds support incremental change-driven processing with defined change semantics. That concept explains Cosmos DB change feed updates; the situation instead concerns Cosmos DB multi-region writes conflict handling. Assuming global writes automatically merge arbitrary business transactions may lose updates.

Question 455

A team must use unsupported-by-PaaS instance extensions in a cloud-hosted SQL engine. During testing, the team observes this specific failure: Treating a VM as fully managed PaaS can leave guest patching unattended. Which corrective check should be performed FIRST?

  1. Use GROUP BY then HAVING to filter aggregate group results.
  2. Evaluate Azure SQL Managed Instance for compatible lift-and-modernize workloads.
  3. Claim Azure SQL Database always permits installing arbitrary OS drivers.
  4. Verify agent and version requirements plus backup responsibility.

Explanation

Correct Answer

D:

Verify agent and version requirements plus backup responsibility. A successful correction should demonstrate that the needed engine and OS components run under customer-managed patch and backup duties.

Incorrect Answers

A:

Use GROUP BY then HAVING to filter aggregate group results. It serves SQL HAVING after grouping, not the diagnosed SQL Server on Azure VM OS control problem. Treating a VM as fully managed PaaS can leave guest patching unattended.

B:

Evaluate Azure SQL Managed Instance for compatible lift-and-modernize workloads. It serves Azure SQL Managed Instance compatibility, not the diagnosed SQL Server on Azure VM OS control problem. Treating a VM as fully managed PaaS can leave guest patching unattended.

C:

Claim Azure SQL Database always permits installing arbitrary OS drivers. This reinforces the error rather than addressing the SQL Server on Azure VM OS control failure. IaaS SQL Server offers control with greater operational responsibility.

Question 456

A telemetry lookup needs simple wide entities but no relational joins. Which principle BEST explains the correct Azure Table Storage key-value entities design decision?

  1. Different data roles collaborate but have distinct primary responsibilities.
  2. Table Storage is a key-attribute NoSQL store not a relational SQL engine.
  3. Data store suitability depends on workload access patterns not only data types.
  4. XML explicitly represents a hierarchy using nested tags and attributes.

Explanation

Correct Answer

B:

Table Storage is a key-attribute NoSQL store not a relational SQL engine. In this case the applicable decision is to use Azure Table Storage for schema-flexible key-based entity retrieval.

Incorrect Answers

A:

Different data roles collaborate but have distinct primary responsibilities. That concept explains Separation of data roles in a migration; the situation instead concerns Azure Table Storage key-value entities. Expecting server-side joins and foreign keys in Table Storage fails.

C:

Data store suitability depends on workload access patterns not only data types. That concept explains Data platform read and write profiles; the situation instead concerns Azure Table Storage key-value entities. Expecting server-side joins and foreign keys in Table Storage fails.

D:

XML explicitly represents a hierarchy using nested tags and attributes. That concept explains XML tagged hierarchy; the situation instead concerns Azure Table Storage key-value entities. Expecting server-side joins and foreign keys in Table Storage fails.

Question 457

A startup wants Azure hosting while preserving familiar MongoDB client interactions. Which principle BEST explains the correct Cosmos DB API for MongoDB design decision?

  1. Cosmos DB offers MongoDB-compatible interfaces but not necessarily every upstream feature identically.
  2. Shared access signatures grant bounded access without broad permanent account credentials.
  3. Azure Table Storage supports nonrelational wide entities beyond fixed SQL columns.
  4. TTL governs data expiration without requiring manual per-item deletes.

Explanation

Correct Answer

A:

Cosmos DB offers MongoDB-compatible interfaces but not necessarily every upstream feature identically. In this case the applicable decision is to evaluate Azure Cosmos DB for MongoDB compatible offerings and feature support.

Incorrect Answers

B:

Shared access signatures grant bounded access without broad permanent account credentials. That concept explains Blob SAS delegated access; the situation instead concerns Cosmos DB API for MongoDB. Assuming perfect wire compatibility without testing unsupported operations risks failures.

C:

Azure Table Storage supports nonrelational wide entities beyond fixed SQL columns. That concept explains Table Storage schemaless properties; the situation instead concerns Cosmos DB API for MongoDB. Assuming perfect wire compatibility without testing unsupported operations risks failures.

D:

TTL governs data expiration without requiring manual per-item deletes. That concept explains Cosmos DB TTL document expiration; the situation instead concerns Cosmos DB API for MongoDB. Assuming perfect wire compatibility without testing unsupported operations risks failures.

Question 458

A dashboard shows conflicting net revenue totals across reports. During testing, the team observes this specific failure: Uncontrolled measure definitions create contradictory dashboards. Which corrective check should be performed FIRST?

  1. Validate data quality and compare segmented trends before conclusions.
  2. Reconcile definitions against approved sample business records.
  3. Assume a column named Revenue is self-explanatory across all systems.
  4. Preserve object hierarchy and array semantics while parsing nested JSON properties.

Explanation

Correct Answer

B:

Reconcile definitions against approved sample business records. A successful correction should demonstrate that reports calculate the same measure under the same filters.

Incorrect Answers

A:

Validate data quality and compare segmented trends before conclusions. It serves Data analyst anomaly interpretation, not the diagnosed Data analyst metric definition problem. Uncontrolled measure definitions create contradictory dashboards.

C:

Assume a column named Revenue is self-explanatory across all systems. This reinforces the error rather than addressing the Data analyst metric definition failure. Data analysts define and test business measures rather than only placing visuals.

D:

Preserve object hierarchy and array semantics while parsing nested JSON properties. It serves JSON arrays and nested objects, not the diagnosed Data analyst metric definition problem. Uncontrolled measure definitions create contradictory dashboards.

Question 459

Business analysts repeatedly query totals across years and departments. Which principle BEST explains the correct Analytical warehouse for structured reporting design decision?

  1. File storage and searchable record databases serve different access patterns.
  2. Unstructured logs can become analyzable after parsing but remain unstructured at source.
  3. Predictive analytics estimates likely future outcomes from patterns.
  4. A warehouse organizes integrated analytical tables optimized for reporting.

Explanation

Correct Answer

D:

A warehouse organizes integrated analytical tables optimized for reporting. In this case the applicable decision is to use an analytical warehouse or Fabric Warehouse for governed relational reporting.

Incorrect Answers

A:

File storage and searchable record databases serve different access patterns. That concept explains File store versus database selection; the situation instead concerns Analytical warehouse for structured reporting. Treating production checkout row updates as a warehouse's primary workload can hurt analytics design.

B:

Unstructured logs can become analyzable after parsing but remain unstructured at source. That concept explains Log text extraction versus structured event fields; the situation instead concerns Analytical warehouse for structured reporting. Treating production checkout row updates as a warehouse's primary workload can hurt analytics design.

C:

Predictive analytics estimates likely future outcomes from patterns. That concept explains Predictive analytics forecasts; the situation instead concerns Analytical warehouse for structured reporting. Treating production checkout row updates as a warehouse's primary workload can hurt analytics design.

Question 460

A report must filter transaction amounts by customer region and month. After selecting the proper Star schema report model approach, which observation gives the clearest evidence of success?

  1. Time-filtered KQL queries return current and historical event patterns.
  2. Slices sum to the intended whole and readers can compare shares.
  3. Images remain retrievable while SQL reports query approved modeled facts.
  4. Filtered aggregations match approved transactional totals.

Explanation

Correct Answer

D:

Filtered aggregations match approved transactional totals. This is the directly observable result for Star schema report model; star schemas simplify controlled dimension filtering for analytics.

Incorrect Answers

A:

Time-filtered KQL queries return current and historical event patterns. This supports Fabric Eventhouse KQL event analytics, not confirmation of Star schema report model. The relevant evidence is that filtered aggregations match approved transactional totals.

B:

Slices sum to the intended whole and readers can compare shares. This supports Pie donut chart proportion caution, not confirmation of Star schema report model. The relevant evidence is that filtered aggregations match approved transactional totals.

C:

Images remain retrievable while SQL reports query approved modeled facts. This supports Structured warehouse and unstructured lake coexistence, not confirmation of Star schema report model. The relevant evidence is that filtered aggregations match approved transactional totals.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests