Two-minute data freshness from Azure SQL requires DirectQuery connectivity

Get or connect to data
Answer Correct answer: A — DirectQuery reads DB1 at query time, keeping the model current within the two-minute bound.

You plan to create a Power BI semantic model named Model1 that will contain data from an Azure SQL database named DB1. Model1 must show updated data within two minutes of the data being updated in DB1. You need to select a connectivity mode for the connection to DB1. What should you choose?

  1. DirectQuery Correct Answer
  2. live connection
  3. import
directquery connectivity near real time azure sql source

Community Votes

A
100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

DirectQuery sends each visual query straight to DB1, so any committed change is visible the moment a report visual re-queries — the only listed mode that can guarantee sub-2-minute freshness continuously.

Model1 will read from Azure SQL database DB1 and must reflect data changes within two minutes, so the connectivity mode must show current source data without dependence on scheduled refresh cycles.

Choosing import plus frequent refresh — even Premium's 48 refreshes a day average one every 30 minutes, and no import schedule can approach a two-minute staleness bound.

Community Discussion (4 comments)

Minh2712 👍 1 Selected: A
DirectQuery, as the model requires near real-time refresh.
Anloindian123 👍 1 Selected: A
DirectQuery is best. 2 minutes is very close to real-time
NadeemSalam 👍 2 Selected: A
DirectQuery is the right option as we need to refresh data every 2 minutes.
Pitxunet 👍 1 Selected: A
It seems the most appropriate solution for having the data updated all the time. No point in using import if we need to refresh the model every two minutes

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

DirectQuery keeps the data in DB1 and translates visual interactions into source queries. Whenever a report user opens or interacts with a page, the current state of DB1 is read, so updates appear well within two minutes — typically instantly after a query executes. No import schedule can promise continuous two-minute freshness, and Microsoft's guidance positions DirectQuery precisely for near-real-time needs like this.

Why the Other Options Are Wrong

Live connection (B) attaches a report to an existing published model rather than defining connectivity to DB1 itself, and it inherits whatever freshness that model has — there is no model yet, since Model1 is being planned. Import (C) loads a snapshot at refresh time; with scheduled refresh granularity in minutes-to-hours and refresh overhead on the source, it cannot satisfy a two-minute service level.

Community Comment Notes

Every comment agrees on DirectQuery, citing the near-real-time requirement. One comment notes there is no point using import when the model must be current within two minutes, which captures the core reasoning.

Official Reference

https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-about

Related Analysis

You have a Power BI semantic model that contains the followi

S-Grade

Note: This question is part of a series of questions that pr

A-Grade

You are configuring a Power BI report for accessibility as s

S-Grade

Practice All PL-300 Questions

Access 116 questions with complete answers and detailed explanations.

View Full PL-300 Practice Test →

← Back to PL-300 Study Guide