the question would have been alright in 2005 when that was an issue

so the only people to get the question right were people have fully patched sql 2005