Path & PassCertification practice
SAA-C03

AWS Certified Solutions Architect - Associate (SAA-C03)

Study another certification
Progress0%
Recent accuracy0%
Review due0questions
Answered0 / 155questions

Practice by topic

1 Design secure architecturesSecure access, workload protection, and data security controls.41questionsHigh
2 Design resilient architecturesScalable, loosely coupled, highly available, and fault-tolerant designs.40questionsHigh
3 Design high-performing architecturesStorage, compute, databases, networking, and data processing.38questionsMedium
4 Design cost-optimized architecturesCost optimization for storage, compute, databases, and networking.36questionsMedium
4 areas / 14 objectives selected155questionseligible

Learning modes

Mock examPractice with exam-style timing and length

Browse questions by objective

Choose a topic to read an individual question, its hints, and explanations. No session setup is required.

1.1 Secure access to AWS resources10 questions
  1. Secure access from EC2 to AWS services
  2. Design cross-account access
  3. Federate workforce access to multiple accounts
  4. Restrict the Regions available to an organization
  5. Limit the maximum permissions of delegated administrators
  6. Protect the root user credentials
  7. Grant temporary permissions to an external workload
  8. Grant operators only the required permissions
  9. Provide managed end-user authentication for a web app
  10. Access S3 from EC2 without long-term credentials
1.2 Secure workloads and applications14 questions
  1. Separate web and database subnets
  2. Use security groups and network ACLs
  3. Choose protections for web threats and DDoS
  4. Reach Secrets Manager privately from a private subnet
  5. Limit a sudden request spike from one source IP
  6. Allow the web tier to receive traffic only from the load balancer
  7. Allow return traffic through a stateless network ACL
  8. Prevent unintended public S3 access across an account
  9. Choose advanced DDoS protection and support
  10. Block SQL injection against a public web API
  11. Choose a boundary with automatic return traffic
  12. Prevent accidental public S3 access across accounts
  13. Reduce public HTTPS certificate maintenance
  14. Encrypt an external connection over the internet
1.3 Choose appropriate data security controls17 questions
  1. Encrypt stored data with KMS
  2. Protect data in transit with TLS
  3. Protect application secrets
  4. Combine S3 access control with encryption
  5. Reduce KMS requests while retaining SSE-KMS
  6. Delegate limited KMS use to a temporary processing service
  7. Manage certificates for internal TLS services
  8. Replicate backups to another Region
  9. Audit S3 object-level operations
  10. Design KMS key rotation
  11. Require TLS for S3 requests
  12. Separate secret storage from key management
  13. Prevent tampering with audit data for a retention period
  14. Detect tampering with CloudTrail log files
  15. Encrypt large data with a KMS key
  16. Centralize API auditing across multiple accounts
  17. Rotate database credentials regularly
2.1 Design scalable and loosely coupled architectures22 questions
  1. Decouple bursty order processing with a queue
  2. Fan out one event to multiple services
  3. Route events by their content
  4. Horizontally scale a web tier
  5. Reduce static-content delivery load
  6. Manage state across a multi-step workflow
  7. Scale database reads
  8. Throttle a sudden increase in API requests
  9. Preserve order for updates to the same order
  10. Deliver only the required events to each subscriber
  11. Reduce server management for container workloads
  12. Manage a burst of Lambda database connections
  13. Expose an API only inside a VPC
  14. Retry a transient failure inside a workflow
  15. Discover services that scale dynamically
  16. Move existing SFTP users to object storage
  17. Match shared-file throughput to the workload
  18. Isolate failed messages for later processing
  19. Replace an unhealthy EC2 instance automatically
  20. Retry failed events and keep them for investigation
  21. Make container rollback safe
  22. Avoid duplicate orders after a retry
2.2 Design highly available and fault-tolerant architectures18 questions
  1. Design RDS failover across Availability Zones
  2. Switch DNS after a Regional failure
  3. Choose a disaster-recovery approach from RTO and RPO
  4. Route users to a Region with lower latency
  5. Reduce configuration drift on production servers
  6. Stabilize connections from an unmodifiable legacy database application
  7. Remove a single-AZ failure from the web tier
  8. Continuously replicate S3 data to another Region
  9. Fail over to a healthy load balancer in another Region
  10. Balance targets across Availability Zones
  11. Measure the recovery time of backups
  12. Plan service quotas for a disaster recovery Region
  13. Trace latency across distributed services
  14. Continue RDS writes after an Availability Zone failure
  15. Replicate objects automatically to another Region
  16. Provide low-latency reads and writes in multiple Regions
  17. Resolve users to a nearby Region
  18. Prepare an EBS recovery point in another Region
