Sign in
Home/Splunk/Splunk Enterprise Security Certified Admin (SPLK-3001)/Free questions

Splunk Enterprise Security Certified Admin (SPLK-3001) — Free Practice Questions

10 free sample questions from a bank of 144, with the correct answers and explanations. No signup required — start practising right now.

1The Add-On Builder creates Splunk Apps that start with what?
  • DA-
  • SA-
  • TA-
  • App-
Answer: C

The short version

C — Add-On Builder apps start with TA-. Technology add-ons use the TA- prefix by convention, signaling parsing and CIM mapping content rather than domain or suite apps.

Key concepts in this question

  • Add-On Builder: Splunk tool that scaffolds add-ons with props, transforms, inputs and CIM mappings.
  • TA- prefix: Naming standard for technology add-ons that normalize a specific data source.
  • SA- contrast: Support add-ons that provide shared libraries or helpers, not direct data collection.
  • DA- contrast: Domain add-ons that deliver dashboards and data models for a use case area.
  • App- generic myth: No standard ES prefix, it would collide with custom app naming.

Why C is correct

C is correct because Splunk developer guidance states the Add-On Builder creates technology add-ons whose names start with TA-. That prefix tells admins the package holds source-type parsing and field mappings for a technology, ready to feed CIM. The other prefixes belong to different package roles, so only TA- matches builder output for a new data source integration.

Why the others are wrong

  • A. DA- marks domain apps with content for a security domain, not builder-generated parsing add-ons.
  • B. SA- marks supporting apps with shared code, not the primary TA parsing package.
  • D. App- is not a Splunk standard prefix and gives no signal about technology versus domain role.

SPLK-3001 exam tip

Link letters to roles, TA equals technology parsing, SA equals support, DA equals domain content.

2Which indexes are searched by default for CIM data models?
  • notable and default
  • summary and notable
  • _internal and summary
  • All indexes
Answer: D

The short version

D — All indexes are searched by default. CIM data models do not limit themselves to main or summary indexes out of the box, so acceleration searches all indexes for matching tags and fields. Many learners expect a narrow scope, but the default stays broad to catch normalized data anywhere.

Key concepts in this question

  • CIM data models: standardized hierarchical datasets that normalize diverse sourcetypes into common fields and tags for Enterprise Security content.
  • Default index scope: the set of indexes consulted when a data model is accelerated or queried without an explicit indexes constraint.
  • Acceleration and summary storage: background summarization that builds tstats-friendly summaries so searches over large datasets return quickly.
  • Indexes allowlist constraint: optional allowlist in datamodels.conf that an admin can set to narrow scope for performance, which is opt-in rather than default.

Why D is correct

Model definitions without an explicit indexes allowlist stay unconstrained and consider all indexes during acceleration and search. Splunk answers and admin training note this default for CIM models. Admins can restrict the list for performance, but coverage stays global until they do, which maximizes detection coverage for Enterprise Security correlations.

Why the others are wrong

  • A. notable and default are far too narrow and confuse the notable index used for correlation outputs with input search scope.
  • B. summary and notable mix output and summary storage concepts and omit the main production indexes where normalized events actually reside.
  • C. _internal and summary describe internal logs plus summaries, which would miss nearly all security-relevant indexed data.

SPLK-3001 exam tip

Remember default equals all, restriction is manual: if you see indexes allowlist think opt-in performance tuning, not out-of-box behavior.

3What is an example of an ES asset?
  • MAC address
  • User name
  • People
  • Server
Answer: A

The short version

A — A MAC address is tracked as an ES asset identifier. ES asset lookups match events by asset fields such as IP, MAC, DNS and host, so a MAC address is a valid asset example in this key.

Key concepts in this question

  • Assets: Systems and devices ES protects, enriched from asset lookups for context and priority.
  • Asset lookup fields: Columns such as ip, mac, dns and nt_host used to match an event to a known asset.
  • Identities contrast: People and accounts matched by identity, email or nickname, not hardware addresses.
  • Correlation enrichment: Process that adds asset priority and category to notables for urgency and triage.
  • Device example nuance: A full server is also an asset in plain language, but the settled key treats the MAC identifier as the asset marker here.

Why A is correct

