A tax-assessment service hardcodes localhost Redis and a compile-time JDBC driver path so developers can run “everything on one laptop.” Which cloud-native adjustment treats those collaborators correctly?
Select an answer to reveal the explanation.
Short Explanation
Backing services are like municipal utility hookups: you plug into water or power by address and credential, and you can point the hose at a different hydrant later. Hardcoded localhost and compile-time assumptions glue the service to one laptop. Rebindable URL-plus-credential attachments keep it movable.
Full Explanation
Twelve-factor style design treats collaborators as attached resources addressed by configuration. That lets operators retarget test versus production instances without rewriting code. Compile-time embedding, permanent single-host binds, and production-only mocks destroy portability. This item is about the design stance, not naming a specific OCI queue product as the answer core.