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 92

Question 910

At Silverfield Security access logs require prompt anomaly notification and historical reporting. The team proposes this approach: Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing. Which technical principle explains the choice?

  1. Position along a time axis makes change and seasonality easier to compare across ordered periods.
  2. Stream Analytics applies SQL-like continuous queries to configured inputs and outputs.
  3. A hot streaming path reacts promptly while the cold path can consolidate history for deeper analysis.
  4. Fact tables hold numeric events while dimensions describe dates, products and customers used to filter or group them.

Answer & Explanations

Correct answer: C

A.

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 Silverfield Security access logs require prompt anomaly notification and historical reporting. The actual mechanism is: A hot streaming path reacts promptly while the cold path can consolidate history for deeper analysis.

B.

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 Silverfield Security access logs require prompt anomaly notification and historical reporting. The actual mechanism is: A hot streaming path reacts promptly while the cold path can consolidate history for deeper analysis.

C.

A hot streaming path reacts promptly while the cold path can consolidate history for deeper analysis. This principle supports the intervention: Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing. The relevant scenario is: At Silverfield Security access logs require prompt anomaly notification and historical reporting. Verify the result by: Emit a synthetic threshold event and verify an immediate alert and a later analytical archive record.

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 Silverfield Security access logs require prompt anomaly notification and historical reporting. The actual mechanism is: A hot streaming path reacts promptly while the cold path can consolidate history for deeper analysis.

Question 911

At Silverfield Security access logs require prompt anomaly notification and historical reporting. After implementing this approach—Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing—which result would most directly confirm success?

  1. Update two fictional source records and confirm the second pipeline run imports only eligible changes.
  2. Emit a synthetic threshold event and verify an immediate alert and a later analytical archive record.
  3. Replay a fictional event with the same ID and confirm the sink counts it only once.
  4. Open a sample filtered visual and confirm the corresponding source query executes under the designed permissions.

Answer & Explanations

Correct answer: B

A.

Update two fictional source records and confirm the second pipeline run imports only eligible changes. This tests a separate situation: At Cedarbank Payments the warehouse must refresh recent settlements without reloading years of history. The observed case is: At Silverfield Security access logs require prompt anomaly notification and historical reporting. Use this acceptance check instead: Emit a synthetic threshold event and verify an immediate alert and a later analytical archive record.

B.

Emit a synthetic threshold event and verify an immediate alert and a later analytical archive record. This tests the targeted action: Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing. The reason is: A hot streaming path reacts promptly while the cold path can consolidate history for deeper analysis. The reported case is: At Silverfield Security access logs require prompt anomaly notification and historical reporting.

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 Silverfield Security access logs require prompt anomaly notification and historical reporting. Use this acceptance check instead: Emit a synthetic threshold event and verify an immediate alert and a later analytical archive record.

D.

Open a sample filtered visual and confirm the corresponding source query executes under the designed permissions. This tests a separate situation: At Cedarfield Operations a governed warehouse remains the authority for interactive dashboard queries. The observed case is: At Silverfield Security access logs require prompt anomaly notification and historical reporting. Use this acceptance check instead: Emit a synthetic threshold event and verify an immediate alert and a later analytical archive record.

Question 912

At Silverfield Security access logs require prompt anomaly notification and historical reporting. Which shortcut most directly threatens the intended data outcome?

  1. Assume DirectQuery has no dependency on the source system's availability or latency.
  2. Append duplicate transactions on every network retry without comparing event IDs.
  3. Route emergency alerts through a slow end-of-day ETL job.
  4. Deploy a static SQL query in a disconnected relational database and assume it automatically subscribes to the sensor stream.

Answer & Explanations

Correct answer: C

A.

Assume DirectQuery has no dependency on the source system's availability or latency. This concerns another issue: At Cedarfield Operations a governed warehouse remains the authority for interactive dashboard queries. In the stated case—At Silverfield Security access logs require prompt anomaly notification and historical reporting—reject: Route emergency alerts through a slow end-of-day ETL job. The safer response is: Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing.

B.

Append duplicate transactions on every network retry without comparing event IDs. This concerns another issue: At Silverbrook Logistics pipelines reattempt delayed shipment messages. In the stated case—At Silverfield Security access logs require prompt anomaly notification and historical reporting—reject: Route emergency alerts through a slow end-of-day ETL job. The safer response is: Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing.

C.

Route emergency alerts through a slow end-of-day ETL job. The scenario is: At Silverfield Security access logs require prompt anomaly notification and historical reporting. This undermines the mechanism: A hot streaming path reacts promptly while the cold path can consolidate history for deeper analysis. Instead: Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing.

D.

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 Silverfield Security access logs require prompt anomaly notification and historical reporting—reject: Route emergency alerts through a slow end-of-day ETL job. The safer response is: Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing.

Question 913

