The Twelve-Factor methodology requires configuration to be separated from application code and backing services to be treated as attached resources. Oracle ' s Twelve-Factor guidance specifically recommends keeping configuration outside the Docker image and supplying deployment-specific values through the environment. This allows the same application artifact to move between development, test, and production without rebuilding it. Kubernetes ConfigMaps or environment variables implement this principle effectively. The backing-services factor similarly treats databases, queues, caches, and external services as replaceable resources referenced through configuration rather than hardcoded dependencies. Consequently, switching a database or message broker should require configuration changes rather than application-code changes. Hardcoding credentials or environment-specific values violates configuration separation, while sharing one database across environments is not required for dev/prod parity. Therefore, B and D are correct.

Top of Form

Bottom of Form