This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
A certification doesn't make you an architect. Knowledge and experience does. The SCEA curriculum does cover architecture and non-fucntional requirements well. I recommend you use it as a learning guide and then just don't take the test. It also refers to good books for more information.
You can't just only study to become an architect. The best way to become an architect is to start thinking and acting like one. If you start thinking like one, you will not only start to observe the architects at current work, but will also start acting like one. This is true for the other roles as well. Learn to ask the right questions, look at things from both business and technical perspective, and get a good handle on the 16 key areas.
Proactively apply these key areas and get a well rounded hands-on experience. It is also imperative to focus on the soft skills. So, the combination of all the above will transform you into an architect.