3.1 Choose high-performing storage8 questions
  1. Choose stable low-latency block I/O
  2. Share files from EC2 instances in multiple AZs
  3. Upload a large object efficiently
  4. Transfer large data to S3 from a distant site
  5. Provide shared files to Windows applications
  6. Tune general-purpose SSD block storage
  7. Retrieve only selected columns from a large CSV
  8. Migrate an on-premises file share in stages
3.2 Choose elastic and high-performing compute7 questions
  1. Tune Lambda execution performance
  2. Scale EC2 capacity with load
  3. Choose EC2 for CPU-intensive processing
  4. Scale Fargate tasks with CPU load
  5. Place HPC nodes for low-latency communication
  6. Reduce Lambda cold-start latency
  7. Scale bursty image processing independently
3.3 Choose a high-performing database8 questions
  1. Choose a key-value database for unpredictable volume
  2. Cache frequently read database results
  3. Distribute Aurora reads across instances
  4. Query DynamoDB by a second attribute efficiently
  5. Lower cross-Region read latency
  6. Reduce repeated DynamoDB read latency
  7. Preserve compatibility for an existing MySQL application
  8. Scale high-concurrency key-value lookups
3.4 Choose a high-performing network7 questions
  1. Optimize global paths for TCP and UDP applications
  2. Connect on-premises systems with a dedicated path
  3. Expose a service privately to customer VPCs
  4. Send fixed-IP TCP traffic to healthy endpoints
  5. Provide redundant VPN paths
  6. Route an HTTP application by URL path
  7. Distribute a TCP service whose clients allowlist fixed IPs
3.5 Choose high-performing data ingestion and transformation8 questions
  1. Ingest continuous sensor data
  2. Transform CSV data for a data lake
  3. Buffer a stream and deliver it to S3
  4. Select a service for large-scale distributed processing
  5. Synchronize on-premises files on a schedule
  6. Discover schemas in an S3 data lake
  7. Centralize table permissions for a data lake
  8. Stabilize dashboard response time for analytics
4.1 Choose cost-optimized storage8 questions
  1. Optimize storage for objects that become infrequent
  2. Allocate retrieval charges for a large public data set
  3. Automatically tier objects with an unknown access pattern
  4. Reduce the cost of infrequently accessed shared files
  5. Lower storage cost for infrequently accessed logs
  6. Reduce the storage consumed by EBS backups
  7. Use only the needed performance for unpredictable shared files
  8. Migrate a large dataset over a bandwidth-constrained link
4.2 Choose cost-optimized compute7 questions
  1. Reduce compute cost for interruptible batch jobs
  2. Apply a discount to steady compute usage
  3. Reduce cost for a development instance that starts and stops
  4. Lower compute cost for an infrequent event handler
  5. Optimize the cost of steady compute usage
  6. Reduce excess EC2 capacity during normal hours
  7. Use inexpensive storage for regenerable temporary data
4.3 Choose a cost-optimized database9 questions
  1. Optimize DynamoDB capacity for predictable traffic
  2. Optimize database backup retention cost
  3. Automatically adjust capacity for variable relational database load
  4. Automatically remove expired session data
  5. Avoid oversizing a database only because of connection bursts
  6. Choose a pricing mode for unpredictable DynamoDB load
  7. Avoid scaling the primary database only for reads
  8. Migrate gradually to a different database engine
  9. Choose a database type for column-focused analytics
4.4 Choose a cost-optimized network12 questions
  1. Use private access to S3 to reduce transfer cost
  2. Balance NAT availability and transfer cost across AZs
  3. Simplify connectivity among many VPCs
  4. Optimize global static-content delivery
  5. Reduce NAT processing for private AWS API access
  6. Lower NAT cost for a small test environment
  7. Centralize routing for many VPCs
  8. Reduce cross-Region delivery of repeated content
  9. Reach S3 from a VPC without NAT
  10. Estimate cross-Region transfer cost
  11. Control API usage to protect the backend
  12. Provide bandwidth and connectivity redundancy