A SAM project for a county records API packs unit tests, Markdown docs, and multi-gigabyte sample media into the same directory that becomes the deployment bundle. What should the team change?
Select an answer to reveal the explanation.
Short Explanation
Deployment packages are not attic storage. Keep tests, docs, and giant sample scans out of the SAM packaging path so uploads stay lean and cold starts stay sane. Timeout hikes and stuffing media into source just paper over a bad layout.
Full Explanation
Domain 3 packaging skills include organizing directory structure so build and package steps ship only what the runtime needs. Tests, documentation, and large sample media inflate upload size, increase deploy time, and can push Lambda package limits. SAM/CloudFormation packaging should target application code and declared dependencies. Changing timeouts, abusing layers as a catch-all, or inlining media does not fix the packaging boundary.