Accessing OneLake Shortcuts in Fabric Notebooks

DP-600 By islever Editorial Last updated

Short answer

A Use spark.read.format("delta").load("Files/ResearchProduct") to read data from the shortcut as a file path in the notebook.

Question

Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question. Overview - Contoso, Ltd. is a US-based health supplements company. Contoso has two divisions named Sales and Research. The Sales division contains two departments named Online Sales and Retail Sales. The Research division assigns internally developed product lines to individual teams of researchers and analysts. Existing Environment - Identity Environment - Contoso has a Microsoft Entra tenant named contoso.com. The tenant contains two groups named ResearchReviewersGroup1 and ResearchReviewersGroup2. Data Environment - Contoso has the following data environment: • The Sales division uses a Microsoft Power BI Premium capacity. • The semantic model of the Online Sales department includes a fact table named Orders that uses Import made. In the system of origin, the OrderID value represents the sequence in which orders are created. • The Research department uses an on-premises, third-party data warehousing product. • Fabric is enabled for contoso.com. • An Azure Data Lake Storage Gen2 storage account named storage1 contains Research division data for a product line named Productline1. The data is in the delta format. • A Data Lake Storage Gen2 storage account named storage2 contains Research division data for a product line named Productline2. The data is in the CSV format. Requirements - Planned Changes - Contoso plans to make the following changes: • Enable support for Fabric in the Power BI Premium capacity used by the Sales division. • Make all the data for the Sales division and the Research division available in Fabric. • For the Research division, create two Fabric workspaces named Productline1ws and Productline2ws. • In Productline1ws, create a lakehouse named Lakehouse1. • In Lakehouse1, create a shortcut to storage1 named ResearchProduct. Data Analytics Requirements - Contoso identifies the following data analytics requirements: • All the workspaces for the Sales division and the Research division must support all Fabric experiences. • The Research division workspaces must use a dedicated, on-demand capacity that has per-minute billing. • The Research division workspaces must be grouped together logically to support OneLake data hub filtering based on the department name. • For the Research division workspaces, the members of ResearchReviewersGroup1 must be able to read lakehouse and warehouse data and shortcuts by using SQL endpoints. • For the Research division workspaces, the members of ResearchReviewersGroup2 must be able to read lakehouse data by using Lakehouse explorer. • All the semantic models and reports for the Research division must use version control that supports branching. Data Preparation Requirements - Contoso identifies the following data preparation requirements: • The Research division data for Productline1 must be retrieved from Lakehouse1 by using Fabric notebooks. • All the Research division data in the lakehouses must be presented as managed tables in Lakehouse explorer. Semantic Model Requirements - Contoso identifies the following requirements for implementing and managing semantic models: • The number of rows added to the Orders table during refreshes must be minimized. • The semantic models in the Research division workspaces must use Direct Lake mode. General Requirements - Contoso identifies the following high-level requirements that must be considered for all solutions: • Follow the principle of least privilege when applicable. • Minimize implementation and maintenance effort when possible. Which syntax should you use in a notebook to access the Research division data for Productline1?
  1. spark.read.format(“delta”).load(“Files/ResearchProduct”) Correct Answer
  2. spark.sql(“SELECT * FROM Lakehouse1.ResearchProduct ”)
  3. spark.sql(“SELECT * FROM Lakehouse1.Tables.ResearchProduct ”)
  4. external_table(ResearchProduct)

Key Takeaways

Shortcuts are file system mounts, not managed tables; thus you must use spark.read.format("delta").load() with the Files/ path rather than SQL SELECT statements.

Learn the correct PySpark syntax to read Delta format data from a OneLake shortcut in Microsoft Fabric, distinguishing between filesystem paths and registered tables.

Common mistake: Learners often choose the SQL option (B) because they assume shortcuts automatically register as tables in the Lakehouse catalog, which is incorrect for raw data access via notebooks.

Expert Analysis

Why the Answer Is Correct

The correct syntax is A: spark.read.format("delta").load("Files/ResearchProduct"). In Microsoft Fabric, a shortcut acts as a virtual mount point in the OneLake file system. When accessing data directly from a shortcut in a notebook without first creating a managed table or view, you must treat it as a file path. The Files/ prefix is required to reference the OneLake filesystem, and since the source data is in Delta format, specifying format("delta") ensures proper parsing.

