AWS SAP Specialty study plan

Map every multi-account governance control (SCPs, OU structure, centralized logging, identity federation) to at least one design scenario you can explain aloud

Draft a hub-and-spoke versus Transit Gateway network topology comparison with explicit tradeoffs for latency, cost, and blast radius

Configure a working AWS Organizations structure with at least three OUs and two SCPs in a sandbox account

Write a one-page decision guide for when to use RAM sharing versus cross-account resource duplication

Design and document a three-tier application that spans two Regions with defined RPO and RTO targets

Select and justify compute, storage, and database services against at least four competing alternatives

Build a working proof-of-concept stack for the design in a sandbox using infrastructure as code

Enumerate failure modes for the design and state the mitigation for each

Design a hybrid connectivity solution combining at least two of Direct Connect, Site-to-Site VPN, and Transit Gateway, with failover behavior stated

Define a DNS and traffic-routing strategy across accounts and Regions, including health-check-driven failover

Model the cost of the hybrid design at three traffic volumes and identify where cost grows nonlinearly

Explain aloud how identity propagation works from on-premises directory to AWS workloads

Audit an existing sandbox workload against the Well-Architected pillars and log every gap with a severity rating

Prioritize the gaps by remediation effort versus risk reduction and justify the ordering in writing

Implement the top two remediations and measure the before-and-after state

Define the operational metrics you would monitor to detect regression in each remediated area

Design a centralized observability strategy covering logs, metrics, and traces across at least three accounts

Define an alerting policy that distinguishes actionable pages from dashboards, with thresholds justified

Automate one recurring operational task end to end and document the rollback path

Draft a patch and configuration-compliance workflow with drift detection

Design a migration plan for a multi-tier legacy application using the appropriate migration strategy for each tier

Sequence the migration waves and state the cutover and rollback criteria for each wave

Compare at least three database migration approaches on downtime, effort, and risk

Identify which components should be rehosted, replatformed, or refactored, and defend each choice

Design a modernization path that decomposes one monolith capability into a decoupled service with a defined contract

Select an integration pattern for the decomposition and justify it against at least two alternatives

Define a data migration and dual-write or backfill strategy that avoids downtime

Specify how the modernized component is tested, deployed, and observed in production

Rehearse timed scenario questions across all four domains and record accuracy by domain

Revisit every domain where rehearsal accuracy falls below your target and close the specific gap

Practice articulating tradeoffs aloud for the ten designs you are least confident about

Consolidate your decision guides and design documents into a single reviewable reference