Which statement best summarises the use of service naming rules?
Select an answer to reveal the explanation.
Short Explanation
You want naming rules enforced in the platform so every discovered service gets a stable, distinct, recognisable name. That keeps alerts, dashboards, and investigations usable when you're hunting problems.
Full Explanation
Apply naming rules in the platform so discovered services carry stable, distinct and recognisable names that alerts, dashboards and investigations rely on. Applying those three properties in the platform, not documentation, makes discovered services usable operationally.
Keeping discovered identifiers unchanged and translating them in documentation when needed is wrong because live views remain unreadable and translation lands during incidents.
Standardising on one shared application name so components group together is wrong because shared names make components indistinguishable.
Including deployment identifier in each name so current version is always visible is wrong because version-bearing names change with each release and break historical continuity.
Exam: name all three properties.