The final level — and deliberately not a certification target. Architect level is less about day-to-day configuration and more about high-level design and business strategy: translating what an organization needs into a technology architecture. At this altitude, the proof is a portfolio of design documents and decisions, not an exam score.
The retired program had no multiple-choice exam and no CLI — it ran like a doctoral defense. I keep its three stages as the bar my portfolio exercises aim for:
| Stage | What happens |
|---|---|
| 1. Application | Submit your CV, CCDE credential, and evidence of ~10 years of architecture-level experience. Cisco's program committee decides if you may proceed. |
| 2. Architecture challenge | You receive a realistic, ambiguous business scenario from a fictional large enterprise (think: "global retailer post-merger, aggressive cloud mandate, flat IT budget"). Over several months you produce a complete architecture proposal. |
| 3. Board defense | You present and defend your architecture live in front of a board of existing Cisco architects. They probe trade-offs, push back on costs, change requirements mid-session — exactly like a real executive steering committee. |
There is no published topic blueprint like CCNA/CCNP — these are the competency areas the board evaluates. Treat each as a long-term development goal.
No simulators here. The practice field is paper, whiteboards and meeting rooms. These exercises build the exact muscles the board tests.
Take a public RFP or case study (banks and governments publish them) and write the full architecture response: requirements analysis, three options with trade-offs, recommendation, cost model, migration plan.
Present an architecture to senior colleagues with one instruction: attack it. Budget cuts mid-presentation, surprise compliance requirements, "why not just use the cloud for everything?"
Two fictional companies merge: incompatible IP plans, different security postures, duplicated data centers, one year to integrate. Produce the target architecture and the 4-phase migration roadmap.
For every major design you've ever done (including the CCIE labs from Level 4), retro-write an ADR: context, options considered, decision, consequences. Publish sanitized ones in this repo.
The Open Group's enterprise architecture framework — the shared vocabulary of the architect profession. TOGAF certification is a worthwhile parallel credential.
PaidArchitects live in diagrams: capability maps, layered views, migration timelines. Executive-readable beats technically-exhaustive.
Free (draw.io)TCO and ROI spreadsheets. If you can't model 5-year cost of two options, you can't defend a recommendation.
You own itCisco Validated Designs — free, deep reference architectures for every domain. Read them like an architect: ask "why did they choose this?"
FreeToastmasters, conference talks, internal brown-bags. The board defense is a speaking exam wearing a technology costume.
Mostly freeCase-study books and an MBA-lite reading list (strategy, finance for non-finance managers). Future CTOs read what CEOs read.
Books