Which of the following scenarios would not be suited to using a Group By parameter?

• A. Calculating the perimeter of a property.
• B. Calculating the total area of parks for each neighborhood in a city.
• C. Calculating the total sales in dollars of inventory items by product category.
• D. Calculating the total number of users who logged on to a system this month, broken down by day.

Answer: (A)

Group By is used to create aggregated results by grouping input features according to an attribute, then applying an aggregate function (sum, count, average, etc.) within each group. This makes sense when you want a summary per category, neighborhood, day, or other grouping.

Calculating the perimeter of a property is a per-feature measurement. It yields one value for each property and doesn’t require combining multiple features into groups. Using a Group By here would force artificial grouping and won’t provide a meaningful per-property perimeter, so it’s not suited.

The other scenarios illustrate meaningful groupings: total park area by neighborhood (summed within each neighborhood), total sales by product category (summed per category), and total user logins by day (counted or summed per day). These all rely on producing a summary for each group, which is exactly what Group By advances.