Roadmap for Architecture [closed]

Question

Ok, I am a developer for 6 years now and I came from a hater to an enthusiast about technology.
I am a senior developer, almost all focused in web applications, asp.net, quite experienced and very, very focused in develop myself.
I come to a crossroads in my area, I want to become an Architect, not an analyst or a project manager. I like to get my hands dirty, to actually do things, and I, well,... have to admit it, that I am a little lost about what I should've already known, and what i should be studying, in order to enter in that field.
So here comes the question:

What an Architect should be proficient in?

Answer 1

Sales.

Architecture is all about selling a potential solution to folks who (a) trust you and (b) believe that what you're saying will work.

After that, you have to deliver.

But you'll never get to deliver if you can't sell the vision.

Answer 2

Understanding various trade-offs in different solutions, using different solution ideas, and getting both the big picture and being able to handle questions about some little details that may turn out to be a big deal with some plans.

Do you know how to build a large-scale web application? Do you know what priorities you value in a solution,e.g. ease of maintenance, scalability, reliability, simplicity, and performance to name a few? How well can you justify one approach over another? How many different design patterns have you seen or used? Those are some of the questions I'd consider if I was going to go down the road of becoming an architect.