View source for Azure Cosmos DB Mirroring for Fabric

&larr; Back to [[DP-420: Azure Cosmos DB Developer Specialty|DP-420 Terminology Reference]]

'''Category:''' Integration & Analytics

'''Summary:''' Near real-time replication of Cosmos DB data into Microsoft Fabric's OneLake.

== Overview ==
Azure Cosmos DB Mirroring for Microsoft Fabric continuously replicates Azure Cosmos DB data into Microsoft Fabric's OneLake in near real time, storing it in open Delta format, and making the data available for unified analytics, reporting, and cross-workload querying within Fabric (including via Direct Lake) without a separate ETL/copy pipeline, complementing (and in newer scenarios, replacing) the older Synapse Link/Spark connector approach.

== More Info & Links ==
* [https://learn.microsoft.com/en-us/fabric/database/mirrored-database/azure-cosmos-db Microsoft Learn: Mirroring Azure Cosmos DB in Microsoft Fabric]

== DP-420 Style Practice Questions ==
'''Q1.''' What does Azure Cosmos DB Mirroring for Microsoft Fabric provide?
* A. Near real-time replication of Cosmos DB data into Fabric's OneLake for unified analytics without a separate ETL pipeline
* B. A backup mechanism for disaster recovery only
* C. A way to enable multi-region writes
* D. A tool for managing RBAC permissions

'''Q2.''' When choosing between Azure Cosmos DB Mirroring and the Spark connector for analytics, what is a key consideration?
* A. Mirroring offers simpler, near real-time replication into Fabric OneLake without custom Spark code
* B. The Spark connector is required for any read access to Cosmos DB
* C. Mirroring only supports the MongoDB API
* D. The Spark connector cannot write data back to Cosmos DB

== Answer Key ==
''Answers are listed at the very end so you can attempt the questions first.''

* '''Q1 (Azure Cosmos DB Mirroring for Fabric):''' A. Near real-time replication of Cosmos DB data into Fabric's OneLake for unified analytics without a separate ETL pipeline — Mirroring continuously replicates data into OneLake for analytics, avoiding the need for custom ETL.
* '''Q2 (Azure Cosmos DB Mirroring for Fabric):''' A. Mirroring offers simpler, near real-time replication into Fabric OneLake without custom Spark code — Mirroring provides a low-code, near real-time path into Fabric OneLake, while the Spark connector offers more custom control via code.

----
''DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB — term detail page''

[[Category:DP-420 Terminology]]
[[Category:Integration & Analytics]]