Sign in Get started

Interview Q&A · 111 questions · 24 answered publicly

Solutions Architect Interview Questions

Ordered by how often they're asked. Sign in free to see every answer, rate your confidence and run timed mock interviews.

  1. Most asked What does the AWS Well-Architected Operational Excellence pillar cover, and how do you apply it?

    Summary

    Run and monitor systems to deliver business value and continually improve processes.

    Longer Answer

    Run and monitor systems to deliver business value and continually improve processes. In practice: design ops runbooks, automate changes, and learn from failures.

    Key Points

    • Run and monitor systems to deliver business value and continually improve processes
    • In practice: design ops runbooks, automate changes, and learn from failures
    • Core SA Associate / Well-Architected interview topic: Operational Excellence
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'What does the AWS Well-Architected Operational Excellence pillar cover, and how do you apply it?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Run and monitor systems to deliver business value and continually improve processes.
    Practical tradeoff Core SA Associate / Well-Architected interview topic: Operational Excellence.

    Permalink

  2. Most asked What does the AWS Well-Architected Security pillar cover, and how do you apply it?

    Summary

    Protect information and systems via identity, detection, infrastructure, and data protection.

    Longer Answer

    Protect information and systems via identity, detection, infrastructure, and data protection. In practice: apply least privilege, encrypt data, and enable detective controls.

    Key Points

    • Protect information and systems via identity, detection, infrastructure, and data protection
    • In practice: apply least privilege, encrypt data, and enable detective controls
    • Core SA Associate / Well-Architected interview topic: Security
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'What does the AWS Well-Architected Security pillar cover, and how do you apply it?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Protect information and systems via identity, detection, infrastructure, and data protection.
    Practical tradeoff Core SA Associate / Well-Architected interview topic: Security.

    Permalink

  3. Most asked What does the AWS Well-Architected Reliability pillar cover, and how do you apply it?

    Summary

    Ensure workloads perform correctly and recover from failures.

    Longer Answer

    Ensure workloads perform correctly and recover from failures. In practice: use Multi-AZ, backups, and graceful degradation.

    Key Points

    • Ensure workloads perform correctly and recover from failures
    • In practice: use Multi-AZ, backups, and graceful degradation
    • Core SA Associate / Well-Architected interview topic: Reliability
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'What does the AWS Well-Architected Reliability pillar cover, and how do you apply it?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Ensure workloads perform correctly and recover from failures.
    Practical tradeoff Core SA Associate / Well-Architected interview topic: Reliability.

    Permalink

  4. Most asked When would you choose Amazon EC2 in an AWS architecture, and what are its key characteristics?

    Summary

    Virtual servers in the cloud; choose instance families for CPU/memory/GPU needs.

    Longer Answer

    Virtual servers in the cloud; choose instance families for CPU/memory/GPU needs. Choose it when those characteristics match workload requirements, cost, and operational constraints.

    Key Points

    • Virtual servers in the cloud; choose instance families for CPU/memory/GPU needs
    • Choose it when those characteristics match workload requirements, cost, and operational constraints
    • Service selection is a core Solutions Architect skill for Amazon EC2
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When would you choose Amazon EC2 in an AWS architecture, and what are its key characteristics?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Virtual servers in the cloud; choose instance families for CPU/memory/GPU needs.
    Practical tradeoff Service selection is a core Solutions Architect skill for Amazon EC2.

    Permalink

  5. Most asked When would you choose Amazon S3 in an AWS architecture, and what are its key characteristics?

    Summary

    Object storage with eleven 9s durability; use storage classes and lifecycle policies.

    Longer Answer

    Object storage with eleven 9s durability; use storage classes and lifecycle policies. Choose it when those characteristics match workload requirements, cost, and operational constraints.

    Key Points

    • Object storage with eleven 9s durability; use storage classes and lifecycle policies
    • Choose it when those characteristics match workload requirements, cost, and operational constraints
    • Service selection is a core Solutions Architect skill for Amazon S3
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When would you choose Amazon S3 in an AWS architecture, and what are its key characteristics?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Object storage with eleven 9s durability; use storage classes and lifecycle policies.
    Practical tradeoff Service selection is a core Solutions Architect skill for Amazon S3.

    Permalink

  6. Most asked When would you choose Amazon VPC in an AWS architecture, and what are its key characteristics?

    Summary

    Isolated virtual network with subnets, route tables, NACLs, and security groups.

    Longer Answer

    Isolated virtual network with subnets, route tables, NACLs, and security groups. Choose it when those characteristics match workload requirements, cost, and operational constraints.

    Key Points

    • Isolated virtual network with subnets, route tables, NACLs, and security groups
    • Choose it when those characteristics match workload requirements, cost, and operational constraints
    • Service selection is a core Solutions Architect skill for Amazon VPC
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When would you choose Amazon VPC in an AWS architecture, and what are its key characteristics?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Isolated virtual network with subnets, route tables, NACLs, and security groups.
    Practical tradeoff Service selection is a core Solutions Architect skill for Amazon VPC.

    Permalink

  7. Most asked When would you choose Amazon RDS in an AWS architecture, and what are its key characteristics?

    Summary

    Managed relational databases with Multi-AZ and read replicas.

    Longer Answer

    Managed relational databases with Multi-AZ and read replicas. Choose it when those characteristics match workload requirements, cost, and operational constraints.

    Key Points

    • Managed relational databases with Multi-AZ and read replicas
    • Choose it when those characteristics match workload requirements, cost, and operational constraints
    • Service selection is a core Solutions Architect skill for Amazon RDS
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When would you choose Amazon RDS in an AWS architecture, and what are its key characteristics?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Managed relational databases with Multi-AZ and read replicas.
    Practical tradeoff Service selection is a core Solutions Architect skill for Amazon RDS.

    Permalink

  8. Most asked When would you choose Amazon DynamoDB in an AWS architecture, and what are its key characteristics?

    Summary

    Fully managed NoSQL key-value/document store with single-digit ms latency.

    Longer Answer

    Fully managed NoSQL key-value/document store with single-digit ms latency. Choose it when those characteristics match workload requirements, cost, and operational constraints.

    Key Points

    • Fully managed NoSQL key-value/document store with single-digit ms latency
    • Choose it when those characteristics match workload requirements, cost, and operational constraints
    • Service selection is a core Solutions Architect skill for Amazon DynamoDB
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When would you choose Amazon DynamoDB in an AWS architecture, and what are its key characteristics?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Fully managed NoSQL key-value/document store with single-digit ms latency.
    Practical tradeoff Service selection is a core Solutions Architect skill for Amazon DynamoDB.

    Permalink

  9. Most asked When would you choose AWS Lambda in an AWS architecture, and what are its key characteristics?

    Summary

    Event-driven serverless compute billed per request and duration.

    Longer Answer

    Event-driven serverless compute billed per request and duration. Choose it when those characteristics match workload requirements, cost, and operational constraints.

    Key Points

    • Event-driven serverless compute billed per request and duration
    • Choose it when those characteristics match workload requirements, cost, and operational constraints
    • Service selection is a core Solutions Architect skill for AWS Lambda
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When would you choose AWS Lambda in an AWS architecture, and what are its key characteristics?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Event-driven serverless compute billed per request and duration.
    Practical tradeoff Service selection is a core Solutions Architect skill for AWS Lambda.

    Permalink

  10. Most asked When would you choose Amazon SQS in an AWS architecture, and what are its key characteristics?

    Summary

    Managed message queue for decoupling producers/consumers.

    Longer Answer

    Managed message queue for decoupling producers/consumers. Choose it when those characteristics match workload requirements, cost, and operational constraints.

    Key Points

    • Managed message queue for decoupling producers/consumers
    • Choose it when those characteristics match workload requirements, cost, and operational constraints
    • Service selection is a core Solutions Architect skill for Amazon SQS
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When would you choose Amazon SQS in an AWS architecture, and what are its key characteristics?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Managed message queue for decoupling producers/consumers.
    Practical tradeoff Service selection is a core Solutions Architect skill for Amazon SQS.

    Permalink

  11. Most asked When would you choose AWS IAM in an AWS architecture, and what are its key characteristics?

    Summary

    Identity and access management with users, roles, policies, and federation.

    Longer Answer

    Identity and access management with users, roles, policies, and federation. Choose it when those characteristics match workload requirements, cost, and operational constraints.

    Key Points

    • Identity and access management with users, roles, policies, and federation
    • Choose it when those characteristics match workload requirements, cost, and operational constraints
    • Service selection is a core Solutions Architect skill for AWS IAM
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When would you choose AWS IAM in an AWS architecture, and what are its key characteristics?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Identity and access management with users, roles, policies, and federation.
    Practical tradeoff Service selection is a core Solutions Architect skill for AWS IAM.

    Permalink

  12. Most asked How would you design a highly available web app on AWS?

    Summary

    ALB across Multi-AZ Auto Scaling groups, Multi-AZ RDS, ElastiCache for sessions, CloudFront for static assets, Route 53 health checks.

    Longer Answer

    ALB across Multi-AZ Auto Scaling groups, Multi-AZ RDS, ElastiCache for sessions, CloudFront for static assets, Route 53 health checks. Architecture scenario covering highly available web app.

    Key Points

    • ALB across Multi-AZ Auto Scaling groups, Multi-AZ RDS, ElastiCache for sessions, CloudFront for static assets, Route 53 health checks
    • Architecture scenario covering highly available web app
    • Relevant areas: Architecture, Scenario, Aws
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'How would you design a highly available web app on AWS?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea ALB across Multi-AZ Auto Scaling groups, Multi-AZ RDS, ElastiCache for sessions, CloudFront for static assets, Route 53 health checks.
    Practical tradeoff Architecture scenario covering highly available web app.

    Permalink

  13. Most asked How would you design a serverless API on AWS?

    Summary

    API Gateway + Lambda + DynamoDB with IAM least privilege, CloudWatch alarms, and optional SQS for async work.

    Longer Answer

    API Gateway + Lambda + DynamoDB with IAM least privilege, CloudWatch alarms, and optional SQS for async work. Architecture scenario covering serverless API.

    Key Points

    • API Gateway + Lambda + DynamoDB with IAM least privilege, CloudWatch alarms, and optional SQS for async work
    • Architecture scenario covering serverless API
    • Relevant areas: Architecture, Scenario, Aws
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'How would you design a serverless API on AWS?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea API Gateway + Lambda + DynamoDB with IAM least privilege, CloudWatch alarms, and optional SQS for async work.
    Practical tradeoff Architecture scenario covering serverless API.

    Permalink

  14. Most asked What is the shared responsibility model on AWS?

    Summary

    AWS secures the cloud (hardware, regions, hypervisor); customers secure in the cloud (data, identity, OS/config for IaaS, application code).

    Longer Answer

    AWS secures the cloud (hardware, regions, hypervisor); customers secure in the cloud (data, identity, OS/config for IaaS, application code). AWS SA interview fundamental.

    Key Points

    • AWS secures the cloud (hardware, regions, hypervisor); customers secure in the cloud (data, identity, OS/config for IaaS, application code)
    • AWS SA interview fundamental
    • Relevant areas: Security, Shared Responsibility
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'What is the shared responsibility model on AWS?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea AWS secures the cloud (hardware, regions, hypervisor); customers secure in the cloud (data, identity, OS/config for IaaS, application code).
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  15. Most asked Difference between Security Groups and NACLs?

    Summary

    Security Groups are stateful instance-level allow rules; NACLs are stateless subnet-level allow/deny rules evaluated in order.

    Longer Answer

    Security Groups are stateful instance-level allow rules; NACLs are stateless subnet-level allow/deny rules evaluated in order. AWS SA interview fundamental.

    Key Points

    • Security Groups are stateful instance-level allow rules; NACLs are stateless subnet-level allow/deny rules evaluated in order
    • AWS SA interview fundamental
    • Relevant areas: Networking, Security
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'Difference between Security Groups and NACLs?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Security Groups are stateful instance-level allow rules; NACLs are stateless subnet-level allow/deny rules evaluated in order.
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  16. Most asked What is an AZ and why Multi-AZ?

    Summary

    An Availability Zone is an isolated data center cluster.

    Longer Answer

    An Availability Zone is an isolated data center cluster. Multi-AZ deployments survive AZ failure for higher availability.

    Key Points

    • An Availability Zone is an isolated data center cluster
    • Multi-AZ deployments survive AZ failure for higher availability
    • AWS SA interview fundamental
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'What is an AZ and why Multi-AZ?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea An Availability Zone is an isolated data center cluster.
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  17. Most asked When do you use NAT Gateway vs Internet Gateway?

    Summary

    IGW enables public subnet internet access; NAT Gateway lets private subnet instances initiate outbound internet without inbound exposure.

    Longer Answer

    IGW enables public subnet internet access; NAT Gateway lets private subnet instances initiate outbound internet without inbound exposure. AWS SA interview fundamental.

    Key Points

    • IGW enables public subnet internet access; NAT Gateway lets private subnet instances initiate outbound internet without inbound exposure
    • AWS SA interview fundamental
    • Relevant areas: Networking, VPC
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When do you use NAT Gateway vs Internet Gateway?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea IGW enables public subnet internet access; NAT Gateway lets private subnet instances initiate outbound internet without inbound exposure.
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  18. Most asked RPO vs RTO?

    Summary

    RPO is acceptable data loss window; RTO is acceptable downtime until recovery.

    Longer Answer

    RPO is acceptable data loss window; RTO is acceptable downtime until recovery. Drive backup and DR strategy.

    Key Points

    • RPO is acceptable data loss window; RTO is acceptable downtime until recovery
    • Drive backup and DR strategy
    • AWS SA interview fundamental
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'RPO vs RTO?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea RPO is acceptable data loss window; RTO is acceptable downtime until recovery.
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  19. Most asked When choose DynamoDB over RDS?

    Summary

    When you need massive scale, simple key-based access patterns, and managed NoSQL; choose RDS for complex relational queries/transactions.

    Longer Answer

    When you need massive scale, simple key-based access patterns, and managed NoSQL; choose RDS for complex relational queries/transactions. AWS SA interview fundamental.

    Key Points

    • When you need massive scale, simple key-based access patterns, and managed NoSQL; choose RDS for complex relational queries/transactions
    • AWS SA interview fundamental
    • Relevant areas: Database, Selection
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'When choose DynamoDB over RDS?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea When you need massive scale, simple key-based access patterns, and managed NoSQL; choose RDS for complex relational queries/transactions.
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  20. Most asked How would you design a disaster recovery (pilot light) on AWS?

    Summary

    Minimal standby in secondary region with replicated data; scale up on failover.

    Longer Answer

    Minimal standby in secondary region with replicated data; scale up on failover. Architecture scenario covering disaster recovery (pilot light).

    Key Points

    • Minimal standby in secondary region with replicated data; scale up on failover
    • Architecture scenario covering disaster recovery (pilot light)
    • Relevant areas: Architecture, Scenario, Aws
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'How would you design a disaster recovery (pilot light) on AWS?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Minimal standby in secondary region with replicated data; scale up on failover.
    Practical tradeoff Architecture scenario covering disaster recovery (pilot light).

    Permalink

  21. Most asked What is eventual consistency vs strong consistency in DynamoDB?

    Summary

    Eventually consistent reads may return stale data briefly; strongly consistent reads return the latest successful write but cost more and have limits.

    Longer Answer

    Eventually consistent reads may return stale data briefly; strongly consistent reads return the latest successful write but cost more and have limits. AWS SA interview fundamental.

    Key Points

    • Eventually consistent reads may return stale data briefly; strongly consistent reads return the latest successful write but cost more and have limits
    • AWS SA interview fundamental
    • Relevant areas: Dynamodb, Consistency
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'What is eventual consistency vs strong consistency in DynamoDB?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Eventually consistent reads may return stale data briefly; strongly consistent reads return the latest successful write but cost more and have limits.
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  22. Most asked Explain S3 storage classes briefly.

    Summary

    Standard for frequent access; Intelligent-Tiering; Standard-IA/One Zone-IA for infrequent; Glacier Instant/Flexible/Deep Archive for archival; lifecycle policies move objects.

    Longer Answer

    Standard for frequent access; Intelligent-Tiering; Standard-IA/One Zone-IA for infrequent; Glacier Instant/Flexible/Deep Archive for archival; lifecycle policies move objects. AWS SA interview fundamental.

    Key Points

    • Standard for frequent access; Intelligent-Tiering; Standard-IA/One Zone-IA for infrequent; Glacier Instant/Flexible/Deep Archive for archival; lifecycle policies move objects
    • AWS SA interview fundamental
    • Relevant areas: S3, Cost
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'Explain S3 storage classes briefly.'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Standard for frequent access; Intelligent-Tiering; Standard-IA/One Zone-IA for infrequent; Glacier Instant/Flexible/Deep Archive for archival; lifecycle policies move objects.
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  23. Most asked Horizontal vs vertical scaling on AWS?

    Summary

    Vertical = bigger instance; horizontal = more instances behind a load balancer.

    Longer Answer

    Vertical = bigger instance; horizontal = more instances behind a load balancer. Prefer horizontal for elasticity and fault isolation.

    Key Points

    • Vertical = bigger instance; horizontal = more instances behind a load balancer
    • Prefer horizontal for elasticity and fault isolation
    • AWS SA interview fundamental
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'Horizontal vs vertical scaling on AWS?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Vertical = bigger instance; horizontal = more instances behind a load balancer.
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  24. Most asked What are VPC endpoints?

    Summary

    Interface (PrivateLink) or gateway endpoints that reach AWS services privately without traversing the public internet.

    Longer Answer

    Interface (PrivateLink) or gateway endpoints that reach AWS services privately without traversing the public internet. AWS SA interview fundamental.

    Key Points

    • Interface (PrivateLink) or gateway endpoints that reach AWS services privately without traversing the public internet
    • AWS SA interview fundamental
    • Relevant areas: Networking, Endpoints
    • Use the answer to connect the concept back to a realistic production or interview scenario for 'What are VPC endpoints?'

    Comparison / Tradeoffs

    Aspect Notes
    Core idea Interface (PrivateLink) or gateway endpoints that reach AWS services privately without traversing the public internet.
    Practical tradeoff AWS SA interview fundamental.

    Permalink

  25. When would you choose Application Load Balancer in an AWS architecture, and what are its key characteristics?
  26. When would you choose AWS KMS in an AWS architecture, and what are its key characteristics?
  27. When would you choose AWS Auto Scaling in an AWS architecture, and what are its key characteristics?
  28. How would you design a event-driven order processing on AWS?
  29. How would you design a multi-region active-active on AWS?
  30. How would you design a secure S3 access on AWS?
  31. How would you design a least-privilege IAM on AWS?
  32. How would you design a PCI/sensitive data on AWS?
  33. What is idempotency in distributed AWS designs?
  34. Why is 'Prefer managed services' an important AWS Solutions Architect practice?
  35. Why is 'Automate with IaC' an important AWS Solutions Architect practice?
  36. Why is 'Rate-limit public APIs' an important AWS Solutions Architect practice?
  37. Why is 'Test restore procedures' an important AWS Solutions Architect practice?
  38. Why is 'Review Trusted Advisor' an important AWS Solutions Architect practice?
  39. Why is 'Rotate secrets' an important AWS Solutions Architect practice?
  40. Why is 'Use Parameter Store/Secrets Manager' an important AWS Solutions Architect practice?
  41. Why is 'Throttle with WAF' an important AWS Solutions Architect practice?
  42. Why is 'Use GSI/LSI thoughtfully' an important AWS Solutions Architect practice?
  43. What does the AWS Well-Architected Performance Efficiency pillar cover, and how do you apply it?
  44. What does the AWS Well-Architected Cost Optimization pillar cover, and how do you apply it?
  45. When would you choose Network Load Balancer in an AWS architecture, and what are its key characteristics?
  46. When would you choose Amazon Aurora in an AWS architecture, and what are its key characteristics?
  47. When would you choose Amazon ElastiCache in an AWS architecture, and what are its key characteristics?
  48. When would you choose Amazon CloudFront in an AWS architecture, and what are its key characteristics?
  49. When would you choose Amazon API Gateway in an AWS architecture, and what are its key characteristics?
  50. When would you choose Amazon SNS in an AWS architecture, and what are its key characteristics?
  51. When would you choose Amazon EventBridge in an AWS architecture, and what are its key characteristics?
  52. When would you choose Amazon CloudWatch in an AWS architecture, and what are its key characteristics?
  53. When would you choose AWS CloudTrail in an AWS architecture, and what are its key characteristics?
  54. When would you choose Amazon Route 53 in an AWS architecture, and what are its key characteristics?
  55. When would you choose Amazon ECS in an AWS architecture, and what are its key characteristics?
  56. When would you choose Amazon EKS in an AWS architecture, and what are its key characteristics?
  57. When would you choose Amazon EBS in an AWS architecture, and what are its key characteristics?
  58. When would you choose AWS Organizations in an AWS architecture, and what are its key characteristics?
  59. How would you design a global content delivery on AWS?
  60. How would you design a hybrid connectivity on AWS?
  61. How would you design a data lake on AWS?
  62. How would you design a blue/green deployment on AWS?
  63. How would you design a warm standby DR on AWS?
  64. How would you design a cost-optimize compute on AWS?
  65. How would you design a observability baseline on AWS?
  66. How would you design a containerized microservices on AWS?
  67. How would you design a queue backlog handling on AWS?
  68. How would you design a database read scaling on AWS?
  69. How would you design a cross-account access on AWS?
  70. What is envelope encryption with KMS?
  71. How do you protect against accidental S3 deletion?
  72. How does CloudFront Origin Access Control help?
  73. ALB target group health checks purpose?
  74. How do SCPs differ from IAM policies?
  75. Why is 'Use circuit breakers' an important AWS Solutions Architect practice?
  76. Why is 'Tag for cost allocation' an important AWS Solutions Architect practice?
  77. Why is 'Centralize logging' an important AWS Solutions Architect practice?
  78. Why is 'Snapshot before changes' an important AWS Solutions Architect practice?
  79. Why is 'Budget alarms' an important AWS Solutions Architect practice?
  80. Why is 'Prefer IAM roles for EC2' an important AWS Solutions Architect practice?
  81. Why is 'Enable MFA on root' an important AWS Solutions Architect practice?
  82. Why is 'Validate input at edges' an important AWS Solutions Architect practice?
  83. Why is 'Avoid hot partitions' an important AWS Solutions Architect practice?
  84. Why is 'Cache aggressively at edge' an important AWS Solutions Architect practice?
  85. What does the AWS Well-Architected Sustainability pillar cover, and how do you apply it?
  86. When would you choose AWS Config in an AWS architecture, and what are its key characteristics?
  87. When would you choose AWS Step Functions in an AWS architecture, and what are its key characteristics?
  88. When would you choose Amazon Cognito in an AWS architecture, and what are its key characteristics?
  89. When would you choose AWS WAF in an AWS architecture, and what are its key characteristics?
  90. When would you choose AWS Shield in an AWS architecture, and what are its key characteristics?
  91. When would you choose Amazon EFS in an AWS architecture, and what are its key characteristics?
  92. When would you choose AWS Glue in an AWS architecture, and what are its key characteristics?
  93. When would you choose Amazon Athena in an AWS architecture, and what are its key characteristics?
  94. When would you choose Amazon Redshift in an AWS architecture, and what are its key characteristics?
  95. When would you choose AWS Control Tower in an AWS architecture, and what are its key characteristics?
  96. How would you design a thundering herd on launch on AWS?
  97. What is AWS Transit Gateway?
  98. Spot Instances tradeoffs?
  99. What is a Launch Template used for?
  100. Explain sticky sessions on ALB.
  101. Why is 'Design for failure' an important AWS Solutions Architect practice?
  102. Why is 'Encrypt everything' an important AWS Solutions Architect practice?
  103. Why is 'Separate accounts by env' an important AWS Solutions Architect practice?
  104. Why is 'Use private subnets for data' an important AWS Solutions Architect practice?
  105. Why is 'Monitor golden signals' an important AWS Solutions Architect practice?
  106. Why is 'Apply CIS benchmarks' an important AWS Solutions Architect practice?
  107. Why is 'Disable root access keys' an important AWS Solutions Architect practice?
  108. Why is 'Prefer HTTPS everywhere' an important AWS Solutions Architect practice?
  109. Why is 'Design partition keys carefully' an important AWS Solutions Architect practice?
  110. Why is 'Model access patterns first' an important AWS Solutions Architect practice?
  111. How would you design a highly available web application on AWS?