Unit 4 Final Review and Readiness Check

Learning outcomes

By the end of this lesson, the learner can:

1. Explain the core role of the main AWS services covered in Unit 4.
2. Choose the right service for a basic scenario without guessing randomly.
3. Recognize where they are strong and where they still need review.
4. Decide whether they are ready to move from service recognition into broader review and scenario practice.

---

What "ready" means here

Being ready at the end of Unit 4 does not mean knowing every AWS feature. It means you can look at a simple requirement and choose the right service category and a reasonable first-fit architecture. For example, you should now be able to tell the difference between a managed virtual server path like EC2 + load balancing + Auto Scaling, a simpler bundled path like Lightsail, a container path like ECS, a relational path like RDS/Aurora, a NoSQL path like DynamoDB, an analytics path like Redshift, a processing path like EMR, and a graph path like Neptune. AWS's service docs draw those role boundaries clearly. (AWS Documentation)

---

Unit 4 review

CSV version:

Area,Ready if you can do this
Compute,Explain when to use EC2 and how ELB plus Auto Scaling fit around it
Storage,Choose an S3 storage class and explain EBS vs EFS vs FSx
Data transfer,Recognize when Snow Family-style thinking matters because the network is the problem
Relational data,Explain RDS vs Aurora in plain terms
NoSQL data,Explain when DynamoDB is a better fit than a relational database
Caching,Explain why ElastiCache sits in front of a slower source of truth
Analytics,Explain Redshift vs EMR
Graph / ledger concept,Explain Neptune and explain QLDB mainly as a ledger concept with an end-of-support status note
Containers / app platform,Explain ECS vs Lightsail
Infrastructure as code,Explain template stack change set and drift in CloudFormation

This checklist matches the core roles AWS documents for EC2 Auto Scaling and ELB, S3 classes, Lightsail, RDS, DynamoDB, Redshift, EMR, Neptune, ECS, and CloudFormation. AWS's QLDB docs also now include an end-of-support notice, which is why it should be treated mainly as a concept here rather than a current new-build recommendation. (AWS Documentation)

---

Readiness Drill: Match the Workload to Its Service

---

Final readiness drill

Answer these without looking back:

1. A small website needs the easiest bundled AWS starting point.
2. A containerized API needs scaling and load balancing without managing servers.
3. A workload needs a persistent disk for one EC2 instance.
4. A workload needs shared Linux file access across multiple compute resources.
5. A team wants managed relational MySQL/PostgreSQL.
6. A team wants serverless NoSQL with unpredictable traffic.
7. A team wants SQL warehouse analytics.
8. A team wants Spark or Hadoop processing.
9. A fraud team needs relationship-heavy queries.
10. A team wants infrastructure in YAML/JSON with preview-before-update safety.

Strong answers would be:

1. Lightsail
2. ECS on Fargate
3. EBS
4. EFS
5. RDS or Aurora
6. DynamoDB
7. Redshift
8. EMR
9. Neptune
10. CloudFormation. These choices line up directly with the current AWS service descriptions. (AWS Documentation)

---

Where learners are usually still weak

The most common weak spots at this stage are:

• mixing up RDS/Aurora and DynamoDB
• mixing up Redshift and EMR
• mixing up ECS, EC2, and Lightsail
• forgetting that CloudFormation is about repeatable infrastructure, not just "deployment"
• forgetting that S3 storage classes are about access pattern and retrieval needs, not just "cheap vs expensive." AWS's docs on those services support exactly those boundaries. (AWS Documentation)

---

Simple scoring guide

Use this self-check:

CSV version:

Score,Meaning
9 to 10 correct,Ready to move on confidently
7 to 8 correct,Good overall but review weak spots once more
5 to 6 correct,Partial understanding review Unit 4 modules before moving on
Below 5 correct,Revisit the service-comparison lessons first

That scoring guide is a course-design recommendation, based on the fact that Unit 4's goal is service recognition and first-fit selection rather than deep implementation mastery.

---

Summary

If a learner can now explain the role of EC2 and Auto Scaling, choose the right storage pattern, separate relational from NoSQL, separate analytics from processing, identify Neptune as the graph service, choose ECS or Lightsail appropriately, and explain why CloudFormation matters for repeatable infrastructure, then Unit 4 has done its job. AWS's current docs define those service roles clearly, and that is the real foundation this unit was meant to build. (AWS Documentation)

The natural next move is Unit 5, where the focus shifts from "What service is this?" to "How do I reason across domains, compare close choices quickly, and answer scenario questions with confidence?"