A is correct because the settled answer defines a MAC address as the asset example for this question. ES asset correlation explicitly matches on the mac column alongside IP and DNS, so a MAC value resolves to an asset record and inherits its priority and category. That lookup behavior makes the MAC address an asset identifier in ES logic, which is the decisive fact behind the key.

Why the others are wrong

  • B. User name belongs to identities, it resolves in the identity store rather than the asset store.
  • C. People in general points to identities and users, not the system-focused asset inventory.
  • D. Server sounds like an asset in everyday terms, but the key for this row selects the MAC identifier, so it is not the credited choice here.

SPLK-3001 exam tip

If asset versus identity appears, check the column, mac plus ip plus dns equals asset, email plus nickname equals identity.

4Analysts have requested the ability to capture and analyze network traffic data. The administrator has researched the documentation and, based on this research, has decided to integrate the Splunk App for Stream with ES. Which dashboards will now be supported so analysts can view and analyze network Stream data?
  • Endpoint dashboards.
  • Protocol Intelligence dashboards.
  • User Intelligence dashboards.
  • Web Intelligence dashboards.
Answer: B

The short version

B — Splunk App for Stream lights up Protocol Intelligence. Stream captures wire data and ES surfaces it through protocol-focused dashboards for network service and traffic analysis.

Key concepts in this question

  • Splunk App for Stream: Captures raw network packets and reassembles flows into searchable protocol metadata.
  • Protocol Intelligence dashboards: ES views for protocols, sessions and network services built from stream data.
  • Endpoint contrast: Host-centric views from endpoint agents, not wire capture.
  • User Intelligence contrast: Identity and behavior views from authentication and user data.
  • Web Intelligence contrast: HTTP and proxy-focused analysis, narrower than full protocol coverage.

Why B is correct

B is correct because integrating Stream feeds the protocol layer that Protocol Intelligence dashboards consume. Admins add Stream to get packet-derived fields for DNS, DHCP, TCP and related services into ES data models. Those dashboards are the documented consumers of stream-sourced network activity, so analysts gain protocol-level visibility rather than endpoint or user-only views.

Why the others are wrong

  • A. Endpoint dashboards need host agent data such as processes and registry, not packet capture alone.
  • C. User Intelligence needs identity and authentication context, which Stream by itself does not provide.
  • D. Web Intelligence covers web traffic subset, missing the broader protocol value Stream adds.

SPLK-3001 exam tip

Hear Stream and think wire plus protocols, then choose Protocol Intelligence before reading the other options.

5Which setting is used in indexes.conf to specify alternate locations for accelerated storage?
  • thawedPath
  • tstatsHomePath
  • summaryHomePath
  • warmToColdScript
Answer: B

The short version

B — tstatsHomePath sets the alternate accelerated storage location. When data model acceleration needs to live on faster or larger volumes, this indexes.conf setting redirects the tstats summaries away from the default path. It is the only supported knob for relocating accelerated data model storage without moving the whole index.

Key concepts in this question

  • indexes.conf volume settings: per-index stanza settings that control homePath, coldPath, thawedPath and specialized summary paths.
  • tstatsHomePath: dedicated setting that defines where accelerated data model summaries backed by tstats are stored.
  • summaryHomePath: related but distinct setting used for report acceleration summaries, not for data model acceleration.
  • Data model acceleration: persistent summarized representation that makes datamodel and tstats searches fast across long time ranges.

Why B is correct

Splunk documentation for accelerated data models explicitly names tstatsHomePath as the setting for specifying an alternate location for accelerated storage. Setting it in indexes.conf lets admins place high-IOPS summary data on dedicated storage while leaving buckets in place. This separation helps size Enterprise Security deployments where acceleration volume can grow large. No other indexes.conf setting performs this exact relocation for data model summaries.

Why the others are wrong

  • A. thawedPath controls where restored frozen buckets are placed for searchable thaw, not where acceleration summaries live.
  • C. summaryHomePath handles report acceleration for scheduled reports, not data model acceleration queried with datamodel or tstats.
  • D. warmToColdScript defines a script hook for cold transition handling, not a storage path for summaries.

SPLK-3001 exam tip

Link t in tstatsHomePath to t in tstats summaries: report acceleration uses summaryHomePath, model acceleration uses tstatsHomePath.

6Which of the following is a way to test for a property normalized data model?
  • Use Audit -> Normalization Audit and check the Errors panel.
  • Run a | datamodel search, compare results to the CIM documentation for the datamodel.
  • Run a | loadjob search, look at tag values and compare them to known tags based on the encoding.
  • Run a | datamodel search and compare the results to the list of data models in the ES normalization guide.
