That may not be key for all positions, but for more senior roles, and all roles which are predominantly customer facing, it's absolutely critical.
Being able to say "no" is important, but so is knowing when to say "no" and when to say "yes".
If somebody tries to drag you onto an irrelevant tangent in a meeting, that's when you should say "no". If somebody is talking to you one-on-one and you discover that they actually care about something different than you thought, that's when you should say "yes".
The problem with this scenario is that it pretends to measure a person's ability to say "no" all while giving them no reason whatsoever to actually say "no".
If you want to test a person's ability to say "no", you have to put them in a situation where that's actually the correct move.
In a meeting or presentation, you have a subject and an agenda and many people present who expect you to cover them.
In an interview, it's one-on-one. If the interviewer asks you A, then stops and asks you B, there's no reason not to move to B. If the interviewer is suddenly asking about B, they must want to know about it. There are no other stakeholders present who might care more about A. You didn't even know you were going to be talking about A until a few minutes before!
It's an important skill to be able to say "no" and stay focused on a subject. But this is a shitty test for finding out whether a person has that skill.