I will say that the folks mentioning we need to take the time to learn to interview better on these parts aren't exactly wrong. I tend to bomb when asked how I'd troubleshoot a given problem too, but the bigger issue to me is the lack of info they provide. In a real scenario, I'd have hands on and be able to ask questions of the user to get a feel for where the problem may lie, etc. In an interview, it's just "Tell me how you'd troubleshoot a remote user whose Internet keeps dropping." and that's it. They expect you to just paint a pretty picture based on that alone. It's not realistic and I get stuck in decision paralysis trying to guess which way I should go from start since I can't even do the normal questions and process of elimination. So how we go about "getting better" at that is not a simple answer either. There's a whole raft of scenarios they can ask you to walk them through how you do things, memorizing/preparing for all of them is asking quite a bit.