A team uses Snowflake as its operational analytics store and wants the same data available in Microsoft Fabric as Delta tables in OneLake that Spark and the SQL analytics endpoint can query. The replica should follow source changes closely, and the team wants a managed capability rather than a pipeline they have to build and operate. Which Fabric capability best meets these requirements?
- AA OneLake shortcut from the Lakehouse to the Snowflake warehouse, so Fabric queries read the Snowflake tables in place without any replication.
- BA Spark structured streaming job that continuously reads from Snowflake and writes Delta tables into the Lakehouse for the analytics endpoint.
- CFabric mirroring for Snowflake, which replicates the Snowflake database into OneLake as Delta tables that Spark and the SQL analytics endpoint can query. Correct
- DA scheduled Dataflows Gen2 refresh that reads Snowflake and writes the tables into the Lakehouse once an hour for downstream queries.
Why A is wrong: Shortcuts point at storage locations and supported item types, not a Snowflake compute warehouse, so this does not surface Snowflake tables as queryable OneLake Delta tables.
Why B is wrong: A structured streaming job could replicate the data, but it is a pipeline the team must build, tune, and operate, which contradicts the requirement for a managed capability with low overhead.
Why C is correct: Fabric mirroring supports Snowflake as a source and continuously lands the data in OneLake as Delta tables, giving the managed, near-real-time replica the requirement asks for without a hand-built pipeline.
Why D is wrong: An hourly Dataflows Gen2 refresh lags the source by up to an hour and is a schedule the team manages, so it neither follows changes closely nor removes the operational burden mirroring eliminates.