Fabric Analytics Engineer (DP-600) · Free practice question 2 of 12
Shortcut caching for cross-cloud egress
Data engineers repeatedly read the same Parquet files from a Google Cloud Storage bucket through an external shortcut, and the cross-cloud egress charges are growing. The files change only occasionally. What should you configure to reduce egress?
- A.Convert the shortcut into an internal OneLake shortcut
- B.Turn on OneLake availability for the bucket
- C.Enable shortcut caching in the workspace's OneLake settings and choose a retention period
- D.Create a mirrored database for the bucket
Show answer and explanation
Correct answer: C. Enable shortcut caching in the workspace's OneLake settings and choose a retention period
Why: Shortcut caching stores files read through supported external shortcuts, including Google Cloud Storage and Amazon S3, in a workspace-level cache for a retention period of 1 to 28 days, so repeated reads are served from OneLake instead of the remote provider. Internal shortcuts can point only to OneLake locations, OneLake availability is an eventhouse feature, and mirroring targets databases rather than storage buckets.
More free Fabric Analytics Engineer (DP-600) questions
- Reviewing access in the catalog Secure tab
- Open mirroring landing zone for custom sources
- Distinct and conditional counts in KQL
- Converting strings to dates in PySpark
- Warehouse replacements for unsupported types
- Top item value with the INDEX function
- Calculated columns in Direct Lake models
- Diagnosing fallback with TABLETRAITS
- Default lakehouse rules for notebooks
- Opening PBIP projects without a pbip file
- Detect data changes in incremental refresh