ACorrect
AWS Lambda — Executes code in an event-driven manner without managing servers.
This is correct. AWS Lambda is serverless, executes code in response to events, and charges only for execution time.
Which TWO combinations of an AWS compute service and its characteristic are correct? (Choose TWO.)
1 / 1
Select all that apply
CorrectA, C
Explanation
A question asking to select the two correct pairings of compute service and its characteristic.
- 1「compute service and its characteristic」Correctly match Lambda/EC2/Fargate/EKS with their respective execution models.
BIncorrect
Amazon EC2 — A serverless service that requires no server management whatsoever.
Amazon EC2 is a service that provides virtual servers, and customers are required to manage instances and operating systems.
Describing EC2 as serverless is incorrect.
CCorrect
AWS Fargate — Runs containers in a serverless manner, eliminating the need to manage the underlying EC2 instances.
This is correct. AWS Fargate runs containers serverlessly in combination with ECS/EKS, eliminating the need to manage the underlying EC2 instances.
DIncorrect
Amazon EKS — A serverless service that executes only code in an event-driven manner.
Executing only code in an event-driven, serverless fashion is the description of AWS Lambda.
Amazon EKS is a container orchestration service for running managed Kubernetes clusters, and the description is incorrect.
EIncorrect
AWS Lambda — Has no execution time limit and is well suited for running long-lived resident processes.
AWS Lambda has a maximum execution time limit of 15 minutes and is designed for short-duration processing that starts and ends per event.
For long-lived resident processes, EC2 or containers (ECS/Fargate) are appropriate, so this description is the opposite of Lambda's characteristics and is incorrect.
Key Takeaway
Mapping: Lambda = serverless function (execution time limit; not suited for resident processes) / Fargate = serverless containers / EC2 = server management required / EKS = managed Kubernetes. Distinguish by the presence or absence of server management and the execution model.