Microsoft DP-900 Dumps
Microsoft DP-900 Practice Test 80
Question 790
At Meadowport Hotels booking facts must group by property and calendar date. The team proposes this approach: Use a star schema with fact and dimension tables for understandable report filters and aggregations. Which technical principle explains the choice?
Answer & Explanations
Correct answer: B
Larger batch jobs can be efficient but delay availability, so cadence must match business SLAs. That explains a separate situation: At Harborland Retail nightly inventory analytics satisfy finance but not emergency stock alerts. The current case is: At Meadowport Hotels booking facts must group by property and calendar date. The actual mechanism is: Fact tables hold numeric events while dimensions describe dates, products and customers used to filter or group them.
Fact tables hold numeric events while dimensions describe dates, products and customers used to filter or group them. This principle supports the intervention: Use a star schema with fact and dimension tables for understandable report filters and aggregations. The relevant scenario is: At Meadowport Hotels booking facts must group by property and calendar date. Verify the result by: Build a small sales fact table and product dimension then verify a category-filtered revenue total.
RLS filters model rows according to configured role rules and identity mapping rather than merely hiding visuals. That explains a separate situation: At Cedarcrest Finance regional managers should see only their branch transactions. The current case is: At Meadowport Hotels booking facts must group by property and calendar date. The actual mechanism is: Fact tables hold numeric events while dimensions describe dates, products and customers used to filter or group them.
Windowed streaming computations aggregate events over bounded time intervals as new data arrives. That explains a separate situation: At Meadowview Commerce payment anomalies are monitored in rolling five-minute windows. The current case is: At Meadowport Hotels booking facts must group by property and calendar date. The actual mechanism is: Fact tables hold numeric events while dimensions describe dates, products and customers used to filter or group them.
Question 791
At Meadowport Hotels booking facts must group by property and calendar date. After implementing this approach—Use a star schema with fact and dimension tables for understandable report filters and aggregations—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
Send synthetic purchases across a five-minute interval and verify the window aggregate resets as designed. This tests a separate situation: At Meadowview Commerce payment anomalies are monitored in rolling five-minute windows. The observed case is: At Meadowport Hotels booking facts must group by property and calendar date. Use this acceptance check instead: Build a small sales fact table and product dimension then verify a category-filtered revenue total.
Build a small sales fact table and product dimension then verify a category-filtered revenue total. This tests the targeted action: Use a star schema with fact and dimension tables for understandable report filters and aggregations. The reason is: Fact tables hold numeric events while dimensions describe dates, products and customers used to filter or group them. The reported case is: At Meadowport Hotels booking facts must group by property and calendar date.
Plot fictional advertising spend against sales and identify an outlier while avoiding causal claims. This tests a separate situation: At Pinewood Retail analysts compare campaign spend with customer acquisitions. The observed case is: At Meadowport Hotels booking facts must group by property and calendar date. Use this acceptance check instead: Build a small sales fact table and product dimension then verify a category-filtered revenue total.
Send one valid and one invalid synthetic record and confirm only the valid record reaches the curated table. This tests a separate situation: At Meadowfield Retail some supplier feeds contain negative quantities. The observed case is: At Meadowport Hotels booking facts must group by property and calendar date. Use this acceptance check instead: Build a small sales fact table and product dimension then verify a category-filtered revenue total.
Question 792
At Meadowport Hotels booking facts must group by property and calendar date. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: B
Share one destructive manual cursor between unrelated alerting and archival applications. This concerns another issue: At Oakcrest Mobility live tracking and reporting consume the same event source. In the stated case—At Meadowport Hotels booking facts must group by property and calendar date—reject: Place every descriptive product attribute into repeated transaction rows without a governed dimension model. The safer response is: Use a star schema with fact and dimension tables for understandable report filters and aggregations.
Place every descriptive product attribute into repeated transaction rows without a governed dimension model. The scenario is: At Meadowport Hotels booking facts must group by property and calendar date. This undermines the mechanism: Fact tables hold numeric events while dimensions describe dates, products and customers used to filter or group them. Instead: Use a star schema with fact and dimension tables for understandable report filters and aggregations.
Treat a lakehouse as a requirement to convert every audio file directly into a relational transaction row. This concerns another issue: At Cedarbridge Media analysts combine raw events and curated advertising tables. In the stated case—At Meadowport Hotels booking facts must group by property and calendar date—reject: Place every descriptive product attribute into repeated transaction rows without a governed dimension model. The safer response is: Use a star schema with fact and dimension tables for understandable report filters and aggregations.
Build separate disconnected charts each using a different definition of sales. This concerns another issue: At Harborbank Retail executives need sales dashboards sharing one definition of revenue. In the stated case—At Meadowport Hotels booking facts must group by property and calendar date—reject: Place every descriptive product attribute into repeated transaction rows without a governed dimension model. The safer response is: Use a star schema with fact and dimension tables for understandable report filters and aggregations.
Question 793
At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: A
Build an incremental ingestion path based on reliable watermarks or source change tracking. This works because: Incremental loads process changed records instead of copying all historical data on each run. The scenario is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. Verify the outcome by: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Apply Power BI row-level security when different users should see only their permitted records. This addresses a different situation: At Cedarcrest Finance regional managers should see only their branch transactions. The present case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. The relevant action here is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Make ingestion transformations idempotent by using stable business keys when retrying failed batches. This addresses a different situation: At Silverbrook Logistics pipelines reattempt delayed shipment messages. The present case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. The relevant action here is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Use Microsoft Fabric Real-Time Intelligence eventstream capabilities when live events must feed governed Fabric analytics destinations. This addresses a different situation: At Cedarcrest Media live audience actions feed a Fabric real-time dashboard. The present case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. The relevant action here is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Question 794
At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. The team proposes this approach: Build an incremental ingestion path based on reliable watermarks or source change tracking. Which technical principle explains the choice?
Answer & Explanations
Correct answer: B
Extract-transform-load performs transformations before storing the final warehouse-ready form. That explains a separate situation: At Cedarfield Finance external invoices need standard currency codes before reporting. The current case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. The actual mechanism is: Incremental loads process changed records instead of copying all historical data on each run.
Incremental loads process changed records instead of copying all historical data on each run. This principle supports the intervention: Build an incremental ingestion path based on reliable watermarks or source change tracking. The relevant scenario is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. Verify the result by: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Import caches data in the Power BI model and requires refresh to reflect changed source rows. That explains a separate situation: At Pinecrest Finance a morning report refresh is sufficient for yesterday's closing totals. The current case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. The actual mechanism is: Incremental loads process changed records instead of copying all historical data on each run.
Streaming handles events as they arrive while batch processing groups bounded input sets at intervals. That explains a separate situation: At Cedarpoint Manufacturing equipment overheating requires prompt detection. The current case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. The actual mechanism is: Incremental loads process changed records instead of copying all historical data on each run.
Question 795
At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. After implementing this approach—Build an incremental ingestion path based on reliable watermarks or source change tracking—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
Update a synthetic source record and verify the report reflects it after a configured refresh. This tests a separate situation: At Pinecrest Finance a morning report refresh is sufficient for yesterday's closing totals. The observed case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. Use this acceptance check instead: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Update two fictional source records and confirm the second pipeline run imports only eligible changes. This tests the targeted action: Build an incremental ingestion path based on reliable watermarks or source change tracking. The reason is: Incremental loads process changed records instead of copying all historical data on each run. The reported case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history.
Stream sample temperature events, filter values above a threshold and verify only matching output reaches the destination. This tests a separate situation: At Pinebrook Facilities sensors send readings to an event hub. The observed case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. Use this acceptance check instead: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Land sample JSON files and create a queryable curated table without discarding the original files. This tests a separate situation: At Cedarbridge Media analysts combine raw events and curated advertising tables. The observed case is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. Use this acceptance check instead: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Question 796
At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: B
Paste a fixed grand total into every transaction row and expect slicers to recalculate it. This concerns another issue: At Silverlake Services managers compare revenue by selected region. In the stated case—At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history—reject: Reappend the entire transaction history each hour with no deduplication. The safer response is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Reappend the entire transaction history each hour with no deduplication. The scenario is: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. This undermines the mechanism: Incremental loads process changed records instead of copying all historical data on each run. Instead: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Overwrite transformations without a change record while claiming prior KPI totals are reproducible. This concerns another issue: At Cedarcrest Banking financial metrics require stable audit evidence. In the stated case—At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history—reject: Reappend the entire transaction history each hour with no deduplication. The safer response is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Deploy a static SQL query in a disconnected relational database and assume it automatically subscribes to the sensor stream. This concerns another issue: At Pinebrook Facilities sensors send readings to an event hub. In the stated case—At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history—reject: Reappend the entire transaction history each hour with no deduplication. The safer response is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Question 797
At Oakbridge Services service tickets update frequently but old cases rarely change. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: C
Use partitioned analytical files or tables for large date-filtered scans when data volume and query patterns justify it. This addresses a different situation: At Oakfield Utilities analysts frequently report one month of meter usage. The present case is: At Oakbridge Services service tickets update frequently but old cases rarely change. The relevant action here is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Use Azure Stream Analytics for a supported continuous stream query that filters and aggregates incoming events. This addresses a different situation: At Pinebrook Facilities sensors send readings to an event hub. The present case is: At Oakbridge Services service tickets update frequently but old cases rarely change. The relevant action here is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Build an incremental ingestion path based on reliable watermarks or source change tracking. This works because: Incremental loads process changed records instead of copying all historical data on each run. The scenario is: At Oakbridge Services service tickets update frequently but old cases rarely change. Verify the outcome by: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Use a DAX measure for a filter-context-dependent aggregate rather than storing the same changing total in every fact row. This addresses a different situation: At Silverlake Services managers compare revenue by selected region. The present case is: At Oakbridge Services service tickets update frequently but old cases rarely change. The relevant action here is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Question 798
At Oakbridge Services service tickets update frequently but old cases rarely change. The team proposes this approach: Build an incremental ingestion path based on reliable watermarks or source change tracking. Which technical principle explains the choice?
Answer & Explanations
Correct answer: A
Incremental loads process changed records instead of copying all historical data on each run. This principle supports the intervention: Build an incremental ingestion path based on reliable watermarks or source change tracking. The relevant scenario is: At Oakbridge Services service tickets update frequently but old cases rarely change. Verify the result by: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Separating bad records protects curated datasets while retaining evidence for correction and replay. That explains a separate situation: At Meadowfield Retail some supplier feeds contain negative quantities. The current case is: At Oakbridge Services service tickets update frequently but old cases rarely change. The actual mechanism is: Incremental loads process changed records instead of copying all historical data on each run.
Position along a time axis makes change and seasonality easier to compare across ordered periods. That explains a separate situation: At Meadowport Media analysts inspect daily subscription signups. The current case is: At Oakbridge Services service tickets update frequently but old cases rarely change. The actual mechanism is: Incremental loads process changed records instead of copying all historical data on each run.
A hot streaming path reacts promptly while the cold path can consolidate history for deeper analysis. That explains a separate situation: At Pineport Healthcare medical equipment signals abnormal temperatures. The current case is: At Oakbridge Services service tickets update frequently but old cases rarely change. The actual mechanism is: Incremental loads process changed records instead of copying all historical data on each run.
Question 799
At Oakbridge Services service tickets update frequently but old cases rarely change. After implementing this approach—Build an incremental ingestion path based on reliable watermarks or source change tracking—which result would most directly confirm success?
Answer & Explanations
Correct answer: A
Update two fictional source records and confirm the second pipeline run imports only eligible changes. This tests the targeted action: Build an incremental ingestion path based on reliable watermarks or source change tracking. The reason is: Incremental loads process changed records instead of copying all historical data on each run. The reported case is: At Oakbridge Services service tickets update frequently but old cases rarely change.
Execute a test copy from approved storage to an analytical sink and inspect the pipeline run history. This tests a separate situation: At Harborpoint Education SQL and file extracts feed a shared Azure reporting lake. The observed case is: At Oakbridge Services service tickets update frequently but old cases rarely change. Use this acceptance check instead: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Update a synthetic source record and verify the report reflects it after a configured refresh. This tests a separate situation: At Pinecrest Finance a morning report refresh is sufficient for yesterday's closing totals. The observed case is: At Oakbridge Services service tickets update frequently but old cases rarely change. Use this acceptance check instead: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Publish synthetic events, consume them through a test consumer group and verify offsets advance. This tests a separate situation: At Harborcrest Transport thousands of vehicles emit location updates. The observed case is: At Oakbridge Services service tickets update frequently but old cases rarely change. Use this acceptance check instead: Update two fictional source records and confirm the second pipeline run imports only eligible changes.
Question 800
At Oakbridge Services service tickets update frequently but old cases rarely change. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: A
Reappend the entire transaction history each hour with no deduplication. The scenario is: At Oakbridge Services service tickets update frequently but old cases rarely change. This undermines the mechanism: Incremental loads process changed records instead of copying all historical data on each run. Instead: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Connect unrelated tables by matching display names that are not stable unique keys. This concerns another issue: At Harborfield Commerce sales facts reference a product dimension. In the stated case—At Oakbridge Services service tickets update frequently but old cases rarely change—reject: Reappend the entire transaction history each hour with no deduplication. The safer response is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Route emergency alerts through a slow end-of-day ETL job. This concerns another issue: At Pineport Healthcare medical equipment signals abnormal temperatures. In the stated case—At Oakbridge Services service tickets update frequently but old cases rarely change—reject: Reappend the entire transaction history each hour with no deduplication. The safer response is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Schedule a single weekly batch while promising a dashboard accurate every ten minutes. This concerns another issue: At Harborland Retail nightly inventory analytics satisfy finance but not emergency stock alerts. In the stated case—At Oakbridge Services service tickets update frequently but old cases rarely change—reject: Reappend the entire transaction history each hour with no deduplication. The safer response is: Build an incremental ingestion path based on reliable watermarks or source change tracking.
Microsoft Azure Data Fundamentals (DP-900) Practice Tests
- Microsoft DP-900 Practice Test 78 - 10 Questions (Last Reviewed 29-Oct-2026)
- Microsoft DP-900 Practice Test 79 - 10 Questions (Last Reviewed 28-Oct-2026)
- Microsoft DP-900 Practice Test 80 - 10 Questions (Last Reviewed 27-Oct-2026)
- Microsoft DP-900 Practice Test 81 - 10 Questions (Last Reviewed 26-Oct-2026)
- Microsoft DP-900 Practice Test 82 - 10 Questions (Last Reviewed 25-Oct-2026)