I think the question was centered around achieving the certification and first architect role. I would say that anyone who has achieved 5-7 years IT experience in both a infrastructure systems support role as well as development, has a bit more additional business experience [or worked as a Business Analysis] and can demonstrate design and BPM capabilities can become an architect.
Obviously anyone can become certified as an Architect whether it be an SCEA or Zachman Certified, it makes no difference. All that indicates is that you have the basic knowledge and possible skillset. This will potentially qualify you to approach a future employer about becoming a Solution Architect or Application Architect but usually no more, depending upon whether or not you have more of a systems background or a development background. Commonly, you will find SharePoint Architects at this tier. You're not quite in a realm where I would think you could use the term Software Architect confidently, as you would need to demonstrate that your design, leadership and development activity as delivered to market a viable executable package that is commonly run by serveral clients. This IASA's domain [International Association of Software Architects ---
http://www.iasahome.org], though their certification process is geared much more toward a true Enterprise Architecture, complete with balancing Business Architecture and Technical Architecture. Software Architects doing a better job on delivering the entire package of a true, full-breasted Enterprise Architect's skill-sets?? Go figure. Does any of this equip you to become an Enterprise Architect? Not by itself.
This is the area where having 10-15 years of experience, deep development time and a PhD would normally apply, so it is not likely. Why is this the case? Because you are tasked with designing the framework for and leading the development and/or deployment of every system in your domain, which can be the entire enterprise in many an instance. Think of this group of individuals as being Lt. Col responsible for leading special operations units and battalions [300–1000] that have just been promoted to full bird Colonels now responsible for entire brigades [2000–5000]. That is up to 5x's the number of people that his/her decisions affect, and that doesn't even include operational effectiveness as well as other ancillary fallout. So plans have to be meticulous and well-designed in order to extract instructions that can be delivered down the food chain for systems personnel and programmers at the bottom to execute on them in a fashion that delivers value for the business with minimal hiccups. You have to have proverbial "eyes in the back of your head" to do this kind of work as you tend to be the CIO's arms, legs and heart. Think a certification alone will do this? NOT ON YOUR LIFE.
To be sure, the SCEA is still one of the most admirable credentials to have in the industry bar none. But it only develops Software Architects, largely from a design stand point. Fortunately for you, you have done the prudent thing of completing the SCJA, and SCJP, laying the groundwork for being a proper Software Engineer and Developer. I would say, complete the skills development by getting the SCEA, and volunteer for any projects that you can at the office, in addition to joining an Open Source project or two. From there, I would look at CCDA {Cisco Design Associate}, SCSA [SNIA Storage Architect --
http://www.snia.org/education/certification/scsa/], ITIL foundations, CBAP to develop your Business Analysis skills, OCEB for Business Process Modeling {essentially a more in depth extension of CBAP, focused almost solely on the modeling}, SOA -- ok redundant, but just make sure you stay up to date on it, PMP or Prince2 [if you get in a in pinch, it sounds bush, but pick up the Project+ to show SOME kind of project management training], Six Sigma [be sure to learn Business Modeling in Excel -- it will save your life, especially if you have BI projects in a Financial Services firm. pm me if you need a book], TOGAF or Zachman for Enterprise Architecture understanding and finally CTIA from IASA does a good job of bridging the Business Architect side with Technical Architect side, as previously mentioned. Oh, and just for SnG, you probably want to complete an MBA as well as this is slowly starting to become en vogue for Enterprise Architects.... just make sure your doing this WHILE you remain or progress up the food chain in similar roles. Sounds like a lot? Maybe, but it will not be as cumbersome as you think, considering many of the topics covered in these programs are things you already do, you will just be obtaining the knowledge behind why you do them.
Just remember, if you want to be an Enterprise Architect, it is about the Business, not the program, which means you have to know how every group of systems can be effectively leveraged [both cost and performance]. This is more than just the last application you delivered, so it means more than just leading developers. If that is all you want to do, finish the SCEA, learn about databases and just keep coding. An opportunity will come open. There's nothing wrong with stopping at Software Architect --- in fact, you just may want to consider it heavily.