https://docs.splunk.com/Documentation/Splunk/8.1.0/SearchReference/Chart
https://docs.splunk.com/Documentation/Splunk/8.1.0/SearchReference/Stats

In Splunk, when using the chart command, the useother parameter can be set to false (f) to remove the
'OTHER' category, which is a bucket that Splunk uses to aggregate low-cardinality groups into a single group to simplify visualization. Here's how the options break down:
A: | chart count over CurrentStanding by Action useother=fThis command correctly sets the useother parameter to false, which would prevent the 'OTHER' category from being displayed in the resulting visualization.
B: | chart count over CurrentStanding by Action usenull=f useother=tThis command has useother set to true (t), which means the 'OTHER' category would still be included, so this is not a correct option.
C: | chart count over CurrentStanding by Action limit=10 useother=fSimilar to option A, this command also sets useother to false, additionally imposing a limit to the top 10 results, which is a way to control the granularity of the chart but also to remove the 'OTHER' category.
D: | chart count over CurrentStanding by Action limit-10This command has a syntax error (limit-10 should be limit=10) and does not include the useother=f clause. Therefore, it would not remove the 'OTHER' category, making it incorrect.
The correct answers to rewrite the syntax to remove the 'OTHER' category are options A and C, which explicitly set useother=f.

The correct answer is C. Distributable streaming. This is because the eval command is a type of command that can run on the indexers before the results are sent to the search head. This reduces the amount of data that needs to be transferred and improves the search performance. Distributable streaming commands can operate on each event or result individually, without depending on other events or results. You can learn more about the types of commands and how they affect search performance from the Splunk documentation1.

Reference: https://docs.splunk.com/Documentation/PCI/4.1.0/Install/PrivilegedUserActivity A tag is a descriptive label that you can apply to one or more fields or field values in your events1. You can use tags to simplify your searches by replacing long or complex field names or values with short and simple tags1. To search for events that contain a tag name, you can use the tag keyword followed by an equal sign and the tag name1. You can also use wildcards (*) to match partial tag names1. Therefore, option B is correct because it will return events that contain a tag name that starts with Pri. Options A and D are incorrect because they will only return events that contain an exact tag name match. Option C is incorrect because it will return events that contain a tag name that starts with Priv, not Privileged.

Reference: https://docs.splunk.com/Documentation/Splunk/8.0.3/SearchReference/Transaction One of the statements that would help a user choose between the transaction and stats commands is that there is a 1000 event limitation with the transaction command3.
The transaction command is used to group events that share a common value for one or more fields into transactions3. The transaction command has a default limit of 1000 events per transaction, which means that it will not group more than 1000 events into a single transaction3. This limit can be changed by using the maxevents parameter, but it can affect the performance and memory usage of Splunk3. Therefore, option C is correct, while options A, B and D are incorrect because they are not statements that would help a user choose between the transaction and stats commands.