What role does the agent's own log play when an agent is not reporting?
Select an answer to reveal the explanation.
Short Explanation
The agent's own log usually tells you what went wrong. Reading it turns guesswork into one targeted fix.
Full Explanation
The agent log is the first place to look because it usually records the specific failure—such as a rejected key, an unreachable endpoint, or a permission error—and that detail turns guesswork into one targeted fix. The claim that it contains application traces otherwise sent to the backend is wrong: the log is diagnostic output, not application telemetry. The claim that it records only successful startups and stays silent about failures is wrong because failures are exactly what it records. The claim that it should be checked only after reinstalling the agent is wrong because reading the log first often avoids the reinstall entirely. For the exam, place the agent log early in the troubleshooting sequence.