A SAM application is deployed to test and production using the same source. Resource names and configuration differ by environment. Which approach supports repeatable deployment?

1. Use the template parameters and environment-specific deployment configuration while keeping secrets outside source.
2. Use a single untracked file containing every environment secret.
3. Hard-code test database identifiers into every production deployment.
4. Manually edit production resources after each deployment and leave the template stale.