Fabric Lakehouse SQL Endpoint Capabilities

DP-600 By islever Editorial Last updated

Short answer

A You can read Table3 because the SQL analytics endpoint supports read-only access to managed Delta tables.

Question

You are the administrator of a Fabric workspace that contains a lakehouse named Lakehouse1. Lakehouse1 contains the following tables: Table1: A Delta table created by using a shortcut Table2: An external table created by using Spark Table3: A managed table - You plan to connect to Lakehouse1 by using its SQL endpoint. What will you be able to do after connecting to Lakehouse1?
  1. Read Table3. Correct Answer
  2. Update the data Table3.
  3. Read Table2.
  4. Update the data in Table1.

Key Takeaways

Tests knowledge of SQL endpoint limitations: it is read-only and does not expose Spark-created external tables to T-SQL queries.

Determines read/write access for managed, external, and shortcut tables in a Microsoft Fabric lakehouse via the SQL endpoint. The page establishes that only managed Delta tables are readable through this interface.

Common mistake: Users often select B or D, incorrectly assuming the SQL endpoint supports write operations like updates on managed tables.

Expert Analysis

Why the Answer Is Correct

The SQL analytics endpoint in Microsoft Fabric provides a T-SQL interface specifically for reading data from managed Delta tables within a lakehouse. Table3 is defined as a managed table, making it fully accessible for SELECT operations via the SQL endpoint. Therefore, option A is the correct action.

Why the Other Options Are Wrong

Options B and D are incorrect because the SQL analytics endpoint operates in read-only mode; it does not support INSERT, UPDATE, or DELETE operations. Option C is incorrect because tables created externally using Spark (external tables) are not visible or queryable through the SQL endpoint; they must be accessed via Spark notebooks or dataflows.

Community Comment Notes

Community consensus strongly supports A, with multiple users noting that 'SQL endpoint is read only' and 'External Delta tables... won't be visible'. One user clarified that while managed tables allow reads, updates are prohibited at all levels via this endpoint. Another comment confirmed that external tables require Spark dataframe commands rather than SQL queries.

Official Reference

https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-sql-analytics-endpoint

This link opens the official vendor documentation in a new tab.

Exam Strategy

Always check if the question specifies 'managed' vs 'external' tables when dealing with Fabric SQL endpoints. Remember the golden rule: SQL Endpoint = Read-Only + Managed Tables Only.

Frequently Asked Questions

Can I update managed tables using the SQL endpoint?

No, the SQL analytics endpoint is strictly read-only. Write operations must be performed using Spark notebooks or dataflows.

Why can't I see external tables in the SQL endpoint?

External tables created via Spark are not registered in the SQL catalog, so they are invisible to the SQL endpoint's T-SQL interface.

More DP-600 FAQ →

Community Votes

A
100%

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

Discussion 26 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 26

  1. conie 👍 60 Answered A
    B & D is out as you can’t update a table in lakehouse using SQL endpoint as this is read only. You will need to use spark or dataflows. C is out because when you create external table using spark, you can see the table from the lakehouse but you can’t see the table from SQL endpoint let alone ready. A is the answer, as I was able to see and read a managed table using SQL Endpoint
  2. stilferx 👍 4 Answered A
    IMHO, the answer is A. updates are prohibited at all. reading spark external table is a big no-no. Link: https://www.linkedin.com/pulse/use-shortcuts-instead-external-tables-reference-data-fabric-popovic/
  3. a_51 👍 4 Answered A
    A is correct, D is not. SQL endpoint is read-only. https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-sql-analytics-endpoint
  4. Sara0724 👍 3 Answered A
    The SQL analytics endpoint operates in read-only mode over lakehouse Delta tables. External Delta tables created with Spark code won't be visible to the SQL analytics endpoint. https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-sql-analytics-endpoint
  5. XiltroX 👍 3
    With SQL endpoint in a Lakehouse you can only read tables not update them. But that only applies to managed tables. External tables have to be read by logging inside the Lakehouse and using Spark dataframe commands.
