Which dynamic management view can help identify memory-heavy columns loaded into memory in a Direct Lake model?

Which dynamic management view can help identify memory-heavy columns loaded into memory in a Direct Lake model?

• A. $System.DISCOVER_STORAGE_TABLE_COLUMN_SEGMENTS
• B. $System.DISCOVER_STORAGE_TABLES
• C. $System.DISCOVER_MEMORY_GRANTS
• D. $System.DISCOVER_MEMORY_USAGE

Answer: (A)

The test is about detecting memory usage at the column level when a Direct Lake model loads data. Direct Lake can bring data into memory for query processing, and to see which parts of a table are consuming memory, you need visibility down to the column segments. The dynamic management view that reports memory usage by each column segment is the one designed for this: it shows details at the column level so you can identify which columns are loading heavy memory. That’s why this view is the best fit. Other options focus on different aspects: the table-level metadata view lists tables but not memory by column; the memory grants view shows how memory is allocated for queries, not which columns are in memory; and the general memory usage view reports overall usage rather than per-column storage footprint.

The test is about detecting memory usage at the column level when a Direct Lake model loads data. Direct Lake can bring data into memory for query processing, and to see which parts of a table are consuming memory, you need visibility down to the column segments. The dynamic management view that reports memory usage by each column segment is the one designed for this: it shows details at the column level so you can identify which columns are loading heavy memory. That’s why this view is the best fit.

Other options focus on different aspects: the table-level metadata view lists tables but not memory by column; the memory grants view shows how memory is allocated for queries, not which columns are in memory; and the general memory usage view reports overall usage rather than per-column storage footprint.