Fabric Analytics Engineer (DP-600) · Free practice question 9 of 12
Diagnosing fallback with TABLETRAITS
Some report pages built on a Direct Lake on SQL analytics endpoint model are slower than expected, and you suspect that certain tables use DirectQuery fallback. Which DAX query shows the fallback reason for each table?
- A.EVALUATE TABLETRAITS()
- B.EVALUATE INFO.VIEW.TABLES()
- C.EVALUATE COLUMNSTATISTICS()
- D.EVALUATE SUMMARIZECOLUMNS('Sales'[Region])
Show answer and explanation
Correct answer: A. EVALUATE TABLETRAITS()
Why: Running EVALUATE TABLETRAITS() returns a DirectLakeFallbackInfo column that gives the fallback reason for each table, with None meaning the table runs in Direct Lake mode. INFO.VIEW.TABLES returns table metadata, COLUMNSTATISTICS returns column statistics such as cardinality, and a SUMMARIZECOLUMNS query only returns data.
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
- Calculated columns in Direct Lake models
- Default lakehouse rules for notebooks
- Opening PBIP projects without a pbip file
- Detect data changes in incremental refresh