Which storage mode should the detailed fact table use to enable real-time queries against the source?

Unlock all questions

This demo includes only 20 questions. Upgrade to access hundreds of questions, flashcards, exam simulations, and disable ads.

Full question bankExam simulationsFlashcards
From $25.99Unlock all

Prepare for the Fabric Analytics Engineer Associate Test with comprehensive materials. Explore flashcards, multiple choice questions, and detailed explanations. Get ready for your success!

Multiple Choice

Which storage mode should the detailed fact table use to enable real-time queries against the source?

Explanation:
DirectQuery is the storage mode that keeps the detailed fact table in the source system and pushes queries down to that source at query time. This setup lets you run real-time or near real-time queries against the live data, since you’re not loading a static snapshot into the model. In contrast, importing brings a static copy into the modeling environment, so changes in the source aren’t visible until you refresh. Dual can mix modes for different tables, but it doesn’t inherently provide real-time querying for every query on the table. None isn’t correct because there is a mode that enables real-time access.

DirectQuery is the storage mode that keeps the detailed fact table in the source system and pushes queries down to that source at query time. This setup lets you run real-time or near real-time queries against the live data, since you’re not loading a static snapshot into the model.

In contrast, importing brings a static copy into the modeling environment, so changes in the source aren’t visible until you refresh. Dual can mix modes for different tables, but it doesn’t inherently provide real-time querying for every query on the table. None isn’t correct because there is a mode that enables real-time access.

More Multiple Choice Questions
Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy