AWS Certified Developer - Associate DVA-C02

The best-practice approach is multiple API Gateway stages (test and production), a dedicated Lambda function for each environment, and API Gateway stage variables to route traffic to the appropriate Lambda. This provides true environment isolation, cleaner separation of concerns, and better auditability. Single-stage approaches (A, D) mix concerns; a single Lambda with environment variables (B) is less isolated and harder to troubleshoot independently.

The NoSuchBucket error occurs because the CDK deployment bootstrap resources have not been created in the new AWS account. The cdk bootstrap command creates the necessary S3 bucket and other bootstrap infrastructure required for CDK asset deployment. cdk synth only generates the CloudFormation template, cdk init creates new projects, and cdk destroy removes resources.

Lambda has a hard 250 MB unzipped size limit; quota increases cannot override this architectural constraint (A is invalid). Breaking functions into modules (C) reduces individual package sizes and aligns with microservices patterns. Moving dependencies and runtimes to Lambda layers (E) keeps deployment packages lightweight while sharing common libraries across functions. Double-zipping (D) offers no benefit since decompression still yields the same unzipped size.

CAPABILITY_NAMED_IAM is required when deploying IAM resources with custom (user-defined) names in CloudFormation. CAPABILITY_IAM alone permits only unnamed IAM resources. Custom resource names require explicit acknowledgment that the user understands the implications of custom naming.

A Dead Letter Queue (DLQ) configured with SQS captures failed asynchronous Lambda invocations after retries, allowing developers to inspect error details and investigate failures. CloudTrail logs API calls but not Lambda invocation failures, Simple Workflow and Config are not designed for Lambda failure analysis, and this is the standard troubleshooting mechanism for async Lambda failures.