Which action would you take to reference external Gen2 data in the lakehouse without copying it?

Which action would you take to reference external Gen2 data in the lakehouse without copying it?

• A. Create a shortcut.
• B. Create a Dataflow that queries it directly.
• C. Copy the data into a staging folder.
• D. Create a notebook to read it.

Answer: (A)

Creating a shortcut is the way to reference external Gen2 data in the lakehouse without copying it. A shortcut acts as a metadata pointer that links to the data’s real location in Gen2, letting the lakehouse surface and query the data as if it were stored nearby while the actual data stays in place. Because you aren’t duplicating the data, you keep a single source of truth, avoid extra storage, and ensure the data remains up to date with its source. When queries run, the engine reads directly from the external Gen2 location through the pointer, enabling seamless analysis without moving data. The other options either copy the data, which violates the requirement, or don’t establish a persistent lakehouse-level reference that supports governance and reuse.

Creating a shortcut is the way to reference external Gen2 data in the lakehouse without copying it. A shortcut acts as a metadata pointer that links to the data’s real location in Gen2, letting the lakehouse surface and query the data as if it were stored nearby while the actual data stays in place. Because you aren’t duplicating the data, you keep a single source of truth, avoid extra storage, and ensure the data remains up to date with its source. When queries run, the engine reads directly from the external Gen2 location through the pointer, enabling seamless analysis without moving data. The other options either copy the data, which violates the requirement, or don’t establish a persistent lakehouse-level reference that supports governance and reuse.