SAP-C02 Practice Question: Accelerate Workload Migration and Modernization
A company is modernizing a legacy CRM application to a microservices architecture on AWS. They want to use AWS Lambda for compute and Amazon API Gateway for the API layer. Which THREE design patterns should they consider? (Select THREE.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Decompose the monolith into separate Lambda functions for each business capability
The three design patterns for this serverless microservices architecture are: B (Decompose the monolith into separate Lambda functions for each business capability), C (Use API Gateway to expose each microservice as a REST API), and E (Use AWS Step Functions to orchestrate multiple Lambda functions). Options A and D are incorrect: A (ElastiCache) is a caching solution, not a core microservices pattern, and D (EC2 Auto Scaling) introduces server-based compute, which contradicts the serverless approach.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Amazon ElastiCache for session state management
Why it's wrong here
Amazon ElastiCache is a caching service, not a core microservices design pattern. While it can be used for session state, it is not one of the three fundamental patterns for decomposing a monolith into serverless microservices.
- ✓
Decompose the monolith into separate Lambda functions for each business capability
Why this is correct
Decomposing the monolith into separate Lambda functions for each business capability aligns with microservices principles, enabling independent development, deployment, and scaling.
- ✓
Use API Gateway to expose each microservice as a REST API
Why this is correct
Using API Gateway to expose each microservice as a REST API provides a managed API layer, handling authentication, throttling, and routing.
- ✗
Use EC2 Auto Scaling groups for each microservice
Why it's wrong here
Using EC2 Auto Scaling groups introduces server-based compute, which contradicts the serverless approach using Lambda. This is not a recommended pattern for a serverless microservices architecture.
- ✓
Use AWS Step Functions to orchestrate multiple Lambda functions
Why this is correct
AWS Step Functions orchestrates multiple Lambda functions, allowing coordination, error handling, and workflow management in serverless applications.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
About these practice questions
Courseiva writes every SAP-C02 question from scratch — 1,660 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.