Which PowerQuery function should you include in the PowerQuery step to identify the maximum values for numeric columns during profiling?

Which PowerQuery function should you include in the PowerQuery step to identify the maximum values for numeric columns during profiling?

• A. Table.Max
• B. Table.Profile
• C. List.Max
• D. Table.Sort

Answer: (B)

Profiling is about getting a quick summary of each column, including how large numeric values can be. Table.Profile is built for that purpose: it returns a profile table with one row per input column and includes statistics that reveal the range of values, so you can see the maximum value observed in each numeric column along with other helpful metrics. This makes it the most direct way to identify maximum values across numeric columns in a profiling step. The other functions don’t provide a full per-column profile: List.Max would only give the maximum of a single list of values, not a summary across all columns; Table.Max returns the row with the maximum value in a specified column, not a summary of every column’s statistics; Table.Sort just orders rows and doesn’t yield profiling statistics.

Profiling is about getting a quick summary of each column, including how large numeric values can be. Table.Profile is built for that purpose: it returns a profile table with one row per input column and includes statistics that reveal the range of values, so you can see the maximum value observed in each numeric column along with other helpful metrics. This makes it the most direct way to identify maximum values across numeric columns in a profiling step.

The other functions don’t provide a full per-column profile: List.Max would only give the maximum of a single list of values, not a summary across all columns; Table.Max returns the row with the maximum value in a specified column, not a summary of every column’s statistics; Table.Sort just orders rows and doesn’t yield profiling statistics.