Fabric Analytics Engineer (DP-600) · Free practice question 8 of 12
Calculated columns in Direct Lake models
In a Direct Lake on SQL analytics endpoint semantic model, a modeler tries to add a calculated column that concatenates City and Country in the Customer table, but the option isn't available. How should the requirement be met?
- A.Switch the model to the large semantic model storage format
- B.Add the column with a calculation group
- C.Set the Direct Lake behavior property to DirectQueryOnly
- D.Add the column to the Customer Delta table upstream, for example with a notebook or pipeline, and refresh the model
Show answer and explanation
Correct answer: D. Add the column to the Customer Delta table upstream, for example with a notebook or pipeline, and refresh the model
Why: Direct Lake on SQL analytics endpoints doesn't support calculated columns or calculated tables that reference Direct Lake tables, so data preparation such as adding derived columns belongs upstream in the Delta tables. After the column exists in the table, a refresh exposes it to the model. The storage format and fallback settings don't enable calculated columns, and calculation groups modify measures rather than add columns.
More free Fabric Analytics Engineer (DP-600) questions
- Reviewing access in the catalog Secure tab
- Shortcut caching for cross-cloud egress
- 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
- Diagnosing fallback with TABLETRAITS
- Default lakehouse rules for notebooks
- Opening PBIP projects without a pbip file
- Detect data changes in incremental refresh