| 주제 | 소개 |
|---|
| 주제 1 | - Getting Data In: This domain addresses the responsibilities of Splunk Administrators in configuring data inputs, differentiating forwarder types, and using the command-line interface for setting up Universal Forwarders.
|
| 주제 2 | - Forwarder Management: This section, intended for Splunk Administrators, tests the candidate's understanding of deployment servers, forwarder apps, client group management, and monitoring forwarder activities across distributed environments.
|
| 주제 3 | - Parsing Phase and Data: Security Operations Engineers are tested on their understanding of event parsing, timestamp recognition, and the use of data preview tools to verify data correctness prior to indexing.
|
| 주제 4 | - Splunk Authentication Management: This domain is intended for Security Operations Engineers and involves integrating LDAP directories, implementing multi-factor authentication, and exploring other authentication mechanisms within Splunk.
|
| 주제 5 | - Getting Data In – Staging: This section is relevant to Splunk Administrators and focuses on the three stages of data indexing—input, parsing, and indexing—and outlines data ingestion options and configurations.
|
| 주제 6 | - Monitor Inputs: Targeted at Splunk Administrators, this domain involves creating and customising monitor inputs for files and directories, including the deployment of remote monitors.
|
| 주제 7 | - Splunk Admin Basics: This section evaluates the foundational knowledge required of a Splunk Administrator, focusing on identifying core components such as indexers, search heads, and forwarders within a Splunk deployment.
|
| 주제 8 | - Network and Scripted Inputs: Security Operations Engineers are assessed on setting up and customising TCP and UDP network inputs, as well as implementing basic scripted inputs for dynamic data ingestion.
|
| 주제 9 | - License Management: Designed for Splunk Administrators, this domain addresses types of Splunk licenses, how to manage them effectively, and the implications of license violations on operational continuity.
|
| 주제 10 | - Configuring Forwarders: Splunk Administrators are assessed on the deployment and configuration of forwarders, along with recognition of additional forwarder functionalities essential for scalable data ingestion.
|
| 주제 11 | - Splunk Indexes: Relevant to Splunk Administrators, this section covers the structure and types of index buckets, data retention policies, integrity checks, and the role of the fishbucket in tracking file inputs.
|
| 주제 12 | - Agentless Inputs: Designed for Security Operations Engineers, this section covers creating agentless inputs using WMI and HTTP Event Collector (HEC), particularly for integrating data from Windows and RESTful sources.
|
| 주제 13 | - Splunk Configuration Files: This part assesses a Splunk Administrator’s ability to navigate the configuration file directory, understand precedence and layering, and use diagnostic tools like btool to verify configuration settings.
|
| 주제 14 | - Fine Tuning Inputs: Splunk Administrators are evaluated on their ability to customise input processing, including sourcetype identification, character encoding, and other configurations for accurate data onboarding.
|