So far I agree with what has mostly been said. The things I look for in a candidate are 1) their experience up to the point they apply, 2) have they worked with a team before?, 3) how truthful was their resume when I interviewed them, and yes, I'll ask you questions about each technology you list.
With that said, don't be afraid to say "I don't know, as I never ran into that situation/scenario when I worked in that technology". But don't stop there, explain why my question wasn't relevant, what scenario/situation did you use the technology in? Even if you don't fully understand why your scenario wasn't relevant, explain to me how you used the technology and let me come up with why it wasn't relevant. Maybe it was because you were just the low-man on the totem pole, and the more experienced users were in charge of 99% of the work in that technology (and you simply fixed the bugs).
Be open about your experiences (the good and the bad). When you start talking about the bad, end your experience with what you learned from the bad experience. We've all had bad experiences, all I care about is you learned something from it to help prevent that experience from coming around again.
Lastly, show that you are always willing to learn/continue to learn. Our industry changes yearly (sometimes monthly). You need to stay on top of it. Tell them what websites you visit to get news about our industry, RSS feeds you subscribe to, etc. (Hint: If you aren't doing this, start now!)
If you reflect all of the above, you have a good chance getting hired by me.