DP-600 Maintain a Data Analytics Solution Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  SELECT * FROM $System.DISCOVER_SESSION_STATISTICS

  Why it's wrong here

  This view provides information about active sessions and current resource consumption but does not offer granular details regarding column-level storage. While useful for identifying which users are active, it cannot help determine which specific data structures within the semantic model are responsible for high memory usage or inefficient storage engine performance.

• ✓

  SELECT * FROM $System.DISCOVER_STORAGE_TABLE_COLUMN_SEGMENTS

  Why this is correct

  This DMV provides detailed information about the segments of data stored for each column, including their size and compression characteristics. It is the primary tool for diagnosing memory pressure issues in the VertiPaq engine. Analyzing this data allows engineers to identify high-cardinality columns that should be optimized or removed to improve performance.

• ✗

  SELECT * FROM $System.MDSCHEMA_MEASURES

  Why it's wrong here

  The MDSCHEMA_MEASURES view lists the definitions and properties of measures within the model but provides no information about physical storage or memory consumption. It is helpful for documenting the model's logic but serves no purpose when investigating hardware resource utilization or storage engine bottlenecks during query execution or data processing.

• ✗

  SELECT * FROM $System.DISCOVER_CALC_DEPENDENCY

  Why it's wrong here

  This DMV is used to map the dependencies between different objects in the model, such as which measures rely on specific columns. While helpful for impact analysis and understanding model complexity, it does not provide any metrics related to the physical size of the data or the memory footprint of individual columns.