Practice Exams:

Microsoft DP-900 Dumps

EXAM: Microsoft Azure Data Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

DP-900 Premium Bundle


  • Premium File 332 Questions & Answers
  • Training Course 32 Lectures
  • Study Guide 672 Pages

Microsoft DP-900 Practice Test 89

Question 880

At Harborline Retail storefront activity requires near-live operational metrics. Which shortcut most directly threatens the intended data outcome?

  1. Have every department calculate quarterly revenue from unrelated raw CSV files with different definitions.
  2. Add an empty Fabric workspace and assume external live events start arriving without connectors.
  3. Deploy a static SQL query in a disconnected relational database and assume it automatically subscribes to the sensor stream.
  4. Expect a static imported dataset to show each operational write instantly without refresh.

Answer & Explanations

Correct answer: B

A.

Have every department calculate quarterly revenue from unrelated raw CSV files with different definitions. This concerns another issue: At Silvercrest Commerce executives compare sales performance across regions. In the stated case—At Harborline Retail storefront activity requires near-live operational metrics—reject: Add an empty Fabric workspace and assume external live events start arriving without connectors. The safer response is: Use Microsoft Fabric Real-Time Intelligence eventstream capabilities when live events must feed governed Fabric analytics destinations.

B.

Add an empty Fabric workspace and assume external live events start arriving without connectors. The scenario is: At Harborline Retail storefront activity requires near-live operational metrics. This undermines the mechanism: Eventstreams can connect event sources to Fabric's real-time processing experiences and selected sinks. Instead: Use Microsoft Fabric Real-Time Intelligence eventstream capabilities when live events must feed governed Fabric analytics destinations.

C.

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 Harborline Retail storefront activity requires near-live operational metrics—reject: Add an empty Fabric workspace and assume external live events start arriving without connectors. The safer response is: Use Microsoft Fabric Real-Time Intelligence eventstream capabilities when live events must feed governed Fabric analytics destinations.

D.

Expect a static imported dataset to show each operational write instantly without refresh. This concerns another issue: At Pinecrest Finance a morning report refresh is sufficient for yesterday's closing totals. In the stated case—At Harborline Retail storefront activity requires near-live operational metrics—reject: Add an empty Fabric workspace and assume external live events start arriving without connectors. The safer response is: Use Microsoft Fabric Real-Time Intelligence eventstream capabilities when live events must feed governed Fabric analytics destinations.

Question 881

At Meadowport Transit buses upload buffered GPS events after reconnecting. Which design or Azure data approach best fits this requirement?

  1. Choose a lakehouse when a project needs both raw files and managed analytical tables for mixed data engineering workloads.
  2. Use Azure Event Hubs to ingest high-volume event streams from supported producers before downstream processing.
  3. Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.
  4. Use a scatter plot when exploring whether two quantitative variables have an association.

Answer & Explanations

Correct answer: C

A.

Choose a lakehouse when a project needs both raw files and managed analytical tables for mixed data engineering workloads. This addresses a different situation: At Cedarbridge Media analysts combine raw events and curated advertising tables. The present case is: At Meadowport Transit buses upload buffered GPS events after reconnecting. The relevant action here is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

B.

Use Azure Event Hubs to ingest high-volume event streams from supported producers before downstream processing. This addresses a different situation: At Harborcrest Transport thousands of vehicles emit location updates. The present case is: At Meadowport Transit buses upload buffered GPS events after reconnecting. The relevant action here is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

C.

Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time. This works because: Event time reflects when the source event happened; processing time reflects when the system saw it. The scenario is: At Meadowport Transit buses upload buffered GPS events after reconnecting. Verify the outcome by: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

D.

Use a scatter plot when exploring whether two quantitative variables have an association. This addresses a different situation: At Pinewood Retail analysts compare campaign spend with customer acquisitions. The present case is: At Meadowport Transit buses upload buffered GPS events after reconnecting. The relevant action here is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

Question 882

At Meadowport Transit buses upload buffered GPS events after reconnecting. The team proposes this approach: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time. Which technical principle explains the choice?

  1. Stream Analytics applies SQL-like continuous queries to configured inputs and outputs.
  2. Event time reflects when the source event happened; processing time reflects when the system saw it.
  3. Partition pruning lets engines skip unrelated date segments instead of scanning all years of data.
  4. Reports support detailed interactive visuals and filters while dashboards provide a consolidated surface for monitoring selected metrics.

Answer & Explanations

Correct answer: B

A.

