Depends who you ask, as there are different types of "Architects", under "Solution Architect", "Business Architect", "Technical Architect",...
For me, I only care about the technical part of it, meaning:
- Translating requirements into technical specifications
- Designing the application modules and their relationships
- Selecting the languages, libraries and frameworks allowed in the project
- Full stack technical documentation
- Designing and implementation of the continuous deployment infrastructure
- Having an overall picture how all modules come together
- Taking part in the development team as senior coder
Those were just a few examples. Of course, the roles one takes are very dependent on team size and type of customer.
However not all architects are made alike. Meaning while I consider critical that one has a foot in both worlds, architecture and coding, in many enterprise companies that isn't the case.
Moreover usually descriptions like "Solution Architect" and "Business Architect" tend to be alias to roles like "Product Owner" or "Project Manager".