Which file format and shortcut location enable Fabric SQL endpoint queries?

DP-600 By islever Editorial Last updated

Get data Query and analyze data

Short answer

DE Create the shortcut in the Tables section and store the S3 sales data in Delta format so the lakehouse SQL endpoint can query it as a table.

Question

You have a Fabric tenant that contains a lakehouse. You plan to query sales data files by using the SQL endpoint. The files will be in an Amazon Simple Storage Service (Amazon S3) storage bucket. You need to recommend which file format to use and where to create a shortcut. Which two actions should you include in the recommendation? Each correct answer presents part of the solution. NOTE: Each correct answer is worth one point.
  1. Create a shortcut in the Files section.
  2. Use the Parquet format
  3. Use the CSV format.
  4. Create a shortcut in the Tables section. Correct Answer
  5. Use the delta format. Correct Answer

Key Takeaways

Tests Fabric SQL endpoint storage requirements and the shortcut-placement trap: Files-section shortcuts expose raw objects, while Parquet or CSV data in Tables cannot be surfaced as queryable tables.

This DP-600 question asks which two actions let you query Amazon S3 sales files from a Fabric lakehouse SQL endpoint. The page establishes that you must create the shortcut in the Tables section and use the Delta format, because the SQL analytics endpoint queries only Delta tables.

Common mistake: The most common wrong answer is B, D — assuming Parquet files pointed to from the Tables section are automatically recognized as a queryable table, but the SQL endpoint exposes only Delta tables.

Expert Analysis

Why the Answer Is Correct

Fabric lakehouse SQL analytics endpoint is a read-only relational endpoint over Delta tables, not over arbitrary files. To query S3 sales files through that endpoint, the S3 shortcut must land in the Tables section and the underlying files must be Delta so OneLake metadata synchronization can expose a table object. Creating a Delta shortcut in Tables lets Fabric recognize schema and table metadata for SQL queries. This matches the documented behavior that only Delta tables are available in the SQL analytics endpoint. Options D and E together satisfy both the shortcut-location requirement and the format requirement.

Why the Other Options Are Wrong

A shortcut in the Files section (A) is valid for Spark notebooks or data engineering reads but does not create a table that the SQL endpoint can query. Parquet (B) is a columnar format supported by Spark and Power BI, but a Parquet shortcut in Tables is not automatically treated as a Delta table and cannot be queried through the SQL analytics endpoint. CSV (C) is even less suitable because it is row-based, lacks schema enforcement, and is not a Delta table format. Therefore B and C fail on format, and A fails on shortcut placement.

Community Comment Notes

Felgas argued that to use the SQL endpoint you must create the shortcut in Tables and that "the file also needs to be in the delta format to be recognised as a managed table"; they warn a Parquet file added to Tables will not be recognized as a table object. Blue_MSBI quoted Microsoft guidance that "Only the tables in Delta format are available in the SQL analytics endpoint" and noted Parquet and CSV cannot be queried there. woliveiras reported testing Delta files in AWS S3 and creating a shortcut in Tables, which supports D and E. By contrast, d47320d and 282b85d voted for B and D, claiming Parquet in Tables is recognized as Delta, but that conflicts with the documented SQL-endpoint restriction and the tested experience above.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

When a Fabric requirement mentions the SQL endpoint, eliminate Files-section shortcuts and non-Delta formats immediately; only Tables-section shortcuts over Delta data produce a queryable table. Treat community answers that suggest Parquet in Tables as a trap unless the official SQL-endpoint documentation has changed.

Frequently Asked Questions

Why can't a Parquet shortcut in the Tables section be queried via the SQL endpoint?

The Fabric SQL analytics endpoint exposes only Delta tables. A Parquet shortcut in Tables is not materialized as a Delta table, so it remains a file object and cannot be queried through the SQL endpoint.

Why is a Files-section shortcut insufficient for SQL endpoint queries?

Files-section shortcuts expose raw objects for Spark or notebook reads but do not create table metadata. The SQL analytics endpoint therefore cannot see the S3 objects as queryable tables.

More DP-600 FAQ →

Community Votes

