Which two controls can be configured on a GitHub Actions environment to harden production deployments? (Choose two)
Select all correct answers, then click Submit.
Short Explanation and Infographic
Environments support required reviewers and wait timers (plus deployment branch/tag rules and environment secrets). They do not delete repos or disable HTTPS on the API.
Full explanation below image
Full Explanation
GitHub Environments attach protection rules to jobs that set environment: name: production (or similar). Common rules include required reviewers (manual approval gates), wait timers (forced delay), and deployment branch/tag restrictions limiting which refs can deploy. Environment-specific secrets and variables further isolate credentials from non-production jobs. Automatic repository deletion is not an environment feature. Disabling HTTPS is not a control and would be insecure. Combining environments with concurrency groups yields strong production controls: approvals, delays, branch allowlists, and single-flight deploys. On GH-200, map environment protection to human gates in CI/CD, distinct from branch protection on PRs though both can apply together.