a. Help all of its employees move to AZ where they can enjoy
a lower cost of living?
b. Fire all of its employees and hire replacements in AZ?
c. Something else?
Because if they're going with option B, wow. 1. Use the best option available, but
2. We provided example code in multiple languages for the
best one that's widely available
I wouldn't ever use something like FizzBuzz to assess a candidate. It would be more of "here's a mostly finished sample application with a corresponding SQL file, add this feature (e.g. a search bar for a blog) and fix any (intentionally introduced) security bugs you find".
They would be evaluated based on how successfully they complete the main task, and if they have an eye for finding/patching vulnerabilities, that's a bonus that can be used as a secondary selector if a lot of candidates pass. If no one does, it won't be used against them.
That's how I'd approach it, personally. Something specific to the kind of work we're doing, but abstract enough to be approachable without a lot of insider knowledge.