At Oakcrest Mobility live tracking and reporting consume the same event source. Which design or Azure data approach best fits this requirement?

  1. Use a star schema with fact and dimension tables for understandable report filters and aggregations.
  2. Choose a line chart for a continuous time trend rather than using a pie chart for every timestamp.
  3. Use Microsoft Fabric Real-Time Intelligence eventstream capabilities when live events must feed governed Fabric analytics destinations.
  4. Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

Answer & Explanations

Correct answer: D

A.

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 Oakcrest Mobility live tracking and reporting consume the same event source. The relevant action here is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

B.

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 Oakcrest Mobility live tracking and reporting consume the same event source. The relevant action here is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

C.

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 Oakcrest Mobility live tracking and reporting consume the same event source. The relevant action here is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

D.

Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications. This works because: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions. The scenario is: At Oakcrest Mobility live tracking and reporting consume the same event source. Verify the outcome by: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

Question 914

At Oakcrest Mobility live tracking and reporting consume the same event source. The team proposes this approach: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications. Which technical principle explains the choice?

  1. Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions.
  2. Extract-transform-load performs transformations before storing the final warehouse-ready form.
  3. Reports support detailed interactive visuals and filters while dashboards provide a consolidated surface for monitoring selected metrics.
  4. Windowed streaming computations aggregate events over bounded time intervals as new data arrives.

Answer & Explanations

Correct answer: A

A.

Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions. This principle supports the intervention: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications. The relevant scenario is: At Oakcrest Mobility live tracking and reporting consume the same event source. Verify the result by: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

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 Oakcrest Mobility live tracking and reporting consume the same event source. The actual mechanism is: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions.

C.

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 Oakcrest Mobility live tracking and reporting consume the same event source. The actual mechanism is: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions.

D.

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 Oakcrest Mobility live tracking and reporting consume the same event source. The actual mechanism is: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions.

Question 915

At Oakcrest Mobility live tracking and reporting consume the same event source. After implementing this approach—Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications—which result would most directly confirm success?

  1. Add a fictional revenue measure and confirm it changes when the product slicer is adjusted.
  2. Send synthetic purchases across a five-minute interval and verify the window aggregate resets as designed.
  3. Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.
  4. Create a test lakehouse table and verify only approved workspace identities can read the source files.

Answer & Explanations

Correct answer: C

A.

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 Oakcrest Mobility live tracking and reporting consume the same event source. Use this acceptance check instead: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

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 Oakcrest Mobility live tracking and reporting consume the same event source. Use this acceptance check instead: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

C.

Run two test consumer groups and confirm each sees the intended events without resetting the other's offset. This tests the targeted action: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications. The reason is: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions. The reported case is: At Oakcrest Mobility live tracking and reporting consume the same event source.

D.

Create a test lakehouse table and verify only approved workspace identities can read the source files. This tests a separate situation: At Meadowbank Insurance several Fabric teams need a centrally governed analytical foundation. The observed case is: At Oakcrest Mobility live tracking and reporting consume the same event source. Use this acceptance check instead: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

Question 916

At Oakcrest Mobility live tracking and reporting consume the same event source. Which shortcut most directly threatens the intended data outcome?

  1. Share one destructive manual cursor between unrelated alerting and archival applications.
  2. Use a pie chart to prove one numeric factor causes another.
  3. Schedule a single weekly batch while promising a dashboard accurate every ten minutes.
  4. Treat each retransmission as a brand-new purchase.

Answer & Explanations

Correct answer: A

A.

Share one destructive manual cursor between unrelated alerting and archival applications. The scenario is: At Oakcrest Mobility live tracking and reporting consume the same event source. This undermines the mechanism: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions. Instead: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

B.

Use a pie chart to prove one numeric factor causes another. This concerns another issue: At Pinewood Retail analysts compare campaign spend with customer acquisitions. In the stated case—At Oakcrest Mobility live tracking and reporting consume the same event source—reject: Share one destructive manual cursor between unrelated alerting and archival applications. The safer response is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

C.

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 Oakcrest Mobility live tracking and reporting consume the same event source—reject: Share one destructive manual cursor between unrelated alerting and archival applications. The safer response is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

D.

Treat each retransmission as a brand-new purchase. This concerns another issue: At Silverpoint Banking an event publisher retries after a brief timeout. In the stated case—At Oakcrest Mobility live tracking and reporting consume the same event source—reject: Share one destructive manual cursor between unrelated alerting and archival applications. The safer response is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

Question 917

At Cedarline Media two teams process stream events for different dashboards. Which design or Azure data approach best fits this requirement?

  1. Add validation and a quarantine destination for records failing an agreed data quality rule.
  2. Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.
  3. Choose a bar chart for comparing distinct categories with a common quantitative scale.
  4. Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing.

Answer & Explanations

Correct answer: B