Stream Analytics applies SQL-like continuous queries to configured inputs and outputs. That explains a separate situation: At Pinebrook Facilities sensors send readings to an event hub. The current case is: At Meadowport Transit buses upload buffered GPS events after reconnecting. The actual mechanism is: Event time reflects when the source event happened; processing time reflects when the system saw it.

B.

Event time reflects when the source event happened; processing time reflects when the system saw it. This principle supports the intervention: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time. The relevant scenario is: At Meadowport Transit buses upload buffered GPS events after reconnecting. Verify the result by: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

C.

Partition pruning lets engines skip unrelated date segments instead of scanning all years of data. That explains a separate situation: At Oakfield Utilities analysts frequently report one month of meter usage. The current case is: At Meadowport Transit buses upload buffered GPS events after reconnecting. The actual mechanism is: Event time reflects when the source event happened; processing time reflects when the system saw it.

D.

Reports support detailed interactive visuals and filters while dashboards provide a consolidated surface for monitoring selected metrics. That explains a separate situation: At Harborland Banking executives monitor headline risk indicators and analysts need detail pages. The current case is: At Meadowport Transit buses upload buffered GPS events after reconnecting. The actual mechanism is: Event time reflects when the source event happened; processing time reflects when the system saw it.

Question 883

At Meadowport Transit buses upload buffered GPS events after reconnecting. After implementing this approach—Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time—which result would most directly confirm success?

  1. Emit a synthetic threshold event and verify an immediate alert and a later analytical archive record.
  2. Add a fictional revenue measure and confirm it changes when the product slicer is adjusted.
  3. Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.
  4. Import three synthetic source rows containing malformed dates and verify only validated clean records reach the reporting table.

Answer & Explanations

Correct answer: C

A.

Emit a synthetic threshold event and verify an immediate alert and a later analytical archive record. This tests a separate situation: At Pineport Healthcare medical equipment signals abnormal temperatures. The observed case is: At Meadowport Transit buses upload buffered GPS events after reconnecting. Use this acceptance check instead: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

B.

Add a fictional revenue measure and confirm it changes when the product slicer is adjusted. This tests a separate situation: At Silverlake Services managers compare revenue by selected region. The observed case is: At Meadowport Transit buses upload buffered GPS events after reconnecting. Use this acceptance check instead: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

C.

Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window. This tests the targeted action: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time. The reason is: Event time reflects when the source event happened; processing time reflects when the system saw it. The reported case is: At Meadowport Transit buses upload buffered GPS events after reconnecting.

D.

Import three synthetic source rows containing malformed dates and verify only validated clean records reach the reporting table. This tests a separate situation: At Cedarfield Finance external invoices need standard currency codes before reporting. The observed case is: At Meadowport Transit buses upload buffered GPS events after reconnecting. Use this acceptance check instead: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

Question 884

At Meadowport Transit buses upload buffered GPS events after reconnecting. Which shortcut most directly threatens the intended data outcome?

  1. Connect unrelated tables by matching display names that are not stable unique keys.
  2. Store a decade of evenly used time-series data in one undifferentiated daily-export file.
  3. Assume a consumer can recover messages that have already aged out of the event stream.
  4. Assign every delayed event to the moment it reached the processor with no policy.

Answer & Explanations

Correct answer: D

A.

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 Meadowport Transit buses upload buffered GPS events after reconnecting—reject: Assign every delayed event to the moment it reached the processor with no policy. The safer response is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

B.

Store a decade of evenly used time-series data in one undifferentiated daily-export file. This concerns another issue: At Oakfield Utilities analysts frequently report one month of meter usage. In the stated case—At Meadowport Transit buses upload buffered GPS events after reconnecting—reject: Assign every delayed event to the moment it reached the processor with no policy. The safer response is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

C.

Assume a consumer can recover messages that have already aged out of the event stream. This concerns another issue: At Harborcrest Logistics a tracking processor is offline during a deployment. In the stated case—At Meadowport Transit buses upload buffered GPS events after reconnecting—reject: Assign every delayed event to the moment it reached the processor with no policy. The safer response is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

D.

Assign every delayed event to the moment it reached the processor with no policy. The scenario is: At Meadowport Transit buses upload buffered GPS events after reconnecting. The likely failure is: Historical time buckets are distorted during network delays. Instead: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

Question 885

At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. Which design or Azure data approach best fits this requirement?

  1. Define a controlled late-arrival and deduplication policy for at-least-once streaming delivery.
  2. Choose a bar chart for comparing distinct categories with a common quantitative scale.
  3. Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.
  4. Use a star schema with fact and dimension tables for understandable report filters and aggregations.

