Which Fabric Shortcuts Use the OneLake Cache?
You have an Azure Data Lake Storage Gen2 account named storage1 and an Amazon S3 bucket named storage2.
You have the Delta Parquet files shown in the following table.
You have a Fabric workspace named Workspace1 that has the cache for shortcuts enabled. Workspace1 contains a lakehouse named Lakehouse1. Lakehouse1 has the following shortcuts:
A shortcut to ProductFile aliased as Products
A shortcut to StoreFile aliased as Stores
A shortcut to TripsFile aliased as Trips
The data from which shortcuts will be retrieved from the cache?
Community Insight
The question tests the two hard limits of OneLake shortcut caching — supported cloud source types and the 1 GB per-file cap — and the trap is assuming every shortcut in a workspace with caching enabled will be cached.
OneLake shortcut caching in Microsoft Fabric applies only to GCS, S3 and S3-compatible shortcuts, and individual files larger than 1 GB are never cached. Because Products points to ADLS Gen2 and Trips points to a 2 GB file, only the Stores shortcut to StoreFile is served from the cache.
Option B (Products and Store) is the most common wrong pick: learners assume that because Workspace1 has cache for shortcuts enabled, the ADLS-backed Products shortcut is cached, ignoring that caching is not supported for ADLS Gen2 shortcuts at all.
Community Discussion (61 comments)
- Files must be under 1 GB to be eligible for caching. - Cached data is refreshed when accessed and expires after 24 hours of inactivity. - Caching applies to shortcuts in lakehouses with cache enabled.
- Cached files have a retention period of 24 hours. - Individual files greater than 1 GB in size aren't cached.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The cache for shortcuts setting in Workspace1 only benefits shortcuts whose backing store is a supported caching source: Google Cloud Storage, Amazon S3, and S3-compatible storage, as documented for OneLake shortcuts. Products points to ProductFile on storage1, an Azure Data Lake Storage Gen2 account, so it is never cached; Trips points to TripsFile on storage2 (S3) but at roughly 2 GB it exceeds the individual-file ceiling of 1 GB, so it is excluded as well. Stores points to StoreFile on the S3 bucket storage2 and is only about 25 MB, so it satisfies both the supported-source and size conditions and is retrieved from the cache. Therefore Stores alone qualifies, which is option C.Why the Other Options Are Wrong
Option E and option A both include Trips, but a file larger than 1 GB is explicitly not cached regardless of which cloud it lives on, so any choice containing Trips fails. Options B and D include Products, which targets ADLS Gen2 — a source that shortcut caching does not support — so no amount of workspace-level enablement makes ProductFile cacheable. Option B is therefore doubly wrong for readers who reason only about file size and forget the source-type restriction, and option D is wrong on both counts since Products is unsupported while Stores and Trips are not being selected correctly.Community Comment Notes
Tuki93 quoted the documentation directly: "Shortcut caching is currently only supported for GCS, S3 and S3 compatible shortcuts" and added that files untouched for 24 hours are purged. exnaniantwort emphasized that ADLS does not need a cache, concluding "Products is incorrect", while henryphchan and Adriel_1996 reached the same C verdict by citing the 1 GB cap on TripsFile. On the other side, prabhjot and 5dcd3a8 argued for B by stressing S3 and ADLS shortcut support generally, and gretito_g's breakdown — "ProductFile is in storage1 (Azure) → not cached" — is the clearest reason the ADLS-backed shortcut drops out.Official Reference
Exam Strategy
When a Fabric question mentions caching or performance features, first check the supported source types, then the size and retention limits — enablement at the workspace level never overrides a feature's platform restrictions.
Frequently Asked Questions
Why isn't the Products shortcut cached when the workspace has caching enabled?
Products targets ProductFile on ADLS Gen2, and shortcut caching is only supported for GCS, S3 and S3-compatible shortcuts, so workspace enablement does not apply to it.
Why is the Trips shortcut excluded from the cache even though it uses Amazon S3?
TripsFile is about 2 GB, and individual files greater than 1 GB are never cached, so only smaller S3 files such as StoreFile are stored in the cache.