A naive junior shouldn't stump them, but it really does happen all the time. If all they have to do is ask what it takes to flip it to a "yes", the same information is communicated. The only thing ever truly at stake was someone's ego.
My answer won't be "no, we can't do it." It'll be a form of "we have to use this alternate method to get to the goal, how does that affect your budget?"
Frankly, that's toddler level thinking.
While there are certainly people who are rich enough and spoiled enough that they have probably never been meaningfully refused anything in their lives, that produces terrible people, and absolutely everyone needs to learn how to accept being told "no" when "no" is the correct answer (or a reasonable one).
And then I'd sit down and bust my ass trying to find out if it was feasible or not. :)
If it wasn't, we could always come back with a lesser approach and people seemed to be happy with that. ("It turns out Android doesn't widely support [feature x] so we recommend [feature y] instead.")
Nonsense. The client that made me a job offer as CTO listed the fact that I wasn’t afraid of saying ‘no’ to unreasonable requests or unrealistic deadlines one of the things he valued the most in my work. He had plenty of experience with contractors that would always say yes, promise anything and then find themselves unable to deliver because they underestimated the complexity of the task.
Saying no is what makes a professional so valuable. Of course you always want to offer alternative approaches.
"no, I won't be able to make it in time" would be "I can confidently deliver in time if I have X, and we save Y and Z for later."