A.

Add validation and a quarantine destination for records failing an agreed data quality rule. This addresses a different situation: At Meadowfield Retail some supplier feeds contain negative quantities. The present case is: At Cedarline Media two teams process stream events for different dashboards. The relevant action here is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

B.

Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications. This works because: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions. The scenario is: At Cedarline Media two teams process stream events for different dashboards. Verify the outcome by: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

C.

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 Cedarline Media two teams process stream events for different dashboards. The relevant action here is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

D.

Separate real-time alert processing from slower historical archival so urgent actions do not wait for nightly warehousing. This addresses a different situation: At Pineport Healthcare medical equipment signals abnormal temperatures. The present case is: At Cedarline Media two teams process stream events for different dashboards. The relevant action here is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

Question 918

At Cedarline Media two teams process stream events for different dashboards. The team proposes this approach: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications. Which technical principle explains the choice?

  1. A hot streaming path reacts promptly while the cold path can consolidate history for deeper analysis.
  2. Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions.
  3. A warehouse supports curated structured models and analytic queries over integrated business entities.
  4. A measure is evaluated under the report's current filter context while a calculated column is stored per row after refresh.

Answer & Explanations

Correct answer: B

A.

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 Cedarline Media two teams process stream events for different dashboards. The actual mechanism is: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions.

B.

Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions. This principle supports the intervention: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications. The relevant scenario is: At Cedarline Media two teams process stream events for different dashboards. Verify the result by: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

C.

A warehouse supports curated structured models and analytic queries over integrated business entities. That explains a separate situation: At Silvercrest Commerce executives compare sales performance across regions. The current case is: At Cedarline Media two teams process stream events for different dashboards. The actual mechanism is: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions.

D.

A measure is evaluated under the report's current filter context while a calculated column is stored per row after refresh. That explains a separate situation: At Silverlake Services managers compare revenue by selected region. The current case is: At Cedarline Media two teams process stream events for different dashboards. The actual mechanism is: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions.

Question 919

At Cedarline Media two teams process stream events for different dashboards. After implementing this approach—Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications—which result would most directly confirm success?

  1. Send synthetic purchases across a five-minute interval and verify the window aggregate resets as designed.
  2. Relate fictional sales facts to products and dates and verify filters affect the intended totals.
  3. Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.
  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.

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 Cedarline Media two teams process stream events for different dashboards. Use this acceptance check instead: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

B.

Relate fictional sales facts to products and dates and verify filters affect the intended totals. This tests a separate situation: At Harborbank Retail executives need sales dashboards sharing one definition of revenue. The observed case is: At Cedarline Media two teams process stream events for different dashboards. Use this acceptance check instead: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

C.

Run two test consumer groups and confirm each sees the intended events without resetting the other's offset. This tests the targeted action: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications. The reason is: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions. The reported case is: At Cedarline Media two teams process stream events for different dashboards.

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 Cedarline Media two teams process stream events for different dashboards. Use this acceptance check instead: Run two test consumer groups and confirm each sees the intended events without resetting the other's offset.

Question 920

At Cedarline Media two teams process stream events for different dashboards. Which shortcut most directly threatens the intended data outcome?

  1. Share one destructive manual cursor between unrelated alerting and archival applications.
  2. Append duplicate transactions on every network retry without comparing event IDs.
  3. Treat an Event Hubs namespace as a permanent SQL warehouse with relational joins.
  4. Present categories as an unlabeled geographic heatmap with no location meaning.

Answer & Explanations

Correct answer: A

A.

Share one destructive manual cursor between unrelated alerting and archival applications. The scenario is: At Cedarline Media two teams process stream events for different dashboards. This undermines the mechanism: Partitioned event ingestion supports parallel consumers while independent groups track their own reading positions. Instead: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

B.

Append duplicate transactions on every network retry without comparing event IDs. This concerns another issue: At Silverbrook Logistics pipelines reattempt delayed shipment messages. In the stated case—At Cedarline Media two teams process stream events for different dashboards—reject: Share one destructive manual cursor between unrelated alerting and archival applications. The safer response is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

C.

Treat an Event Hubs namespace as a permanent SQL warehouse with relational joins. This concerns another issue: At Harborcrest Transport thousands of vehicles emit location updates. In the stated case—At Cedarline Media two teams process stream events for different dashboards—reject: Share one destructive manual cursor between unrelated alerting and archival applications. The safer response is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

D.

Present categories as an unlabeled geographic heatmap with no location meaning. This concerns another issue: At Cedarbank Logistics supervisors compare delivery counts among depots. In the stated case—At Cedarline Media two teams process stream events for different dashboards—reject: Share one destructive manual cursor between unrelated alerting and archival applications. The safer response is: Choose event partitions and consumer groups to scale ingestion and allow independent downstream applications.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests