The Lambda we covered in Week 3 is not a simple "serverless function". The Firecracker MicroVM execution model, the reliability models of the three invocation styles, the deployment lifecycle of versions, aliases, and layers, and the four layers of concurrency control — all of these are a single system, organically connected.
Today, rather than memorizing, we redraw the whole map with the question "why was it designed this way?" Then we check our real-exam instincts with 12 scenario questions in the form that actually appears on the test.