Where should you create a table shortcut when querying lakehouse data stored in S3 via the SQL endpoint?

• A. Files section
• B. Pipelines section
• C. Tables section
• D. Dataflows section

Answer: (C)

When you want to access lakehouse data stored in S3 through a SQL endpoint, you expose that data as a table-like object that SQL can query. This is done by creating a table shortcut, which acts as a logical reference to the external data, so queries can treat it as a table without importing the data. The appropriate place to define and manage these table-level references is the Tables section, which is specifically built to hold table definitions and shortcuts used by SQL endpoints. The Files section is for raw file management, not for defining table-level metadata. Pipelines and Dataflows are for data movement and transformation, not for registering table shortcuts used by SQL queries.