Answer: B

The short version

B — Run a piped datamodel search and validate fields against CIM docs. Proper normalization testing means executing the model and comparing returned fields and tags to the published CIM reference for that dataset. This proves the mapping works in search, not just that config files exist.

Key concepts in this question

  • CIM normalization: field aliases, tags and eventtypes that map raw sourcetype fields into standard models like Network Traffic or Authentication.
  • Pipe datamodel search: syntax such as from datamodel that materializes model datasets in search for inspection and validation.
  • CIM reference documentation: per-model tables listing required fields, tags and expected values that define correctness.
  • Audit vs functional test: checking an audit dashboard may surface errors, but direct search proves usable normalized output.

Why B is correct

The CIM guide for normalizing data at search time describes testing by running a datamodel search and comparing results to CIM documentation for that model. If expected tags appear and required fields populate with sensible values, the property mapping is working. Missing fields or untagged events immediately reveal broken TA mappings or unmapped sourcetypes. This method directly validates what Enterprise Security content will consume.

Why the others are wrong

  • A. Audit Normalization Audit Errors panel can hint at issues but it is an indirect health check, not the defined functional test for a specific property mapping.
  • C. loadjob plus tag comparison misstates the workflow and tag checks based on encoding do not validate CIM field conformance.
  • D. comparing datamodel output to the list of models in the ES normalization guide only confirms which models exist, not whether fields normalize correctly.

SPLK-3001 exam tip

Think run it and read the spec: datamodel search plus CIM field table is the normalization test to pick on exam day.

7Which argument to the | tstats command restricts the search to summarized data only?
  • summaries=t
  • summaries=all
  • summariesonly=t
  • summariesonly=all
Answer: C

The short version

C — summariesonly=t limits tstats to summarized data only. This Boolean-style argument tells tstats to skip raw events and use only accelerated summaries from data models. It is the standard way to verify acceleration coverage and to force fast summary-only queries.

Key concepts in this question

  • tstats command: high-performance search command that reads indexed fields and accelerated summaries without retrieving raw events.
  • summariesonly argument: toggle that when true restricts results strictly to data already summarized by acceleration.
  • Accelerated data models: prebuilt summaries keyed by time and fields that tstats can scan far faster than bucket raw data.
  • Summaries versus raw fallback: default tstats may combine summaries and raw data, so forcing summaries-only changes completeness and speed tradeoffs.

Why C is correct

Splunk Search Reference and accelerated data model docs show summariesonly=t in examples such as querying min and max time from datamodel=mydm to inspect summary range. Setting it to t means true and eliminates raw-data fallback, so results reflect exactly what acceleration has built. That makes it ideal for checking whether acceleration is keeping up or for guaranteeing consistent fast performance. No other listed parameter has this strict summary-only semantic.

Why the others are wrong

  • A. summaries=t is not the documented flag for summary-only mode and does not enforce the strict summarized-only restriction.
  • B. summaries=all suggests combining sources rather than restricting to summaries only, so it cannot guarantee summary-only behavior.
  • D. summariesonly=all mixes the correct argument name with an invalid value, since the toggle expects a Boolean true value not all.

SPLK-3001 exam tip

Memorize the exact pair: summariesonly plus equals t means only, any variant with all or bare summaries is a distractor.

8When investigating, what is the best way to store a newly-found IOC?
  • Paste it into Notepad.
  • Click the ג€Add IOCג€ button.
  • Click the ג€Add Artifactג€ button.
  • Add it in a text note to the investigation.
Answer: C

The short version

This asks the best way to store a newly found IOC during investigation, and the correct answer is C, Add Artifact. The banked key said B, Add IOC, but vendor prose notes there is no button called Add IOC. Community voting unanimously favors C, so the verdict flips to C.

Key concepts in this question

ES investigations use the workbench and artifact model to preserve observables, files, and notes. Artifacts are the structured container for indicators found during analysis. Text notes and external notepads lack enrichment and linkage. A dedicated IOC button is not part of the tested workflow.

Why C is correct

C uses the investigation artifact workflow that attaches the IOC to the case with context. Artifacts support further action, sharing, and review inside the investigation. That matches the vendor note that no Add IOC button exists. Community agreement adds weight to the documented workflow.

