Spring Boot reads configuration from many sources with a clear precedence (later wins): application.yml → application-{profile}.yml → environment variables → command-line args. Mechanism Example Profiles spring.profiles.active=prod (env: SPRINGPROFILESACTIVE=prod) Profile-specific file application-prod.yml Multi-document YAML --- + spring.config.activate.on-profile: dev Env var mapping app.payment.timeout ← APPPAYMENTTIMEOUT (relaxed binding) Typed config @ConfigurationProperties(prefix = "app.payment") record + validation Single value @Value("${app.name:demo}") (fine for one-offs) Profile-only beans @Profile("dev") Secrets env vars, Vault / AWS Secrets Manager via Spring Cloud, never Git Prefer @ConfigurationProperties records over scattered @Values: type-safe, validated at startup…