DOP-C02 Practice Question 66: Lambda Code Signing Signer
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 7 · question 6 of 10
A security team wants to guarantee that only Lambda deployment packages built and signed by the company's trusted CI pipeline can ever be deployed to a set of production functions, and that any tampered or unsigned package is rejected by Lambda itself at deployment time rather than merely flagged after the fact. Which combination of steps achieves this?
Show answer and explanation
Answer:
Lambda code signing integrates with AWS Signer: the CI pipeline signs the build artifact using a signing profile, and a code signing configuration (CSC) attached to the function lists the allowed signing profiles and a validation policy. Setting that policy to Enforce means Lambda checks the signature at deployment time and rejects any UpdateFunctionCode or CreateFunction call whose package is unsigned, signed by an untrusted profile, or has been altered since signing. Option A only restricts who can write to the artifact bucket; it does not stop a package from being deployed directly through the Lambda API by a caller with lambda:UpdateFunctionCode permissions, and it provides no cryptographic integrity check. Option B describes Amazon Inspector, which scans for vulnerabilities after deployment and has no deployment-time signature enforcement mechanism. Option D is a custom, brittle workaround that runs after the unsigned code has already been deployed and executed, so it cannot block the deployment itself.
Reference: Configuring code signing for AWS Lambda