Objective 2.1 · high
Design a deployment strategy
Select infrastructure, application-release, environment, testing, rollback, automation, and organizational deployment patterns.
- Lesson
- d2-lesson
- Practice pool
- d2-questions
- Application
- sap-l04
SAP-C02 · D2 · 29%
Design for New Solutions
Turn new workload requirements into deployable, secure, resilient, performant, and cost-effective architectures with explicit tradeoffs.
Provider facts checked 2026-08-03
Objective coverage
Objective 2.2 · high
Design business continuity
Translate business impact, RTO, RPO, dependency, data, and operational constraints into backup and disaster-recovery architecture.
- Lesson
- d2-lesson
- Practice pool
- d2-questions
- Application
- sap-l03
Objective 2.3 · high
Determine security requirements
Embed identity, data, network, application, logging, compliance, and supply-chain controls into the architecture.
- Lesson
- d2-lesson
- Practice pool
- d2-questions
- Application
- sap-l01, sap-l02
Objective 2.4 · high
Design reliability
Remove single points of failure, manage dependencies and quotas, isolate faults, scale, recover, and validate behavior.
- Lesson
- d2-lesson
- Practice pool
- d2-questions
- Application
- sap-l03, sap-l04
Objective 2.5 · normal
Design for performance
Choose compute, storage, database, network, integration, caching, concurrency, and scaling from measurable workload characteristics.
- Lesson
- d2-lesson
- Practice pool
- d2-questions
- Application
- sap-l05, sap-l07
Objective 2.6 · normal
Design for cost optimization
Model demand, unit economics, elasticity, commitments, data movement, storage lifecycle, and managed-service tradeoffs.
- Lesson
- d2-lesson
- Practice pool
- d2-questions
- Application
- sap-l05, sap-l07
title: "Design for New Solutions" summary: "A structured approach to designing new AWS solutions from business constraints, quality attributes, failure modes, and evidence."
Convert requirements into measurable architecture
Record workload shape, users, data, access patterns, consistency, latency, throughput, availability, RTO/RPO, security, compliance, deployment, operations, growth, and cost before selecting services. Professional-level questions usually contain multiple viable architectures; the best answer satisfies all stated constraints with the least unnecessary burden.
Deployment and continuity
Version infrastructure and application releases. Choose immutable, rolling, blue/green, canary, feature-flag, workflow, or event-driven deployment based on rollback, state, compatibility, blast radius, and validation. Disaster recovery must include identity, secrets, DNS, data consistency, dependencies, quotas, operations, communication, failover, reconciliation, and failback—not just replication.
Security, reliability, performance, and cost
Embed identity, network, data, application, logging, supply-chain, and compliance controls. Remove single points of failure, isolate faults, manage backpressure and quotas, and test recovery. Select compute, storage, database, integration, caching, and scaling from representative demand and access patterns. Model unit cost and data movement rather than relying only on headline service price.
Self-check
For an event-driven global transaction system, defend deployment, consistency, integration, data, recovery, identity, observability, quota, performance, and cost choices. Name the constraint that eliminates each rejected alternative.