Indeed, one of the reasons normalisation is such a Big Deal to relational bigots like me is that it makes SQL's querying tools much more useful and versatile.
If someone knows about set-theory and the ideas behind query-languages, knowing SQL isn't a deal breaker, it's just a nice to have.
It sucks, but it's what we have for now.
Also: If you can read the SQL book two days earlier and answer these questions in a reasonable amount of time - sounds like an insta-hire to me. There's certainly nothing so hard about SQL that you couldn't do that - but some people who spend a lot of time working with databases seem to find the climb insurmountable.
Once you grasp that conceptually, SQL generally executes left-to-right, it's easier.
In (almost) all cases, a subquery with an extra `where` clause will have equal performance to a `having` clause in the main query.
See the final example in: http://en.wikipedia.org/wiki/Having_(SQL)
If someone came to me and I asked them to write fizzbuzz, an answer of the form "I would google if-thens and modulo and print statements" would be a pretty obvious no-hire.