A city permitting portal bakes stage-specific API base URLs into the built Lambda zip, so every environment change forces a full rebuild. What should the developers do?
Select an answer to reveal the explanation.
Short Explanation
Think of the zip like a sealed lunchbox—same sandwich, different sticky notes for each cafeteria. Bake the code once, then inject API URLs with env vars, AppConfig, or Parameter Store so you are not rebuilding for every stage. Editing live zips or shipping four Git artifacts is how civic deploys turn into spaghetti.
Full Explanation
DVA-C02 expects deployable artifacts to stay as environment-agnostic as possible. Stage-specific endpoints belong in configuration injected at deploy or runtime—Lambda environment variables, AWS AppConfig, Systems Manager Parameter Store, or Secrets Manager—rather than being compiled into the package. That pattern lets one immutable artifact promote from sandbox to production. Baking URLs into builds, checking in per-stage binaries, or hand-editing production packages breaks reproducibility and slows municipal release cycles.