Multiple ChoiceIntermediate 30s
Secrets management
Choose the best answer for: sensitive config
Options
- 1Shared credentials committed to the repo so every teammate can reuse
- 2A public repository holding all secrets in plaintext for easy access
- 3GitHub Secrets, Vault, env vars — never in code or git history
- 4Secrets stored directly in the source code and committed to git history
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.