Hugo Kornelis (1/28/2013)
Tough I applaud the effort to create questions on new SQL2012 functionality, I really see nothing positive about this question.
Absolutely. QotD gets quite a mixed bag of good & poor questions, the poor ones due to the usual; ambiguities, poor phrasiology etc. However, if I were to vote on the worst QotD ever, this one would get it.
I know it's not everyone's "thing" but my choice is to always select my answer without running any queries or reading any material first - if I get it wrong or have to guess, then that's the pompt to go reading and/or experimenting. The only way you could answer this question in that way is to have AW2012 Employee table committed to memory.