You have two lakehouses named Lakehouse1 and Lakehouse2. Lakehouse1 contains a table FactSales that is partitioned by a column named CustomerID. You need to create a shortcut to the FactSales table in Lakehouse2. The shortcut must only connect to data for CustomerID 100. What should you do?

• A. As you create the shortcut, select the CustomerKey=100 folder under the FactSales folder in Tables.
• B. Create a copy of the table filtered to CustomerID 100.
• C. Apply a SQL view with a WHERE clause.
• D. Create a view on Lakehouse2.

Answer: (A)

When a table is partitioned, each partition is stored in its own folder under the table’s Tables section. Creating a shortcut that points directly to the specific partition folder for CustomerKey 100 makes the shortcut inherently scoped to that subset of data. In practice, you navigate to the FactSales table, then select the folder corresponding to CustomerKey=100, and create the shortcut there. Any queries using this shortcut will only access data for CustomerID 100, avoiding exposure to other partitions and improving performance through partition-level pruning.

Other options wouldn’t achieve the same direct, built-in scoping. Copying the table would duplicate data instead of providing a shortcut. A view (on Lakehouse2) or a view with a WHERE clause could filter data, but they add an extra object and don’t bind the shortcut itself to the partition, making the access control and data path less straightforward.