This workshop ends with a challenge whose answer is hidden under a ribbon in the guide. Search before pulling it: getting it wrong and then correcting teaches more than reading a solution. The sandbox lives for two hours, precisely to give you that time. Access remains read-only, you cannot damage anything.
Tip
The rule that explains almost every GROUP BY error: every column in the SELECT must either be in the GROUP BY or wrapped in an aggregate. If a column is not, ask yourself which single value it should take for the whole group; if you cannot answer, neither can PostgreSQL, and it is right to refuse. And before writing the query, ask the question the other way round: "my answer will have one row per what?" That "per what" is your GROUP BY.
sql
group by
count
sum
aggregation
challenge
SQL: count and group with COUNT and GROUP BY · MonPremierLab