BD
56%
DE
44%

56% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 32 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 30 of 32

  1. Felgas 👍 31
    Answer is DE. To be able to use the SQL Endpoint you need to create the shortcut in the Tables section. The file also needs to be in the delta format to be recognised as a managed table. If you try to add a parquet file to the tables section, it will not be recognised as a table object and you won't be able to query it.
  2. d47320d 👍 22
    B,D are the correct answers, since the Parquet file format within S3, and the pointing to it via a lakehouse Table shortcut, allows the shorcut to be recognized by Fabric as a Delta table and hence provide access to the SQL endpoint. Explanation: As per the provided links: "If the target of the shortcut contains data in the Delta\Parquet format, the lakehouse automatically synchronizes the metadata and recognizes the folder as a table". It is stated that S3 contains sales data files, that is files not tables. Besides, delta tables are not supported in S3. So the file format needs to be either CSV or Parquet, leading us to choose the latter for all the reasons stated in other comments. So creating a shortcut in Table section that points to S3 Parquet files, will allow Fabric to recognise it as a Delta table, which in turn enables the SQL endpoint.
  3. woliveiras 👍 5
    D and E. Tested. You can turn delta files available in your AWS Service and create a shortcut here.
  4. woliveiras 👍 4
    If you need just query, as they mentioned. Parquet (read in parallel) and shortcut in the table solve this problem. you don't need delta.
  5. Nicofr 👍 4
    delta format like the default format for Fabric