Answer & Explanations

Correct answer: C

A.

Define a controlled late-arrival and deduplication policy for at-least-once streaming delivery. This addresses a different situation: At Silverpoint Banking an event publisher retries after a brief timeout. The present case is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. The relevant action here is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

B.

Choose a bar chart for comparing distinct categories with a common quantitative scale. This addresses a different situation: At Cedarbank Logistics supervisors compare delivery counts among depots. The present case is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. The relevant action here is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

C.

Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time. This works because: Event time reflects when the source event happened; processing time reflects when the system saw it. The scenario is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. Verify the outcome by: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

D.

Use a star schema with fact and dimension tables for understandable report filters and aggregations. This addresses a different situation: At Pinecrest Retail product-category reporting relies on many transactions. The present case is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. The relevant action here is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

Question 886

At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. The team proposes this approach: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time. Which technical principle explains the choice?

  1. Model relationships propagate filter context between related tables according to direction and cardinality.
  2. Event time reflects when the source event happened; processing time reflects when the system saw it.
  3. Streaming handles events as they arrive while batch processing groups bounded input sets at intervals.
  4. Fact tables hold numeric events while dimensions describe dates, products and customers used to filter or group them.

Answer & Explanations

Correct answer: B

A.

Model relationships propagate filter context between related tables according to direction and cardinality. That explains a separate situation: At Harborfield Commerce sales facts reference a product dimension. The current case is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. The actual mechanism is: Event time reflects when the source event happened; processing time reflects when the system saw it.

B.

Event time reflects when the source event happened; processing time reflects when the system saw it. This principle supports the intervention: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time. The relevant scenario is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. Verify the result by: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

C.

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 Pinecrest Manufacturing factory devices sometimes deliver readings out of order. The actual mechanism is: Event time reflects when the source event happened; processing time reflects when the system saw it.

D.

Fact tables hold numeric events while dimensions describe dates, products and customers used to filter or group them. That explains a separate situation: At Pinecrest Retail product-category reporting relies on many transactions. The current case is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. The actual mechanism is: Event time reflects when the source event happened; processing time reflects when the system saw it.

Question 887

At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. After implementing this approach—Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time—which result would most directly confirm success?

  1. Plot fictional advertising spend against sales and identify an outlier while avoiding causal claims.
  2. Query one synthetic month from several years of data and inspect which partitions were read.
  3. Replay a fictional event with the same ID and confirm the sink counts it only once.
  4. Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

Answer & Explanations

Correct answer: D

A.

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 Pinecrest Manufacturing factory devices sometimes deliver readings out of order. Use this acceptance check instead: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

B.

Query one synthetic month from several years of data and inspect which partitions were read. This tests a separate situation: At Oakfield Utilities analysts frequently report one month of meter usage. The observed case is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. Use this acceptance check instead: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

C.

Replay a fictional event with the same ID and confirm the sink counts it only once. This tests a separate situation: At Silverpoint Banking an event publisher retries after a brief timeout. The observed case is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. Use this acceptance check instead: Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window.

D.

Delay a fictional event by two minutes and verify the configured lateness rule places it in the correct time window. This tests the targeted action: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time. The reason is: Event time reflects when the source event happened; processing time reflects when the system saw it. The reported case is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order.

Question 888

At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. Which shortcut most directly threatens the intended data outcome?

  1. Place every descriptive product attribute into repeated transaction rows without a governed dimension model.
  2. Deploy a static SQL query in a disconnected relational database and assume it automatically subscribes to the sensor stream.
  3. Hide a confidential table on the report canvas while leaving its underlying dataset unrestricted.
  4. Assign every delayed event to the moment it reached the processor with no policy.

Answer & Explanations

Correct answer: D

A.

Place every descriptive product attribute into repeated transaction rows without a governed dimension model. This concerns another issue: At Pinecrest Retail product-category reporting relies on many transactions. In the stated case—At Pinecrest Manufacturing factory devices sometimes deliver readings out of order—reject: Assign every delayed event to the moment it reached the processor with no policy. The safer response is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

B.

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 Pinecrest Manufacturing factory devices sometimes deliver readings out of order—reject: Assign every delayed event to the moment it reached the processor with no policy. The safer response is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

C.

