That is, unless they interview at an organization that is much more interested in finding compatible personality for their culture than they are in the person's ability. These organizations exist; I worked for one a year or two back. The candidate I was interviewing as part of a panel had not been asked a coding question to that point, and she was already quite far along in the interview process -- the next step after the panel interview was an offer. No one else really cared; they just wanted someone who would increase headcount while not disrupting the culture and structure of the organization.
So, the people who answer this way, they're just playing a numbers game. They keep going on interviews until they hit an organization like I describe above; at that point, all they need to be hired is to just be agreeable.
Also, most people have figured out how to trial-and-error tweaking existing code. Blank editor window? Nothing. Modifying a bunch of existing code that renders a web page? Surprisingly able.
Try being part of the interview process sometimes; you'll have lots of fun :)
For this particular job configuring routers was not a primary task, but because I had a passing knowledge of Cisco routers I asked a couple of questions since he had brought it up. After 2-3 questions which the candidate couldn't answer, he finally admitted that his experience in 'configuring' Cisco routers consisted of plugging the network cables into the port at the back.