Which language should you use in Dataflow Gen2 to transform data when ingesting from Azure SQL Database into a Lakehouse?

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 language should you use in Dataflow Gen2 to transform data when ingesting from Azure SQL Database into a Lakehouse?

Explanation:
The language used to transform data inside Dataflow Gen2 is the Power Query M language. When you ingest from Azure SQL Database into a Lakehouse, you define a dataflow and apply shaping and cleaning steps—renaming columns, changing data types, filtering rows, merging with other sources—through M. DAX is a calculation language for data modeling in BI tools, not for ETL-style transformations in dataflows. SQL could be used to pull data from the source, but the in-flow transformations you define are done with M, not SQL. XML isn’t used for these dataflow transformations either. So the best choice is M.

The language used to transform data inside Dataflow Gen2 is the Power Query M language. When you ingest from Azure SQL Database into a Lakehouse, you define a dataflow and apply shaping and cleaning steps—renaming columns, changing data types, filtering rows, merging with other sources—through M. DAX is a calculation language for data modeling in BI tools, not for ETL-style transformations in dataflows. SQL could be used to pull data from the source, but the in-flow transformations you define are done with M, not SQL. XML isn’t used for these dataflow transformations either. So the best choice is M.

More Multiple Choice Questions
Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy