Alibaba Cloud Architect Professional study materials
Alibaba Cloud Architect Professional study resources

Alibaba Cloud Architect Professional study plan

Alibaba Cloud Architect Professional · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Cloud Architecture Design

  • Map each of the four domains to its exam weight and write a one-page outline of the architecture-design decisions the exam expects you to justify

  • Sketch three reference architectures from scratch (single-region web tier, multi-tier with managed database, hybrid connectivity) and label every component with its Alibaba Cloud service category

  • Explain aloud, without notes, the tradeoffs between ECS, SLB, and Auto Scaling for a variable-traffic workload

  • List the design questions you would ask a stakeholder before choosing between a single VPC and a multi-VPC topology

Your checkpoint

A 10-15 page personal architecture notes document containing three labeled reference diagrams and a tradeoff table for compute, networking, and storage choices

Week 2

Cloud Architecture Design

  • Design a multi-AZ, highly available three-tier application and document the failure mode each redundancy layer addresses

  • Compare at least four data-tier options (RDS, PolarDB, Tablestore, OSS) against consistency, scaling, and cost criteria

  • Draft a cost and performance comparison for two candidate architectures serving the same workload

  • Identify and correct three deliberately flawed architectures (single points of failure, cross-region latency traps, over-permissioned designs)

Your checkpoint

A written architecture decision record for one workload covering at least two candidate designs, the chosen design, and the rejection rationale for the alternative

Week 3

Cloud Migration and Deployment

  • Inventory a sample on-premises estate and classify each workload as rehost, replatform, refactor, or retire with a stated justification

  • Sequence a migration wave plan across three waves, ordering by dependency and risk

  • Select the appropriate migration tool category for server, database, and object-storage moves and state why each fits

  • Draft a cutover and rollback runbook for one workload, including validation checks and a go/no-go gate

Your checkpoint

A migration plan document for a 10-workload sample estate with wave sequencing, tool selection per workload, and one complete cutover/rollback runbook

Week 4

Cloud Migration and Deployment & Cloud Operations and Optimization

  • Design a landing-zone structure with account/resource hierarchy, VPC segmentation, and centralized logging

  • Specify infrastructure-as-code coverage for a repeatable two-environment deployment and note what must stay manual

  • Define the observability baseline: which metrics, logs, and alerts every deployed workload must ship with

  • Write the acceptance criteria a migrated workload must pass before it is declared production-ready

Your checkpoint

A landing-zone and deployment-standard document plus a production-readiness checklist of at least 15 pass/fail criteria

Week 5

Cloud Operations and Optimization

  • Build an operations runbook for one workload covering incident triage, escalation, and post-incident review

  • Diagnose five given symptom descriptions (latency spikes, throttling, connection exhaustion, disk pressure, cost anomaly) and name the first three diagnostic steps for each

  • Define SLOs and error budgets for two services and derive the alert thresholds from them

  • Produce a cost-optimization review identifying at least six levers (rightsizing, commitment discounts, storage tiering, idle-resource reclamation) with estimated impact

Your checkpoint

An operations package for one workload: runbook, SLO definitions with derived alerts, and a cost-optimization review with quantified savings estimates

Week 6

Cloud Security and Compliance

  • Model a least-privilege identity design covering human roles, service roles, and cross-account access

  • Map data-classification tiers to encryption, key-management, and retention controls

  • Design network security controls (segmentation, security groups, WAF, DDoS posture) for the week-1 reference architecture

  • Assemble the compliance evidence checklist an auditor would request for one regulated workload

Your checkpoint

A security architecture and controls matrix mapping each control to the asset it protects, the identity or key involved, and the evidence artifact that proves it is in place

Week 7

Cloud Architecture Design & Cloud Security and Compliance

  • Red-team your own week-2 architecture and document at least eight weaknesses with remediations

  • Reconcile security controls against architecture decisions and resolve every conflict where a control degrades availability or performance

  • Rewrite the weakest section of your architecture notes so a reviewer could defend it in a design review

  • Produce a one-page executive summary of the design, its risks, and its cost profile

Your checkpoint

A design-review packet: red-team findings with remediations, a resolved conflict log, and a one-page executive summary

Week 8

Cloud Architecture Design & Cloud Migration and Deployment & Cloud Operations and Optimization & Cloud Security and Compliance

  • Answer timed practice sets across all four domains and log every miss by domain and root cause

  • Re-teach your three weakest sub-topics from first principles in writing, without consulting notes

  • Rehearse scenario-based explanations aloud for migration sequencing, cost optimization, and security tradeoffs

  • Consolidate all prior deliverables into a single indexed study binder with a personal weakness list

Your checkpoint

A scored practice-exam log with root-cause analysis per miss, plus a final indexed binder and a prioritized weakness list for continued review

Milestones

Week 2: Can sketch and defend a multi-AZ three-tier architecture on a blank page in under 15 minutes, naming the failure mode each redundancy layer covers

Week 4: Migration plan for the 10-workload estate is complete, wave-sequenced, and each workload has a named tool category and a validated cutover gate

Week 6: Security controls matrix is complete with no unmapped asset, and every control has a named evidence artifact

Week 8: Practice-exam log shows a documented root cause for every miss and a written remediation for each of the three weakest sub-topics