Why the Other Options Are Wrong

Options B and C (spark.sql) are incorrect because they attempt to query a table name that does not exist in the Lakehouse catalog. A shortcut is not automatically a table; it is a directory link. Unless a user explicitly creates a table or view pointing to that shortcut, SQL queries will fail with a "table not found" error. Option D is invalid syntax for PySpark in this context.

Community Comment Notes

Many candidates were confused by the distinction between shortcuts and tables. As user MAKI911 noted, "options B and C are incorrect... ResearchProduct is simply a shortcut (folder) pointing to Delta files." Another commenter, user pk07, clarified that "shortcuts do not behave like managed tables... use Files/ path." While some users argued for SQL syntax based on external documentation regarding SQL endpoints, the question specifically asks for notebook code, where direct Spark API access to the file path is the standard method for unregistered data.

Exam Strategy

Always distinguish between 'SQL Endpoints' (which allow querying shortcuts via SQL if configured) and 'Notebooks' (which require explicit Spark API calls). If the question asks for notebook code to read a shortcut directly, look for the Files/ path and spark.read commands.

Frequently Asked Questions

Can I use spark.sql to read a shortcut directly?

No, unless a table or view has been explicitly created in the Lakehouse catalog pointing to the shortcut. Otherwise, use the Files/ path.

Why is the Files/ prefix needed in the load path?

The Files/ prefix identifies the OneLake file system root, allowing Spark to resolve the shortcut location as a directory structure.

More DP-600 FAQ →

Community Votes

A
53%
B
47%

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

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

  1. MAKI911 👍 3 Answered A
    The main reason why options B and C are incorrect is that they assume “ResearchProduct” has already been registered as a table in Lakehouse1. In this scenario, however, “ResearchProduct” is simply a shortcut (folder) pointing to Delta files. Because no managed table has been created for that folder yet, you cannot use SQL syntax like • spark.sql("SELECT FROM Lakehouse1.ResearchProduct") or • spark.sql("SELECT FROM Lakehouse1.Tables.ResearchProduct") to query the data. Instead, you must read directly from the underlying Delta files by referencing the “Files/ResearchProduct” path. That is why option A (spark.read.format("delta").load("Files/ResearchProduct")) is the correct choice in a Fabric notebook.
  2. f0dd605 👍 3 Answered A
    A according to ChatGPT: The question requires accessing Research division data for Productline1 stored in delta format from the lakehouse (Lakehouse1) in a Fabric notebook. Here’s why option A is the correct choice: Delta Format Access in Spark: The data for Productline1 is stored in Delta format, as per the scenario. When working with Delta format in Spark notebooks, the standard way to read data is using spark.read.format("delta").load(<path>). Files/ResearchProduct Path: A shortcut named ResearchProduct has been created in Lakehouse1. In Microsoft Fabric, the Files/ResearchProduct path refers to the shortcut to the Delta Lake storage (storage1), which makes the data available within the lakehouse.
  3. 4b35503 👍 3 Answered B
    REF https://learn.microsoft.com/en-us/fabric/onelake/access-onelake-shortcuts Correct Sintax spark.sql("SELECT * FROM <LH>.<Shortcut_Name>")
  4. pk07 👍 1 Answered A
    The key change is understanding that shortcuts do not behave like managed tables in Spark SQL. To read data from a shortcut you need to use spark.read.format and use Files/ path, since it's a shortcut it behaves like a file in the filesystem. Corrected Answer: A. spark.read.format("delta").load("Files/ResearchProduct")
  5. RickyK 👍 1 Answered C
    If the requirement is "For the Research division workspaces, the members of ResearchReviewersGroup1 must be able to read lakehouse and warehouse data and shortcuts by using SQL endpoints" then the shortcut would need to be created in the "Tables" section.
Show 4 more comments
  1. Jowalkr 👍 1
    Since the file is in Delta format, it should be a straight forward read and I think the answer should be A.
  2. jackjack1 👍 1 Answered A
    Shortcut hasn't been created yet, don't think B would be correct for that reason.
  3. chq23 👍 3 Answered B
    ResearchProduct is a shortcut
  4. 4e5cf3d 👍 1 Answered B
    A is wrong: Table not Files

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

Direct Lake Fallback to DirectQuery with Row-Level Security

S-grade

Displaying All Rows in Power BI Python Visuals

S-grade

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

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