I'm sorry, but if you don't know the answer to this question, you're not familiar enough with agile to write intelligently about it. If you're going to write about a technique, you should at least know the basic concepts, whether you agree with them or not. And pretending ignorance for effect doesn't add much to the discussion.
Personally, I think one can learn enough about agile to apply it usefully without ever learning what a "scrum master" does. Maybe this goes back to the discussion of process vs. best practices.
Maybe. But it's a pretty critical role, and if no one on the team is filling it (or even aware that the role is needed), you're losing out on most of the benefit of agile. To the point where it's not really what people mean when they refer to the Agile process.
I'm sorry, but if you don't know the answer to this question, you're not familiar enough with agile to write intelligently about it. If you're going to write about a technique, you should at least know the basic concepts, whether you agree with them or not. And pretending ignorance for effect doesn't add much to the discussion.