10 free sample questions from a bank of 161, with the correct answers and explanations. No signup required — start practising right now.
A — Lowering search factor saves far more disk than lowering replication factor. Searchable copies carry index files plus rawdata while replicas carry only rawdata, so trimming searchables saves most.
Setting the cluster search factor to N minus 1 removes one full searchable copy from the retention equation across the cluster. Each searchable copy removed frees far more disk than removing a lean non-searchable copy. Vendor prose confirms replicated non-searchable copies are smaller since they lack associated index files, so reducing search factor has the greater reduction effect. In an ES cluster with heavy index files, this dominates the other options.
Remember search factor costs more disk than replication factor because searchable means tsidx plus rawdata, while replica-only means rawdata alone.
BC — LINE_BREAKER and ANNOTATE_PUNCT affect indexing performance at index time. They run during parsing on every event, while REPORT runs at search time and SHOULD_LINEMERGE alone is a merge toggle with lighter cost.
LINE_BREAKER requires regex evaluation across incoming bytes to decide event splits, which consumes parsing CPU on every kilobyte ingested. ANNOTATE_PUNCT adds extra token metadata per event that must be written into index structures, increasing both CPU and IOPS during indexing. Architecting guidance cited in vendor prose flags these two as performance-relevant index-time attributes. REPORT executes at search time and therefore cannot slow the indexing path, while SHOULD_LINEMERGE is not among the settled performance pair for this question.
Link index-time cost to LINE_BREAKER plus ANNOTATE_PUNCT, and link REPORT to search time.
Banked key AB is incomplete. The correct set is ABD because serverclass.conf supports DNS name, IP address, and platform machine type as client filters, while server role is not a filter.
Server classes group deployment clients for app delivery. Membership is set by filters in forwarder management or serverclass.conf. Splunk defines three kinds: Include, Exclude, and Machine type. Include and Exclude match on IP address, host name, DNS name, or clientName. Machine type matches hardware strings via machineTypesFilter. SPLK-2002 often tests the mapping between UI fields and conf attributes.
A is correct because DNS name is an explicit Include and Exclude value, with wildcards such as star dot ops dot yourcompany dot com. B is correct because IP address is an explicit value, with wildcards such as 10 dot 1 dot 1 dot star. D is correct because platform machine type is a first-class filter via machineTypesFilter, with values such as linux-x86_64 and windows-x64. The spec header also says filters can be based on DNS name, IP address, platform, and clientName.
C is wrong because Splunk server role is never a filtering attribute. Roles describe topology, not client selection. The documented match order is clientName, IP address, DNS name, hostname, and instanceId, plus machineTypesFilter, with no role. Selecting only AB omits a valid filter and fails Select all that apply scoring, so any key without D is incomplete.
Memorize Include, Exclude, Machine type mapped to whitelist, blacklist, machineTypesFilter. Remember machineTypesFilter needs a whitelist match first, often whitelist dot 0 equals star, and forwarder management always uses filterType whitelist. If server role appears as an option, eliminate it at once.
C — Check splunkd.log for regex interpretation errors in a monitor stanza. It is the primary server log for input pipeline and configuration warnings, while btool only shows merged settings and metrics.log carries performance counters.
When a monitor stanza contains a malformed or non-matching regular expression, splunkd logs a parsing or input error at startup or reload time identifying the stanza and pattern problem. Splunk documentation describes splunkd.log as the primary server log requested for troubleshooting, and troubleshooting guides direct regex and monitor issues there. Metrics.log lacks error diagnostics and btool only shows winning values, so splunkd.log directly verifies the problem.
Link regex plus monitor to splunkd.log, link counters to metrics.log, and link effective settings to btool.
D — Monitoring Console is the health-check tool for deployment evaluation. It aggregates topology, performance, license, and search health, while btool, DiagGen, and SPL Clinic are not the admin health dashboard.
Splunk documentation for the Distributed Management Console describes it as the overview and health interface for administrators to evaluate deployment state. It consolidates search head, indexer, and forwarder status plus license and performance indicators that other tools do not present together. Vendor prose cites the DMC overview and confirms D. Btool only prints effective settings, diag captures a point-in-time bundle, and SPL Clinic is not the health-check answer here. Monitoring Console is therefore the only option matching the health-check description.
Map health check plus deployment health directly to Monitoring Console.
B — Use site_search_factor origin colon 2, site2 colon 1, total colon 4 for the stated layout. Search factor governs searchable copies, origin and site2 name the constrained sites, and total caps searchable copies cluster-wide.
The requirement asks for two searchable copies at origin, one searchable copy at site2, and four searchable copies overall. Only site_search_factor with origin colon 2, site2 colon 1, total colon 4 expresses searchable placement with those exact numbers. Options using site_replication_factor describe total copies rather than searchable copies and miss the searchable guarantee. Option A names the wrong second site. Vendor consensus selects B because search factor is the searchable-copy control the scenario demands.
Read searchable in the stem and immediately choose site_search_factor with matching site names.
C — Universal Forwarder has its own license model among the listed offerings. It is the lightweight forwarder with distinct licensing.
Splunk licensing distinguishes the Universal Forwarder as a separately licensed lightweight offering that customers deploy widely for collection without consuming Enterprise ingest license in the same way. Heavy forwarders are Enterprise instances performing parsing and routing under Enterprise terms. Forwarder Management is a server role, not a licensed forwarder product. Community and vendor consensus select C as the final answer. Choosing Universal Forwarder therefore matches the only offering with its own license in this set.
Isolate Universal Forwarder as the own-license forwarder among Enterprise-based roles.
D — AggregatorMiningProcessor logs bad event breaking detail in splunkd.log. When line breaking or truncation limits split events incorrectly, this processor component emits the diagnostic message to inspect.
Splunk troubleshooting references and community answers for breaking event because limit has been exceeded point to AggregatorMiningProcessor as the component string to search in splunkd.log. That component handles event boundary detection during aggregation, so misconfigured line breaking surfaces under its name. Filtering by this component isolates the relevant WARN lines, as the vendor reference maps this question to that guide page.
Memorize AggregatorMiningProcessor as the event-breaking signature to grep in splunkd.log.
C — The manager node, formerly called master node, regulates indexer cluster behavior. It coordinates replication, search factor compliance, bucket assignment, and peer recovery from a central control plane.
Only the master slash manager node maintains cluster-wide state and instructs peers where to replicate searchable and non-searchable copies. Documentation for enabling the manager node and indexer cluster architecture assigns regulation of the cluster to this role. Indexers themselves are managed peers that follow manager instructions, while deployer and Monitoring Console serve adjacent but distinct functions. This matches legacy master wording and current manager architecture.
Map manager equals master equals indexer cluster controller, and deployer equals search head cluster app pusher.
D — Run splunk resync shcluster-replicated-config on the affected member. The error signals divergent replicated configs, and member-side resync pulls a clean copy from the captain without cluster-wide disruption.
Splunk community and docs for this exact error direct admins to perform a destructive configuration resync on the affected member using the resync replicated-config command. That operation clears the member-local replicated state and re-pulls captain content, resolving divergence that restarts alone cannot fix. Vendor prose links the error string to this remedy and selects D. Deployer bundle apply targets deployer-managed apps rather than captain-replicated runtime state, and raft cleaning across all members is excessive. Member-side resync is the precise corrective action.
Tie pulling-configurations errors to member-side resync shcluster-replicated-config.
Want the full bank of 161 questions for Splunk Enterprise Certified Architect (SPLK-2002)? See all practice exams.