Why should raised log levels be scoped to specific components rather than applied globally?
Select an answer to reveal the explanation.
Short Explanation
You already know roughly where the problem is. Logging everything drowns that area in output from everywhere else. Scope the raised log level narrowly so the detail stays readable and the cost stays limited.
Full Explanation
The correct answer is the option stating that narrow scope keeps the relevant detail readable and limits the resource cost to the part of the system actually under investigation. Investigations are usually localised to a sensor, a component, or a host. Raising verbosity there produces a manageable volume in which the relevant entries stand out, and confines the performance and storage impact to that scope.
The claim that global log level changes are not supported by Instana agents is incorrect because global changes are possible; they are simply a poor default for troubleshooting.
The claim that global changes require a full backend restart to take effect is incorrect because a backend restart is not what makes global changes undesirable.
The claim that component-level logging captures more detail per component than global logging does is incorrect because the detail level per component is the same either way; the difference is how much unrelated output accompanies it.
For the exam, justify narrow scope by readability and bounded cost.