This is another vague question I couldn't handle well.
He said that if the production application is hung, how do you find out what caused the problem?
Rong: I check CPU, if CPU is busy... (He interrupted: "suppose CPU is not busy.")
Rong: I will check memory usage, if ...(He interrupted: "suppose not memory used up.")
Rong: I will check if there is I/O blocking ...(He interrupted "suppose not because of I/O blocking.")
Rong: That's my way to analyse issue, I will rule out something to ...
(He interrupted "ok, let's suppose it's I/O issue, but it's million line code application,
and could be thousands of part involves I/O, how do you solve the problem?)
Rong: For this huge application, troubleshooting needs deep understanding of the codes.
(He said: suppose you know the code very well, and suppose you wrote the code yourself.)
I thought for a while and cannot answer. (I guess he has a specific answer, but I just cannot spot it.)
He: it's ok, let's move on to next question.
Do you have any idea about what he want? And this is also a Indian. I tend to conclude that either Indian think in a way different from mine, or he intended to mess up the interview, because all interviewers who throw me a vague question and refuse to give further hints are Indians.