This standard Developers answer is that an Architect should also be coding. But it's a kind of Developer that puts technology first. But I tend to disagree. Yes it's beneficial to have some coding skills, in order to be able to review the code.
But the only thing an Architect does is bring together the business requirements with the implementation. And in our case the code. If you have a seriously complex system, you cannot be coding and doing Architecture at the same time, cause you're operating at too many different abstraction levels.
Instead you should be able to rely on the Developers. They should be able to describe the aspects of the implementation, and how it fits in the business requirement that you have pointed out to them. What technology is chosen is the Architects decision, but to come to that decision he has to do research or use past experience. That doesn't mean he doesn't talk to the Developers, or let them investigate a specific technology to see whether the Architecture really works.
