Splunk SPLK-1003 - Splunk Enterprise Certified Admin

"The forwarder/indexer relationship can be considered platform agnostic (within the sphere of supported platforms) because they exchange their data handshake (and the data, if you wish) over TCP.

https://docs.splunk.com/Documentation/Splunk/8.0.3/Data/Monitornetworkports

https://docs.splunk.com/Documentation/Splunk/7.3.1/DistSearch/SHCarchitecture

Scroll down to section titled, How the cluster handles concurrent search quotas, "Overall search quota. This quota determines the maximum number of historical searches (combined scheduled and ad hoc) that the cluster can run concurrently. This quota is configured with max_Searches_per_cpu and related settings in limits.conf."

In Splunk Enterprise, when you configure the server.conf file with strict pool quota=false, it means that license pools are allowed to share the total available license quota rather than being restricted to their individually allocated quotas. However, this does not prevent pools from issuing warnings if they exceed their allocated limits.

Given the environment with a 1000 GB/day license split into three pools:

Pool X: 500 GB/day license, 100 GB used

Pool Y: 350 GB/day license, 400 GB used

Pool Z: 150 GB/day license, 300 GB used

Let's analyze the usage:

Pool X is allocated 500 GB/day but has only used 100 GB, well within its limit.

Pool Y is allocated 350 GB/day but has used 400 GB, which exceeds its limit by 50 GB.

Pool Z is allocated 150 GB/day but has used 300 GB, which exceeds its limit by 150 GB.

Even with strict pool quota=false, pools Y and Z have exceeded their individual allocated quotas and will issue warnings. Pool X has not exceeded its quota and thus will not issue any warnings. Therefore, the pools that are issued warnings are Y and Z.

https://docs.splunk.com/Documentation/Splunk/8.1.1/Data/Monitornetworkports

The failOpen setting in the [duoMFA] stanza determines how Splunk software handles authentication requests when it cannot connect to the Duo Security service. If failOpen is set to True, as in this example, Splunk software allows users to log in without completing a multifactor challenge. If failOpen is set to False, Splunk software denies all logins when it cannot connect to Duo Security. This setting is independent of the authentication type or the secretKey protection. References = Connect to Duo Security for multifactor authentication

To verify the integrity of a local bucket. The command ./splunk check-integrity -bucketPath [bucket path] [-verbose] is used to verify the integrity of a local bucket by comparing the hashes stored in the l1Hashes and l2Hash files with the actual data in the bucket1. This command can help detect any tampering or corruption of the data.