Show 25 more comments
  1. moodi86 👍 3
    Delta uis supported: https://blog.fabric.microsoft.com/en-us/blog/public-preview-of-onelake-shortcuts-to-s3-compatible-data-sources?ft=All ""If your data is already in the Delta Lake format, create your shortcut in the Tables section of your lakehouse. This will allow your table shortcut to benefit from metadata synchronization across Fabric engines, letting you use this structured data where tables are used in Fabric.""
  2. IshtarSQL 👍 3
    B: You should use a columnar file format such as Parquet or ORC (Optimized Row Columnar). These formats are highly optimized for analytical queries and provide efficient storage and query performance. D: In the Tables section of your lakehouse, you define virtual tables that represent external data sources. These virtual tables can be backed by data stored externally in formats such as Parquet or ORC in Amazon S3.
  3. Blue_MSBI 👍 3
    "Only the tables in Delta format are available in the SQL analytics endpoint. Parquet, CSV, and other formats can not be queried using the SQL analytics endpoint. If you don't see your table, you will need convert it to Delta format." https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-overview
  4. 282b85d 👍 3
    To effectively query sales data files stored in an Amazon S3 bucket using the SQL endpoint in your Fabric tenant's lakehouse, you should: B. Use the Parquet format D. Create a shortcut in the Tables section
  5. 6d1de25 👍 3
    B- Because Parquet format is supported in Amazon S3 https://learn.microsoft.com/en-us/azure/data-factory/format-parquet D- Because you need to use the Shortcuts as managed portion of the lakehouse.
  6. sharnav 👍 3
    why not 'A'? The shortcut will be reading files from the S3 instead of tables.
  7. Estratech 👍 2
    For querying sales data files using the SQL endpoint with files stored in an Amazon S3 storage bucket, I recommend the following two actions: File Format: Choose the Apache Parquet file format for the sales data files. Parquet is a columnar storage file format that is optimized for complex queries and is efficient for use with SQL queries due to its data compression and encoding schemes. It supports complex data types and is ideal for large datasets1. Shortcut Creation: Create a shortcut in the Lakehouse Explorer under the Tables section. When you create a shortcut to a Delta formatted table under Tables in Lakehouse Explorer, it will automatically register it as a table, enabling data access through Spark, SQL endpoint, and the default semantic model2. These actions will help ensure efficient querying and easy accessibility of your sales data within the Fabric tenant’s lakehouse environment.
  8. gfors 👍 2
    I just tested this. Have a S3 bucket with a CSV and a parquet file. Created a shortcut, and tried it to place it in tables. That was not successful. It asked me to move it to Files. So answer to the first part must me A. Create a shortcut in the Files section Both csv and parquet can be loaded as table. That is part of the job. The result is that both will result in a delta table, and it is delta tables that can be viewed in SQL endpoints. So the second answer must be E. Use the delta format.
  9. sraakesh95 👍 2
    B - Parquet is a widely accepted format for efficient querying. Delta files are usually good with Spark based querying rather than SQL endpoint based querying. While delta format is highly useful for some usecases like time traveling, incremental loads and data versioning, for simple and high efficiency querying, parquet would be the best. D - A shortcut can be created in the Tables section of the Lakehouse and not the files section.
  10. estrelle2008 👍 2
    I read a requirement to query with SQL analytic endpoint. I'm sure, that recommended Microsoft solution then is: create a shortcut in the Tables section in Delta 'format', to benefit from transactional operations and schema evolution. The File section is more suitable for unstructured data that doesn't require full SQL querying. Parquet and csv lack the support of schema evolution.
  11. stilferx 👍 2
    IMHO, D & E Because of that: Shortcuts aren't supported in other subdirectories of the Tables folder. If the target of the shortcut contains data in the Delta\Parquet format, the lakehouse automatically synchronizes the metadata and recognizes the folder as a table. https://learn.microsoft.com/en-us/fabric/onelake/onelake-shortcuts#lakehouse
  12. 554b579 👍 2
    S3 does support delta parquet: https://aws.amazon.com/blogs/big-data/introducing-native-delta-lake-table-support-with-aws-glue-crawlers/ Answer: DE
  13. Momoanwar 👍 2
    I think its BD. Delta is not file format, lakehouse will read parquet files and create delta table.
  14. Pegooli 👍 2
    ChatGPT is saying amazon S3 supports both Delta and Parquet files
  15. Ziggler 👍 2
    CSV is best if the data is not that large
  16. Azure_2023 👍 1
    - E and D E. Use the delta format - Choosing Delta format is most suitable for complex environments that benefit from features like ACID transactions, schema enforcement, and historical data tracking. This choice is particularly effective in lakehouse architectures where maintaining data integrity and supporting complex queries are paramount. D. Create a shortcut in the Tables section - Given the structured nature of Delta format files and the need to perform SQL queries, creating a shortcut in the Tables section is most beneficial. This approach allows the SQL endpoint to efficiently query the data using table semantics, leveraging the optimizations provided by the lakehouse.
  17. bar_ser 👍 1
    https://learn.microsoft.com/en-us/fabric/onelake/onelake-shortcuts#lakehouse Within this link, it's clear that you can link to Parquet. "If the target of the shortcut contains data in the Delta\Parquet format, the lakehouse automatically synchronizes the metadata and recognizes the folder as a table"
  18. bar_ser 👍 1
    S3 does not support delta. https://productresources.collibra.com/docs/collibra/latest/Content/Catalog/S3/ref-S3-supported-file-types.htm So E is not an option
  19. OLGIS 👍 1
    I guess MS documentation says Delta rather than Parquet? https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-sql-analytics-endpoint
  20. Mhunity 👍 1
    B OR E (Use the Parquet format or Use the delta format) D Create a shortcut in the Tables section
  21. Ziggler 👍 1
    There is no mention of how big the data is , using CSV will be better if the data is small
  22. Amine_spiegel94 👍 1
    SQL Endpoint you need to create the shortcut in the Tables section.
  23. NRezgui 👍 1
    D. Create a shortcut in the Tables section. E. Use the delta format
  24. Egocentric 👍 1
    B.use parquet format D.create a shortcut in the table section
  25. azure_bimonster 👍 2
    D and E seem correct choices

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Fabric Deployment Pipeline Folder Structure Behavior

S-grade

Accessing OneLake Shortcuts in Fabric Notebooks

S-grade

Direct Lake Fallback to DirectQuery with Row-Level Security

S-grade

Displaying All Rows in Power BI Python Visuals

S-grade

Practice All DP-600 Questions

Access 115 questions with complete answers and detailed explanations.

View Full DP-600 Practice Test →

← Back to DP-600 Study Guide