Studying AWS Certified Solutions Architect – Associate becomes much more effective when familiar services are treated as design choices rather than trivia. This article works through the technical decisions a candidate should be able to justify for AWS SAA-C03: connectivity, permissions, data stores, stateful recovery, traffic handling and performance. It is not another list of exam changes or a universal study schedule; it is an architecture reasoning workshop built around realistic constraints.
Use the AWS SAA-C03 credential context for the exam being discussed and AWS’s current official domain guide to keep scope accurate. Its domains cover security, resilience, performance and cost optimization. Every example below is a design exercise, not a claim to reproduce a live exam item or an implementation that has been benchmarked in a customer environment.
Decide whether the application needs public or private connectivity
Imagine an application with public web traffic, private application servers and a database that must not accept arbitrary internet connections. The first decision is how traffic enters: DNS, an appropriate load-balancing layer, application subnets and controlled east-west access. Security groups and network ACLs have different state and scope behavior, while route tables govern where packets can travel. Combining all of them without a defined requirement makes troubleshooting harder rather than increasing security automatically.
For communication between private workloads, distinguish peering, transit architectures and service-specific connections. Transit Gateway, VPC peering and PrivateLink address different connectivity relationships and routing needs. Ask whether the traffic is many-to-many, whether routes must be transitive, whether one service is being privately consumed, and who operates the network boundary. Those constraints determine which option deserves consideration.
Plan identity before the first resource is created
The web workload, deployment service and human administrators should use separate identities with permissions based on their roles. A workload that reads one object prefix does not need full S3 administration. An application that retrieves a secret should not be able to modify every key or trust policy in the account. Where organizational policies apply, understand the interaction between identity permissions, resource permissions and centrally applied restrictions.
Encryption decisions follow data classification and the access path. Encryption at rest does not necessarily prevent an overly privileged application from reading decrypted data. Use key policies, resource policies, endpoint restrictions, logging and lifecycle management according to the threat model. Demonstrate both an authorized request and a denied request when testing whether a design truly enforces least privilege.
Choose database consistency and access patterns deliberately
A transactional order system and a high-volume key-value access layer impose different requirements. Consider whether the workload needs multi-row transactions, relational joins, schema constraints, global reads or extremely predictable key-based latency. If the data model is relational and existing SQL operations are important, a managed relational database may be a sound baseline. If access is driven by well-defined partition keys and throughput patterns, a nonrelational option may fit better.
A useful comparison is DynamoDB versus Aurora Serverless. Do not reduce the choice to ‘serverless is cheaper.’ Evaluate query shapes, partition design, connection behavior, scaling limits, transaction semantics and the organization’s database expertise. A design that minimizes provisioning work may still introduce migration, governance or application complexity.
Separate read scaling from fault tolerance
Consider a service that receives most of its queries during a small peak window while write traffic remains steady. A read replica could help distribute eligible reads, but it changes how applications handle replica lag and routing. An automatically managed standby improves recovery from certain infrastructure failures, but it is not intended simply as a general-purpose read-scaling endpoint. Define the failure and traffic problem before making a choice.
For stateful systems, include recovery targets in the design. Ask what happens if the primary database becomes unavailable, the entire Availability Zone fails or an operator deletes data. Availability mechanisms, backups, point-in-time recovery and cross-region recovery plans address different causes. A restore that has never been tested is a promise without sufficient evidence.
Match storage semantics to the workload
An object archive, shared file system and attached block volume are not interchangeable just because they can store application data. Block storage can serve low-level filesystem and database use cases; object storage suits object access, durability patterns and lifecycle transitions; file storage supports shared namespace needs with service-specific performance and protocol constraints. Consider consistency, attachment model, concurrency, latency, access controls and backup behavior.
For static assets, a design might use S3 behind a content delivery layer instead of asking every application instance to serve files. For a database transaction log, the access and durability pattern is entirely different. The correct architecture also accounts for data growth, retrieval frequency and regional replication cost, so an inexpensive storage-class price does not become an expensive retrieval and transfer bill.
Investigate performance at the layer where delay occurs
Start with the user-visible objective, then trace latency through DNS, connection setup, load balancer, application code, cache, database and storage. If the database is saturated by a missing index, adding more load-balanced web servers will not solve the root cause. If requests are CPU-bound and stateless, horizontal scaling might be appropriate. If an occasional batch causes high network transfer, decoupling or scheduling the workload may be more useful than larger always-on instances.
Use metrics, logs and traces to test your hypothesis. A production-like lab should change one variable at a time and record what improved. Avoid conclusions such as ‘service X is always faster’ without specifying data volume, request type, consistency expectations and configuration. The ability to diagnose a trade-off is central to architecture work and more durable than memorizing benchmark numbers.
Design event-driven boundaries where coupling causes fragility
An online request should not necessarily wait for every downstream notification, image transformation or audit update to finish. Queueing and event-driven processing can isolate failure domains and smooth bursts. But asynchronous design introduces delivery guarantees, retries, duplicate processing, dead-letter handling and observability obligations. Declare which operations must succeed synchronously and which can complete later.
For a payment workflow, a duplicate event must not create a second charge. Build idempotency around stable transaction identifiers and persistent state rather than assuming events arrive once. Where an event handler fails repeatedly, the system needs a visible remediation path. An architecture exam scenario may make this operational trade-off the deciding factor even when multiple service diagrams look plausible.
To test the networking design, follow one request end to end. Resolve the application hostname, enter through the intended public endpoint, authenticate the user, forward to a service instance, query a private data store and return the response. Mark where TLS ends, which identity authenticates each hop and what must be logged. Then ask what happens if the load balancer loses a target, DNS changes slowly or the database endpoint fails over. That trace reveals hidden assumptions that a diagram of subnets alone often misses.
Consider data retention in the same exercise. Customer attachments may require encryption, deletion after an approved period and occasional retrieval by authorized support staff. A storage class with cheap monthly storage may carry retrieval fees or operational restrictions that conflict with support workflows. Include retention lifecycle, access policies and expected read frequency in the cost analysis. A design that optimizes one charge while violating a deletion requirement is not cost-optimized in the business sense.
Introduce an operational incident: traffic suddenly doubles and application latency rises. Before increasing capacity, decide which telemetry distinguishes compute saturation from database contention, dependency timeouts and a request flood. Set a success criterion such as recovery of a specified response-time objective under a representative load. If an auto-scaling rule adds instances but database connections multiply beyond the database’s safe range, the apparent scaling solution can worsen the failure. The correct response depends on the observed bottleneck.
End the review by recording unresolved assumptions. Which data stores support the required consistency? Can the application retry safely? Does the backup procedure meet the actual recovery point? Which change can be deployed or reversed independently? An architecture that makes these questions visible is more mature than one that merely contains every popular AWS service.
Include cost and operations in the final comparison
Compare candidates using a small decision record: security boundary, failure behavior, performance constraint, estimated cost drivers and ongoing operational work. A serverless architecture can reduce idle capacity while increasing sensitivity to request duration or external service costs; a provisioned design may be efficient for sustained predictable load. Consider data-transfer charges, storage retention, replica capacity and observability before choosing only by advertised base price.
When you can defend an AWS design across these dimensions—and explain which requirement would make you choose differently—you have moved beyond memorizing products. That is the practical ability this scenario-focused companion to SAA-C03 preparation is intended to build.