Fabric Analytics Engineer (DP-600) · Free practice question 3 of 12
Open mirroring landing zone for custom sources
A software vendor's application tracks inserts, updates and deletes in its own database engine, which Fabric doesn't support as a mirroring source. The vendor wants that change data to be continuously merged into Delta tables in Fabric without building pipelines. What should the vendor use?
- A.A Dataflow Gen2 with incremental refresh
- B.An external OneLake shortcut to the application database
- C.An open mirrored database, with the application writing change files to its landing zone
- D.Metadata mirroring of the application's catalog
Show answer and explanation
Correct answer: C. An open mirrored database, with the application writing change files to its landing zone
Why: Open mirroring lets any application write change data, in the format the open mirroring specification defines, to the landing zone of a mirrored database. Fabric then merges the inserts, updates and deletes into Delta tables. Dataflows require scheduled refreshes, shortcuts can't target a database engine, and metadata mirroring only references data that already exists in a supported catalog.
More free Fabric Analytics Engineer (DP-600) questions
- Reviewing access in the catalog Secure tab
- Shortcut caching for cross-cloud egress
- 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