Free Splunk SPLK-2001 Practice Exam with Questions & Answers | Set: 2

The correct answer is A because the /servicesNS/-/data/saved/searches/mySearch endpoint path can be used by someone with a power user role to access information about mySearch, a saved search owned by someone with a user role. The /servicesNS/-/data/saved/searches endpoint returns information about saved searches in a specific namespace. The - symbol in the URI means that the user and app context are inherited from the current session. Therefore, a power user can access the saved search information by using the - symbol, assuming the permissions are set appropriately. The other options are incorrect because they either use invalid endpoints or do not specify the user and app context correctly. You can find more information about the /servicesNS endpoint and the namespace in the Splunk REST API Reference Manual.

The correct answer is A, B, and D because these are the statements that are true regarding HEC (HTTP Event Collector) tokens. HEC tokens are unique identifiers that are used to authenticate and authorize the data sent to HEC, which is a service that allows you to send data to Splunk via HTTP or HTTPS. Option A is correct because multiple tokens can be created for use with different sourcetypes and indexes, which are the attributes that define the data type and the location of the data in Splunk. Option B is correct because the edit token http admin role capability is required to create a token, which is a permission that allows the user to manage the HEC tokens. Option D is correct because tokens can be edited using the data/inputs/http/{tokenName} endpoint, which is a REST endpoint that allows you to update the properties of a specific HEC token. Option C is incorrect because to create a token, you need to send a POST request to the data/inputs/http endpoint, not the services/collector endpoint. The services/collector endpoint is used to send data to HEC, not to create tokens. You can find more information about HEC tokens and their endpoints in the Splunk Developer Guide.

The correct answer is A, B, and D, because they are all items that can be configured in inputs.conf. Inputs.conf is a configuration file that defines how Splunk ingests data from various sources, such as files, directories, network ports, scripts, or modular inputs. A modular input written in Python is a type of input that allows Splunk to ingest data from a custom source using a Python script. A file input monitoring a JSON file is a type of input that allows Splunk to monitor a file or directory for new or updated data in JSON format. An HTTP Event Collector as receiver of data from an app is a type of input that allows Splunk to receive data from an app via HTTP or HTTPS requests. A custom search command written in Python is not an item that can be configured in inputs.conf, but in commands.conf.

The correct answer is C, because the XML reference for the file myJS.js located in myOtherApp is . The script attribute specifies the path to the JavaScript file that contains the custom logic for the dashboard. The path must start with the app name, followed by a colon, and then the relative path to the file within the appserver/static folder of the app. The other options are incorrect because they either omit the app name, the colon, or the javascript subfolder.

The correct answer is A because the namespace is a type of token filter. The namespace is a parameter that can be used to filter the tokens returned by the REST API. The namespace consists of the user and the app context, which determine the scope and visibility of the knowledge objects in Splunk. Option B is incorrect because the namespace can include a wildcard (*) for the app attribute, which means it will return tokens from all apps. Option C is incorrect because the namespace does not filter the knowledge objects returned by the REST API, but rather the tokens that reference them. Option D is incorrect because the namespace does filter the tokens returned by the REST API, based on the user and app context. You can find more information about the namespace and the token filter in the Splunk REST API Reference Manual.

 The correct answer is B because when calling the serviceNS endpoint, you must specify the user and app context in the URI. The serviceNS endpoint is a REST endpoint that allows you to access the Splunk service for a specific namespace. The namespace is a combination of the user and the app context, which determine the scope and visibility of the knowledge objects in Splunk. The serviceNS endpoint requires you to specify the user and app context in the URI, such as /servicesNS/{user}/{app}. Option A is incorrect because you do not need to authenticate with an admin user, but rather with the user of the required context. Option C is incorrect because you do not need to authenticate with the user of the required context, but rather with any valid user. Option D is incorrect because you do not need to pass the user and app context in the request payload, but rather in the URI. You can find more information about the serviceNS endpoint and the namespace in the Splunk REST API Reference Manual.

The correct answer is C, because omitting the value of _key from the REST endpoint would cause all records in a collection to be deleted. The _key is a unique identifier for each record in a KV Store collection. The REST endpoint for deleting a record from a collection is /storage/collections/data//, where is the name of the collection and is the value of _key. If the is omitted, the REST endpoint becomes /storage/collections/data/, which deletes all records in the collection. The other options are incorrect because they are not the consequences of omitting the value of _key from the REST endpoint. Cleaning the KV store, deleting all content would require deleting all collections, not just one. Producing the syntax error “Key value missing” would not happen, because the REST endpoint is valid without the value. Meaning that the _key value must be passed as an argument would not make sense, because the argument is the same as the value in the REST endpoint.

The correct answer is A, B, and D because these are the examples of a Splunk KV store use case. A Splunk KV store is a service that allows you to store and manage custom data in Splunk, using key-value pairs. A Splunk KV store can be used for various purposes, such as storing checkpoint data, tracking workflow, and storing application state. Option A is correct because a Splunk KV store can store checkpoint data for modular inputs, which are custom data inputs that use external scripts or binaries to collect and send data to Splunk. Checkpoint data is used to keep track of the data collection progress and resume from the last point in case of interruption. Option B is correct because a Splunk KV store can track workflow in an incident-review system, which is a system that allows you to review and manage the incidents that occur in your environment. Workflow data is used to store the status, priority, and assignee of each incident. Option D is correct because a Splunk KV store can store application state as a user interacts with an app, which is a custom interface that allows you to access and analyze the data in Splunk. Application state data is used to store the user preferences, settings, and selections for the app. Option C is incorrect because a Splunk KV store cannot index metrics data from remote HTTP sources, which are sources that send numerical data to Splunk via HTTP or HTTPS. Metrics data is not stored in the Splunk KV store, but rather in the metrics index, which is a special type of index that optimizes the storage and retrieval of metrics data. You can find more information about the Splunk KV store and its use cases in the Splunk Developer Guide.

The correct answer is D, because defining an alternative search or target view to use is a customization option for the Open in Search panel link button. The Open in Search panel link button is a feature that allows the user to open the search results of a panel in a new search page. The alternative search or target view option allows the user to specify a different search string or a different view name to use when opening the search page4. The other options are not customization options for the Open in Search panel link button, but for the panel itself. Displaying the refresh time, showing the Export Results button, and showing link buttons at the bottom of a panel are all attributes that can be configured for a panel.

 The correct answer is B and D, because they are the ways to optimize the searches in the dashboard. A dashboard is a user interface that displays data from one or more searches in various panels, such as charts, tables, or maps. Optimizing the searches in the dashboard helps to improve the dashboard performance, reduce the load on the Splunk server, and enhance the user experience. Restricting the time range of the search as much as possible and converting the common SPL into a Global Search and converting the other searches to post-processing searches are both methods to optimize the searches in the dashboard by limiting the amount of data to be searched or processed. Converting searches to include NOT expressions and replacing | stats command with | transaction command wherever possible are not methods to optimize the searches in the dashboard, but rather ways to change the search logic or functionality, which might not produce the desired results.