Show 21 more comments
  1. BrandonPerks 👍 3
    I can confirm it is A. I manually went to my fabric tenant to investigate.
  2. 282b85d 👍 2
    Managed tables are fully controlled by the database system. These tables typically allow both read and write operations, including updates, through SQL endpoints. After connecting to Lakehouse1 using its SQL endpoint, you will be able to: - Read Table3 (A) - Update the data in Table3 (B) So, the correct options are:
  3. Chrys941 👍 2 Answered A
    D is completely wrong is not typically feasible through a shortcut in SQL endpoint setup. B Generally Supported but depends on the SQL endpoint permissions for such operations A you should be able to read data from table3 since it is a managed table and such operations are standard through Sql Endpoints
  4. Fermd 👍 2 Answered A
    The right answer is A. A managed table, it is stored within the Fabric storage and becomes immediately accessible through the SQL endpoint upon connection. D is not right becouse tables created using shortcuts might not be immediately accessible through the SQL endpoint for updates.
  5. b65ecca 👍 2 Answered A
    External Delta tables created with Spark code won't be visible to the SQL analytics endpoint. https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-sql-analytics-endpoint So C is out. B and D are also out since with a SQL endpoint we can't update tables.
  6. mtroyano 👍 2 Answered A
    Options B and D are incorrect because an endpoint does not support DML operations. Option C is not correct because the external tables are not accessible from the endpoint. The correct answer is A, the managed tables can be read from the connection point.
  7. Kang_24 👍 2 Answered A
    SQL Endpoint cannot update table --> B & D are outed. Table 2 is a external table so it won't be displayed in SQL Endpoint view --> C is outed.
  8. rmeng 👍 2 Answered A
    C is not correct because the external tables are not accessible from the endpoint. B & D is out of question cause as SQL endpoint is read only.
  9. cafb698 👍 1
    The SQL analytics endpoint operates in read-only mode over lakehouse Delta tables. You can only read data from Delta tables using the SQL analytics endpoint. They can save functions, views, and set SQL object-level security. Hence, B & D are out. External Delta tables created with Spark code won't be visible to the SQL analytics endpoint. Use shortcuts in Table space to make external Delta tables visible to the SQL analytics endpoint. Hence C is out. Correct Answer: A
  10. Ahmadpbi 👍 1
    D is the correct answer. In a lakehouse, the tables that can be edited using SQL endpoints are primarily Delta tables. These tables are specifically designed to be compatible with SQL analytics endpoints, allowing you to perform various SQL operations such as querying, creating views, and applying SQL security. Other table formats like Parquet, CSV, and JSON are not directly editable through SQL endpoints; they need to be converted to Delta format first.
  11. jass007_k 👍 1
    Correct option is A) as Lakehouse SQL endpoint is read only B) and D) are incorrect as Lakehouse SQL endpoint is read only Option C) is also incorrect as external tables created using spark in lakehouse are not visible to Lakehouse SQL endpoint Refer this document for option c: https://learn.microsoft.com/en-us/fabric/data-engineering/notebook-visualization
  12. wojciech_wie 👍 1
    Answer A is correct Using SQL Endpoint we can only READ tables, so B & D is out Moreover for now we can't read external tables using SQL enpoint (https://community.fabric.microsoft.com/t5/General-Discussion/Fabric-SQL-end-point-not-showing-external-delta-tables/m-p/3475969)
  13. theseon 👍 1 Answered C
    C "The SQL analytics endpoint operates in read-only mode over lakehouse delta tables" https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-sql-analytics-endpoint
  14. contactodonuno 👍 1 Answered A
    The right answer is A. A managed table, it is stored within the Fabric storage and becomes immediately accessible through the SQL endpoint upon connection.
  15. Parth_Mehta 👍 1
    We can read table 1 and table 3 not table 2 and can't write any of them.... so ans will be A
  16. IshtarSQL 👍 1 Answered D
    D is correct because you can update a Delta table.
  17. Momoanwar 👍 1 Answered A
    End point dont modify and not read external
  18. Aruuu6 👍 3 Answered A
    A is answer
  19. GPerez73 👍 2 Answered A
    A is correct. Tested!
  20. TashaP 👍 2
    A. Read Table 3
  21. Rakesh16 👍 1 Answered A
    Read Table3 (A managed table)

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.

Submitted for moderation before publishing. Keep it helpful and respectful.

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