Question 440
A platform change attempts to resolve the following condition: An installed universal forwarder tails files but never connects to the central indexer. What observable outcome would demonstrate success?
Explanation
Correct Answer
The stated evidence tests the necessary effect: A new file line appears on the target indexer with forwarder connection health normal. It follows from collecting bytes locally does not deliver them unless forwarding outputs and receiver connectivity are correct. The corresponding corrective step is configure an allowed receiving target in outputs.conf and verify the indexer receiving port and network path.
Incorrect Answers
The option would apply to “A forwarder uses plaintext delivery across an untrusted segment where security requires encryption”. A certificate-validation test rejects an invalid peer while permitted events arrive securely. This question instead requires “A new file line appears on the target indexer with forwarder connection health normal”.
The related but distinct situation is “A fleet forwards to one receiver although the design requires capacity sharing across several receivers”. A controlled receiver outage preserves forwarding to the remaining approved targets. For the stated problem, “A new file line appears on the target indexer with forwarder connection health normal” addresses the central condition.
A valid test of that kind belongs to A project treats a deployment server as an agent that reads host logs instead of configuring agents. In this case the relevant remediation is Configure an allowed receiving target in outputs.conf and verify the indexer receiving port and network path. and verification is A new file line appears on the target indexer with forwarder connection health normal.