Why the others are wrong

A, pasting into Notepad, loses linkage to the investigation and prevents enrichment. B, Add IOC button, names a control that vendor prose says does not exist. D, adding only a text note, is weaker than creating a structured artifact for response. C alone creates reusable investigative data.

SPLK-3001 exam tip

For investigation storage stems, prefer Add Artifact over notes or external tools. If an option names a button that does not exist, eliminate it. Remember artifacts as the IOC container in ES investigations.

9How is it possible to navigate to the list of currently-enabled ES correlation searches?
  • Configure -> Correlation Searches -> Select Status ג€Enabledג€
  • Settings -> Searches, Reports, and Alerts -> Filter by Name of ג€Correlationג€
  • Configure -> Content Management -> Select Type ג€Correlationג€ and Status ג€Enabledג€
  • Settings -> Searches, Reports, and Alerts -> Select App of ג€SplunkEnterpriseSecuritySuiteג€ and filter by ג€-Ruleג€
Answer: C

The short version

C — Find enabled searches under Content Management. Filter Content Management by Type Correlation and Status Enabled to list currently enabled ES correlation searches in one place.

Key concepts in this question

  • Content Management: ES console for browsing, enabling and editing all security content by type and status.
  • Correlation searches: Detection logic that generates notables, managed as content objects with status flags.
  • Type filter: Narrows the list to correlation objects instead of lookups, models or views.
  • Status filter: Narrows further to enabled versus disabled, giving the active detection set.
  • Splunk native search page contrast: Generic Settings page lacks ES status and type facets.

Why C is correct

C is correct because ES documents Content Management as the path to view and manage correlation searches, with filters for Type Correlation and Status Enabled. That combination returns exactly the currently enabled detections without manual name guessing. The Configure menu path is the ES-specific workflow, while generic Splunk settings or partial Configure paths miss the required filters.

Why the others are wrong

  • A. Configure plus Correlation Searches plus Status Enabled sounds close but misses the Content Management hub where filters live.
  • B. Settings plus Searches Reports and Alerts is the core Splunk page, it lacks ES content type and status filtering.
  • D. Filtering by app and Rule suffix in core settings is indirect and error prone compared to Content Management facets.

SPLK-3001 exam tip

Enabled ES searches always mean Configure plus Content Management plus Type plus Status, memorize that four-part path.

10Which of the following is a risk of using the Auto Deployment feature of Distributed Configuration Management to distribute indexes.conf?
  • Indexers might crash.
  • Indexers might be processing.
  • Indexers might not be reachable.
  • Indexers have different settings.
Answer: D

The short version

D — One shared push can clobber per-indexer differences. Auto Deployment sends a single indexes.conf to every indexer, so any indexer that previously had unique retention, paths or volumes is at risk of being overwritten and diverging from expected behavior.

Key concepts in this question

  • Distributed Configuration Management: ES search-head tool that builds the Splunk_TA_ForIndexers package and pushes shared configs to indexers.
  • indexes.conf: Defines indexes, home and cold paths, retention and volumes, so inconsistency breaks search, replication and retention.
  • Auto Deployment: Push model that replaces target files automatically, with no merge of pre-existing local edits.
  • Indexer divergence: Independent local settings for sizes, paths or retention that were tuned per host before central management.
  • Manual reconciliation: Practice of auditing each indexer for local differences before enabling automatic push.

Why D is correct

D is correct because Auto Deployment distributes one common indexes.conf to all indexers. If indexers previously had different settings for retention, storage paths or custom indexes, the single pushed file overwrites those local variations. That creates retention surprises, path errors or missing indexes, which is exactly the documented risk of auto pushing indexes.conf without first normalizing every indexer.

Why the others are wrong

  • A. Crashes are not the expected outcome, the service restarts and loads the new file rather than crashing outright.
  • B. Processing state does not block deployment, indexers continue to index while files are replaced and reloaded.
  • C. Reachability is a delivery concern handled by deployment clients, not the specific content risk of pushing indexes.conf itself.

SPLK-3001 exam tip

Remember auto push equals one file for all indexers, so think overwrite risk first whenever indexes.conf and Auto Deployment appear together.

Want the full bank of 144 questions for Splunk Enterprise Security Certified Admin (SPLK-3001)? See all practice exams.