FWIW, the article said this is a question they use for a senior full stack role, not a frontend specialist role. With that in mind, the question does seem a bit badly formulated. For example, why would you ask about tags that you know through calibration that nobody will answer satisfactorily? And if you're already gathering signals about frontend specialization fluency by discussing web vitals, accessibility and other topics that would already establish competence, then why continue to get into these trivia style questions? Seems like a bit of a waste of time.
One potential problem with this approach of trivia checkbox ticking is that you could be selecting for "mini me" candidates, meaning that you're overfitting for the skillset you already have. For example, maybe the candidate is "full stack" from a primarily backend background, but you're formulating questions like this because you have a frontend background. But then they might seem less qualified than a mid-level frontend-only person because the interview was focusing on frontend, even though stronger expertise on backend would complement your current skill pool better.
One potential problem with this approach of trivia checkbox ticking is that you could be selecting for "mini me" candidates, meaning that you're overfitting for the skillset you already have. For example, maybe the candidate is "full stack" from a primarily backend background, but you're formulating questions like this because you have a frontend background. But then they might seem less qualified than a mid-level frontend-only person because the interview was focusing on frontend, even though stronger expertise on backend would complement your current skill pool better.