Hide a confidential table on the report canvas while leaving its underlying dataset unrestricted. This concerns another issue: At Cedarcrest Finance regional managers should see only their branch transactions. In the stated case—At Pinecrest Manufacturing factory devices sometimes deliver readings out of order—reject: Assign every delayed event to the moment it reached the processor with no policy. The safer response is: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

D.

Assign every delayed event to the moment it reached the processor with no policy. The scenario is: At Pinecrest Manufacturing factory devices sometimes deliver readings out of order. The likely failure is: Historical time buckets are distorted during network delays. Instead: Choose event-time windows when late-arriving sensor measurements must be attributed to their occurrence time rather than receipt time.

Question 889

At Silverpoint Banking an event publisher retries after a brief timeout. Which design or Azure data approach best fits this requirement?

  1. Define a controlled late-arrival and deduplication policy for at-least-once streaming delivery.
  2. Use Azure Event Hubs to ingest high-volume event streams from supported producers before downstream processing.
  3. Use Microsoft Fabric OneLake as a governed shared logical lake for permitted analytics workloads.
  4. Choose a line chart for a continuous time trend rather than using a pie chart for every timestamp.

Answer & Explanations

Correct answer: A

A.

Define a controlled late-arrival and deduplication policy for at-least-once streaming delivery. This works because: Retries and event-time disorder can produce duplicate or tardy events that require stable IDs and window rules. The scenario is: At Silverpoint Banking an event publisher retries after a brief timeout. Verify the outcome by: Replay a fictional event with the same ID and confirm the sink counts it only once.

B.

Use Azure Event Hubs to ingest high-volume event streams from supported producers before downstream processing. This addresses a different situation: At Harborcrest Transport thousands of vehicles emit location updates. The present case is: At Silverpoint Banking an event publisher retries after a brief timeout. The relevant action here is: Define a controlled late-arrival and deduplication policy for at-least-once streaming delivery.

C.

Use Microsoft Fabric OneLake as a governed shared logical lake for permitted analytics workloads. This addresses a different situation: At Meadowbank Insurance several Fabric teams need a centrally governed analytical foundation. The present case is: At Silverpoint Banking an event publisher retries after a brief timeout. The relevant action here is: Define a controlled late-arrival and deduplication policy for at-least-once streaming delivery.

D.

Choose a line chart for a continuous time trend rather than using a pie chart for every timestamp. This addresses a different situation: At Meadowport Media analysts inspect daily subscription signups. The present case is: At Silverpoint Banking an event publisher retries after a brief timeout. The relevant action here is: Define a controlled late-arrival and deduplication policy for at-least-once streaming delivery.

Question 890

At Silverpoint Banking an event publisher retries after a brief timeout. The team proposes this approach: Define a controlled late-arrival and deduplication policy for at-least-once streaming delivery. Which technical principle explains the choice?

  1. Retries and event-time disorder can produce duplicate or tardy events that require stable IDs and window rules.
  2. Position along a time axis makes change and seasonality easier to compare across ordered periods.
  3. A bounded event retention period permits eligible consumers to resume from offsets without requiring the producer to resend immediately.
  4. Data Factory pipelines coordinate copy activities, triggers, transformations and operational monitoring across services.

Answer & Explanations

Correct answer: A

A.

Retries and event-time disorder can produce duplicate or tardy events that require stable IDs and window rules. This principle supports the intervention: Define a controlled late-arrival and deduplication policy for at-least-once streaming delivery. The relevant scenario is: At Silverpoint Banking an event publisher retries after a brief timeout. Verify the result by: Replay a fictional event with the same ID and confirm the sink counts it only once.

B.

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 Silverpoint Banking an event publisher retries after a brief timeout. The actual mechanism is: Retries and event-time disorder can produce duplicate or tardy events that require stable IDs and window rules.

C.

A bounded event retention period permits eligible consumers to resume from offsets without requiring the producer to resend immediately. That explains a separate situation: At Harborcrest Logistics a tracking processor is offline during a deployment. The current case is: At Silverpoint Banking an event publisher retries after a brief timeout. The actual mechanism is: Retries and event-time disorder can produce duplicate or tardy events that require stable IDs and window rules.

D.

Data Factory pipelines coordinate copy activities, triggers, transformations and operational monitoring across services. That explains a separate situation: At Harborpoint Education SQL and file extracts feed a shared Azure reporting lake. The current case is: At Silverpoint Banking an event publisher retries after a brief timeout. The actual mechanism is: Retries and event-time disorder can produce duplicate or tardy events that require stable IDs and window rules.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests