CV0-004 Deployment Practice Question
A team is developing a serverless application on AWS Lambda. The application uses several third-party libraries that are large in size. To reduce deployment package size and enable reuse across functions, the team wants to include these libraries as a separate layer. However, the total unzipped size of all layers exceeds the Lambda limits. What should the team do to resolve this?
⚠ Common exam trap
CV0-004 often tests the misconception that layer size limits can be raised via support tickets or that consolidating layers reduces total size — candidates must recognize the 250 MB unzipped hard limit and the container image escape hatch.
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
✓
Use a container image for the Lambda function instead of layers
AWS Lambda has a hard limit of 250 MB unzipped for the combined deployment package and all layers. When layers exceed this, packaging the function as a container image (up to 10 GB) is the supported workaround. Container images can include large third-party libraries directly in the image, bypassing the layer size limit while still allowing reuse via shared base images.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the Lambda function's reserved concurrency
Why it's wrong here
Concurrency does not affect package size.
- ✓
Use a container image for the Lambda function instead of layers
Why this is correct
Container images bypass the layer unzipped-size ceiling entirely, since Lambda permits images up to 10 GB. Packaging the large third-party libraries into the image satisfies the stem's constraint that combined layer size exceeds the limit, while still allowing reuse across functions via a shared image base.
- ✗
Reduce the number of layers by combining libraries into fewer custom layers
Why it's wrong here
Combining does not reduce total size.
- ✗
Request a service limit increase from AWS for layer size
Why it's wrong here
Layer size limits are not adjustable.
Visual reference
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
One of 834 original CV0-004 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This CV0-004 practice question is part of Courseiva's free CompTIA 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 CV0-004 exam.