I'm a little concerned by your question. At first blush, I'd suggest something along the lines of "please describe the influences of the midwest prairie forms on modern arts and crafts designs".
Removing tongue from cheek, I would suggest what Chris did above. Provide the candidate with an opportunity to interact with you and your team on the design of an architecture relevant to your work. If you don't feel equipped to judge their competence based on seeing them solve problems instead of canned problems, you NEED to get somebody else involved in the interview. Or else take a page from the book of Joel and Jeff and scratch the term "architecture" and start looking for competent software engineers.
In my opinion, ability to design or "architect" is a skill, not a set of knowledge. Asking them a bunch of questions like "what are the performance ramifications of using J2EE vX vs J2EE vY" or "which is better, CORBA or RMI" is just going to make you look silly.
