Which syntax should you use to read data from a Lakehouse shortcut named ResearchProduct in Lakehouse1?

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 syntax should you use to read data from a Lakehouse shortcut named ResearchProduct in Lakehouse1?

Explanation:
Accessing data from a Lakehouse shortcut is done through the catalog as a registered table, so you query it using Spark SQL with its fully qualified name. By running a SELECT * FROM Lakehouse1.ResearchProduct, you rely on the metastore to resolve the shortcut to the underlying data, keeping the access consistent with other tables and letting Spark manage the path and format behind the scenes. The other options try to read from a raw path or use non-standard external_table syntax, which bypasses the Lakehouse shortcut or isn’t valid Spark API for reading a Lakehouse table. Using the fully qualified table name in a SQL query is the straightforward, correct way to read that Lakehouse shortcut.

Accessing data from a Lakehouse shortcut is done through the catalog as a registered table, so you query it using Spark SQL with its fully qualified name. By running a SELECT * FROM Lakehouse1.ResearchProduct, you rely on the metastore to resolve the shortcut to the underlying data, keeping the access consistent with other tables and letting Spark manage the path and format behind the scenes. The other options try to read from a raw path or use non-standard external_table syntax, which bypasses the Lakehouse shortcut or isn’t valid Spark API for reading a Lakehouse table. Using the fully qualified table name in a SQL query is the straightforward, correct way to read that Lakehouse shortcut.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy