Why are generated deployment identifiers a poor choice for permanent service names?
Select an answer to reveal the explanation.
Short Explanation
Generated deployment identifiers are opaque and change with each deployment, so historical comparison breaks and you cannot tell which service an alert refers to. Meaningless and unstable names are the two worst properties a name can have.
Full Explanation
Generated deployment identifiers are opaque and change with each deployment, so historical comparison breaks and no operator can tell which service an alert refers to. A name that changes on redeploy fragments the history of a single logical service, and a name nobody recognises forces a lookup step during exactly the moments when speed matters. The claim that Instana truncates long identifiers is incorrect because display truncation is a minor symptom rather than the objection. The claim that identifiers cannot be used in alert configurations is incorrect because identifiers are technically usable in configuration; they are simply unhelpful. The claim that identifiers consume more storage than descriptive names is incorrect because storage is irrelevant here. For the exam, require names that are stable across deployments and meaningful to operators.