Question 1: What are the basic advantages of serverless computing?
Answer: advantages are
• no OS instances to manage
• features flexible scaling
• relies on a pay-per-usage model (you only pay for compute time when code is running)
• has built-in fault tolerance,
• requires zero maintenance.
• allows developers to focus entirely on application business logic rather than infrastructure tasks
Question 2: What is the limitation of serverless computing?
Answer: One limitation is that the initial effort to get started is higher due to the steep learning curve and
organizational changes required when moving away from traditional architectures. Additionally, developers
do not have direct control over the underlying ephemeral environments where the Lambda function runs.
Question 3: Basic architectural difference between monolithic and microservice architecture.
Answer:
• monolithic: is a single build of a unified code base that “does everything”; it is hard to scale, requires
compiling the entire application for updates, and a single service failure can take down the whole
application
• microservice: consists of a collection of small, independent services that “do one thing,” which allows
for precise scaling, independent deployments, and high reliability because the failure of one service
does not bring down the whole application
Question 4: How can you call/execute the Lambda function?
Answer:
• manually: using AWS Management Console
• programmatically: using AWS CLI or AWS SDKs within your code
• HTTP Requests: via Amazon API Gateway
• Event triggers: automatically configuring other AWS services like an S3 bucket upload, an EventBridge
timer, or DynamoDB change to trigger the function
Question 5: Does Lambda function support versioning?
Answer: Yes
Question 6: Lambda function supports concurrency. (Yes / No)
Answer: Yes
Question 7: What is the push and pull models in the Lambda functions?
Answer:
• push model: an event source (like S3 or API Gateway) directly invokes the Lambda function the
moment an event occurs
• pull model: an event source puts information into a stream or a queue; Lambda itself continuously
polls the stream or queue and invokes the function when it detects a new event payload.
Question 8: What are the different types of PUSH events?
Answer: Synchronous, Asynchronous
Question 9: What is synchronous and asynchronous invocation in AWS Lambda?
Answer:
• synchronous: the service or user making the request waits for the Lambda function to finish processing
and expects an immediate response or error message back (e.g., querying a database via API Gatelay).
1
• asynchronous: the service hands the event over to Lambda and immediately moves on without waiting
for a response (e.g., S3 triggering a Lambda to resize an image in the background). AWS places the
event in a queue and handles retries automatically if the function fails.
Question 10: What are the different types of PULL events?
Answer: Stream based, Queue based
Question 11: What are the two policies that are attached to the execution role of a Lambda function?
Answer: IAM policy, Trust policy
Question 12: What are the different types of Lambda function deployment packages?
Answer: .zip archives and container images