AZ-305 Practice Question 95: OneLake Shortcuts Analyze in Place
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 10 · question 5 of 10
A company already has 40 TB of Parquet files in an Azure Data Lake Storage Gen2 account that several existing Spark and reporting pipelines depend on and cannot be moved. The analytics team is adopting Microsoft Fabric and wants Fabric notebooks, Power BI, and the SQL analytics endpoint to all query that same data as though it lived in a Fabric lakehouse, with any new rows written by the existing pipelines visible immediately. The design must avoid duplicating the 40 TB of data and avoid building a scheduled copy job.
What should you include in the design?
Show answer and explanation
Answer:
A OneLake shortcut is a reference to data stored in another location, including an existing Azure Data Lake Storage Gen2 container, rather than a copy. Fabric compute engines such as Spark notebooks, the SQL analytics endpoint, and Power BI read through the shortcut directly against the source data on every query, so newly written rows from the existing pipelines are visible without any duplication or scheduled copy step.
Option B is wrong because a nightly copy activity duplicates the 40 TB, introduces storage cost and staleness between runs, and is exactly the scheduled copy job the requirement rules out. Option C is wrong because it only exposes the data to Power BI through Synapse serverless SQL, not to Fabric notebooks or the Fabric SQL analytics endpoint, so it fails the requirement that all three surfaces query the same data through Fabric. Option D is wrong because geo-redundant storage protects against a regional outage; it does not create a Fabric-native way to query the data and does not address duplication or scheduling at all.