Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
The exam blueprint and how scenario questions are read
The shared responsibility model in practice
VPC and subnet design
Routing, Transit Gateway and hybrid connectivity
Security groups versus network ACLs
IAM identities, roles and least privilege
S3 storage classes and lifecycle rules
Load balancing, health checks and autoscaling
Serverless architecture patterns and their limits
Choosing a database and reasoning about replication
Multi account organisation design
CloudWatch observability and the signals that matter
Cost optimisation and governance
Disaster recovery, objectives and resilience patterns
Migration strategies and the seven Rs
Containers on AWS, EKS and ECS
The reliability pillar
The security pillar
Regions, Availability Zones and service quotas
Architecture review and tradeoff reasoning
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
Each item is a situational narrative with four options, and you are scored on the best architectural judgement rather than the most familiar service.
AWS secures the infrastructure: data centres, hardware, power, physical networking, hypervisors and the managed service itself.
A VPC is a region scoped virtual network with an address block from /16 to /28, and a subnet is a smaller range inside it that exists in exactly one availability zone.
A route table is scoped to a subnet, the most specific matching route wins, and the local route for the VPC address block is always present and cannot be deleted.
Security groups are stateful, so allowing inbound traffic implicitly permits the response and you only write rules for one direction of a conversation.
Policy evaluation is an intersection rather than a union: an explicit deny in any applicable policy wins, and anything left unmatched is denied by default.
Questions this pack covers
How should you read a long AWS scenario question before choosing an answer?
Which hard constraints should you extract first from a scenario?
Where exactly does the responsibility boundary sit for EC2?
How does the responsibility boundary change for a managed database service?
How do you plan VPC address space across several environments and regions?
What actually makes a subnet public or private?
How does longest prefix match decide which route a packet takes in AWS?
Why does relying on a single NAT Gateway increase traffic cost?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
