AWS Certified Solutions Architect Associate SAAC02 AWS Certified Solutions Architect Associate SAAC02 Free Practice Test — 30 Questions
This practice bank exercises the ability to design resilient, scalable, and secure architectures on AWS. It tests decisions around incident response during cascading failures, migration strategies (rehost vs. refactor), database high availability (Multi-AZ, Read Replicas, Aurora Global Database), and security auditing (CloudTrail, Config, IAM). Scenarios emphasize trade-offs between cost, performance, and compliance, requiring knowledge of services like CloudWatch, X-Ray, SQS, and Auto Scaling. Behavioral competencies such as adaptability and crisis management are also assessed. Master these patterns to reason through AWS architectural challenges under real-world constraints.
What this AWS Certified Solutions Architect Associate SAAC02 AWS Certified Solutions Architect Associate SAAC02 practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Incident Response and Fault Isolation
A recurring theme is diagnosing and mitigating cascading failures in distributed systems. Questions test the ability to use CloudWatch Logs Insights, X-Ray, and Config to trace issues across microservices. Strategies like circuit breakers, dead-letter queues, and rollback procedures are emphasized to prevent system-wide outages. Understanding how to isolate faulty components while maintaining partial service is critical.
- Use AWS X-Ray for distributed tracing to pinpoint latency bottlenecks across services.
- Implement circuit breaker patterns and SQS dead-letter queues to handle microservice failures gracefully.
- Use AWS Config and CloudTrail to detect configuration drift and unauthorized API calls during an incident.
Migration and Modernization Approaches
Several questions cover migrating legacy monolithic applications to AWS while minimizing downtime and meeting compliance. The bank contrasts rehost (lift-and-shift) with refactoring into microservices using containers (ECS/EKS) and managed databases. Key decisions involve using AWS DMS with CDC, Oracle Data Guard for hybrid setups, and phase-based decomposition to break monoliths gradually.
- AWS DMS with Change Data Capture (CDC) enables near-zero-downtime database migrations.
- Containerizing components with Amazon EKS allows incremental refactoring of monoliths.
- Hybrid architectures using VPN or Direct Connect can bridge on-premises dependencies during migration.
High Availability and Disaster Recovery
The practice bank emphasizes multi-Region designs using Route 53, CloudFront, Aurora Global Database, and S3 Cross-Region Replication to meet strict RTO/RPO objectives. Active-active vs. warm standby patterns are evaluated, with considerations for data residency regulations. Testing failover mechanisms and ensuring stateful session management are also covered.
- Amazon Aurora Global Database provides sub-1-minute RPO for cross-Region disaster recovery.
- Route 53 with latency or failover routing enables global traffic distribution and automatic failover.
- S3 Cross-Region Replication (CRR) replicates objects to a secondary Region for resilience.
Security, Compliance, and Access Control
Bank scenarios require securing PII and meeting regulations like GDPR/SOX using IAM policies, S3 bucket policies, and infrastructure-level controls (SCPs, Config rules). Continuous auditing via CloudTrail, Config, and third-party integrations is stressed. Understanding shared responsibility and how to grant least-privilege access across multi-account environments is essential.
- Use IAM roles with S3 bucket policies to restrict access to specific application roles.
- AWS Organizations Service Control Policies (SCPs) can enforce data residency across all accounts.
- Custom AWS Config rules trigger evaluations when sensitive API actions are detected.
Practice AWS Certified Solutions Architect Associate SAAC02 AWS Certified Solutions Architect Associate SAAC02 with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 30-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
A financial services firm operates a critical customer-facing application on AWS, comprising a web tier, an application tier with multiple microservices, and a managed relational database. During a peak trading period, an unexpected surge in client requests, combined with a latent defect in a recently deployed payment processing microservice, caused a significant increase in CPU utilization across a portion of the application servers. This led to increased request latency and connection timeouts, which subsequently impacted the web tier’s ability to connect to the application tier. The load balancer, detecting unhealthy application instances, began de-registering them, further exacerbating the load on the remaining instances and ultimately resulting in a complete service outage. Which architectural strategy would most effectively mitigate the risk of such cascading failures in this scenario?
Study workflow
Turn one AWS Certified Solutions Architect Associate SAAC02 AWS Certified Solutions Architect Associate SAAC02 attempt into a study plan
- 1
Log Analysis for Root Cause
When facing sporadic failures, centralize logs from EC2, RDS, and SQS into CloudWatch Logs. Use Logs Insights to query correlated patterns (e.g., error codes + latency spikes). Filter by timestamps matching user reports to isolate the affected service.
- 2
Implement Circuit Breaker Pattern
To prevent cascading failures in microservices, wrap remote calls with a circuit breaker (e.g., using AWS App Mesh or custom logic). When errors exceed a threshold, the breaker opens, failing fast and avoiding timeouts. Combine with SQS dead-letter queues for retry isolation.
- 3
Design Multi-Region Active-Active
For global availability, deploy the application stack (ALB + Auto Scaling + DB) in two Regions. Use Aurora Global Database for cross-Region replication (sub-1s latency). Route 53 with latency routing sends traffic to the nearest healthy Region. Test failover quarterly.
- 4
Automate Security Auditing with Config
Enable AWS Config in all accounts. Create custom rules to monitor S3 bucket policies and IAM roles for PII access. Stream configuration changes and compliant evaluations to a central S3 bucket for audit trails. Use SCPs to enforce cross-account compliance.
- 5
Phase Migration with DMS CDC
For minimal-downtime database migration, use AWS DMS with Change Data Capture. Start with a full load, then continuously replicate changes to Amazon RDS. Keep the source online until cutover. Test rollback procedures and use AWS SCT for schema conversion.
FAQ
Questions about this exam practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
What is the difference between SAA-C02 and the new SAA-C03 exam?+
SAA-C02 focuses more on AWS services like EC2 Classic and older RDS versions; SAA-C03 emphasizes modern services like Aurora, EKS, and AWS Organizations. However, core concepts like high availability, fault tolerance, and cost optimization remain similar.
When should I choose a circuit breaker pattern instead of using SQS?+
Use a circuit breaker when you need to fail fast to protect downstream services from overload; it prevents wasted retries. SQS is better for decoupling when work can be retried later asynchronously without immediate user impact.
How can I enforce data residency across multiple AWS accounts?+
Use AWS Organizations Service Control Policies (SCPs) to restrict the AWS Regions where resources can be created. Combine with AWS Config rules that flag resources deployed in non-compliant Regions, and automate remediation via Lambda.
What are the key considerations for choosing between EC2 Auto Scaling and Amazon ECS for microservices?+
EC2 Auto Scaling gives full control over instances but requires more operational overhead. ECS (or EKS) simplifies container orchestration, offers better resource utilization, and integrates with service discovery and load balancers. Choose ECS for portability and ease of scaling.
How do Aurora Global Database differ from RDS Multi-AZ?+
Aurora Global Database replicates data across multiple AWS Regions with sub-1-second latency, enabling cross-region disaster recovery. RDS Multi-AZ replicates within a single Region for high availability. Global Database handles cross-region failover while Multi-AZ handles local AZ failures.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.