Why is monitoring only server hostnames insufficient for understanding service health?
Select an answer to reveal the explanation.
Short Explanation
The hostname is an address, not a measurement. It's genuinely useful for locating a problem once you know there is one - it just cannot tell you that there is one.
Full Explanation
The correct answer is the option stating that hostnames identify where a service runs but carry no information about response time, demand, failure rate, or resource pressure. Health is a question about behaviour: how fast, how much, how often failing, how close to capacity. The hostname answers none of those; it is context for locating a problem, not evidence of one.
The option claiming hostnames change too frequently in modern environments to be recorded reliably is incorrect because host churn in dynamic environments is a real challenge but not the reason hostnames fail as a health signal - a perfectly stable hostname is equally uninformative.
The option claiming Instana cannot associate a hostname with a monitored service is incorrect because Instana does associate hosts with the services running on them; that association is part of its topology.
The option claiming hostname monitoring is available only in self-hosted deployments is incorrect because host monitoring is not restricted by deployment model.
For the exam, distinguish inventory and topology data from the measurements that indicate health.