Build the foundations
Gather functional needs, constraints, data classifications and non-functional requirements.
Loading your career tools…
Make architecture trade-offs visible and defensible.
Gather functional needs, constraints, data classifications and non-functional requirements.
Compare compute, data, networking and integration options with explicit trade-offs.
Design identity, resilience, recovery and cost controls; test important assumptions.
Present a decision record and migration plan with risks, ownership and measurable acceptance criteria.
Your checklist stays in this page session only. It is a self-check, not a skills assessment.
Start with architecture fundamentals and implementation evidence. Senior credentials are useful after real design experience; check prerequisite credentials such as Azure Administrator for Microsoft’s architect award.
Helps cloud engineers connect services into reliable designs. A useful architecture foundation before taking on larger AWS systems.
Before booking: AWS recommends around one year designing cloud solutions.
For architects designing Google Cloud solutions and explaining business and technical trade-offs.
Before booking: Best after hands-on design and operational experience on Google Cloud.
For experienced architects translating business requirements into Azure infrastructure designs.
Before booking: Advanced IT operations and Azure design experience is recommended.
Best for architects already making decisions across complex AWS environments. Supports architecture discussions that span several teams and applications.
Before booking: AWS recommends 2+ years designing and implementing AWS solutions.
Review the official source for fees, assessment format, prerequisites and award/renewal requirements. Guidance reviewed 13 September 2026.
Design a resilient order platform with an architecture diagram, cost assumptions, recovery plan and five decision records.
Use these original practice scenarios to structure your answers. They are not leaked exam questions or an employer’s interview script.
A strong answer covers: Clarify actual business impact and service objectives, then compare realistic availability/cost options.
A strong answer covers: Explain dependencies, waves, data consistency, validation, cutover and rollback.