Containers must find the current healthy payments endpoint without hard-coded IPs that change on every deploy. What capability should the platform provide?
Select an answer to reveal the explanation.
Short Explanation
Service discovery is the receptionist who always knows which desk payments sits at today. Hard-coded IPs go stale the moment pods move. Ask the platform, not yesterday's sticky note.
Full Explanation
Service discovery dynamically resolves the network locations of healthy service instances at runtime so clients are not frozen to hard-coded IP addresses that change on every deploy or scale event. Containerized workloads that must find the current healthy payments endpoint therefore rely on platform discovery—DNS, service meshes, or registries—integrated with health and readiness checks. Static hosts files baked into images with last week’s IPs break as soon as instances recycle. Manual whiteboard updates of IP addresses after each rolling deploy cannot keep pace with cloud churn and invite human error during incidents. Disabling all health checks so clients always reuse the first address they saw leaves traffic pinned to failed endpoints and prolongs citizen-facing outages. Exam caveat: discovery without health awareness still sends clients to dead instances—Cloud+ expects dynamic location plus readiness signals, not DNS alone with stale targets. Operational check: register payments instances on start and deregister on shutdown, publish only healthy endpoints, configure client-side retries and timeouts, exercise rolling deploys in a lower environment, and confirm callers shift without emergency configuration pushes.