SPLK-1005 practice question 8 of 10

What is the recommended approach to collect data from network devices?

Full set: 80 questions

Domain Monitoring, Alerting, and Incident Response

Answer options
A: TCP/UDP Feed > Heavy Forwarder > Intermediate Forwarder > Splunk Cloud
B: TCP/UDP Feed > Syslog Server with Universal Forwarder > Splunk Cloud Correct answer
C: TCP/UDP Feed > Universal Forwarder > Intermediate Forwarder > Splunk Cloud
D: TCP/UDP Feed > Intermediate Forwarder > Heavy Forwarder > Splunk Cloud
Correct Answer:
B. TCP/UDP Feed > Syslog Server with Universal Forwarder > Splunk Cloud
Explanation

The most reliable and scalable method for collecting network data, such as syslog, is to use a dedicated syslog server (e.g., syslog-ng, rsyslog). This server listens for the TCP/UDP feeds and writes the data to log files. A Splunk Universal Forwarder is then installed on this syslog server to monitor these files and securely forward the data to Splunk Cloud. This architecture decouples data collection from forwarding, providing buffering and preventing data loss if the forwarding agent is temporarily unavailable. It is the standard best practice recommended by Splunk for production environments.

Why Incorrect

A. Using a Heavy Forwarder directly for collection is less resilient than a dedicated syslog server and is not the primary recommended method.
C. A Universal Forwarder can listen on a port, but it's not recommended for production syslog due to potential data loss (especially with UDP).
D. This data flow is architecturally incorrect; the Heavy Forwarder's role (if used for parsing) should be earlier in the data pipeline. ---

References

1. Splunk Enterprise Documentation, Getting Data In Manual, "Get data from TCP and UDP ports": In the section "Best practices for configuring syslog input," the documentation explicitly states: "For syslog data in a production environment, Splunk recommends that you configure a separate syslog server to receive the data, and then use a universal forwarder to read the syslog data from files on that server. This method is more robust and scalable than receiving syslog directly."

2. Splunk Cloud Platform Documentation, Getting Data In Manual, "Get data from TCP and UDP ports on a universal forwarder": This section reinforces the best practice, stating, "For production environments, Splunk recommends that you do not configure a universal forwarder to receive data directly over TCP or UDP. Instead, configure a syslog server to receive the data and write it to a file. Then, configure the universal forwarder to monitor the file."

3. Splunk Validated Architectures, "Data Collection for Splunk Enterprise": This guide details reference architectures. In the section on "Network and Syslog Data," the recommended architecture diagram shows network devices sending data to a dedicated syslog server tier, with Universal Forwarders installed on that tier to collect and forward the data. This confirms the pattern of Syslog Server > Universal Forwarder.

Scroll to Top