Splunk SPLK-2001 Splunk Certified Developer Exam Exam Practice Test

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 HTTP Event Collector (HEC) endpoint that should be used to collect data in the given format is services/collector/raw. This endpoint accepts raw data that is not formatted as JSON, such as plain text or XML. The data format is specified by the sourcetype parameter in the request. The other endpoints are either used for different purposes or do not exist. For more information, see Use the raw HEC endpoint.

A Splunk custom visualization is a visualization that uses the Splunk Custom Visualization API. This API lets you create your own visualizations using JavaScript, HTML, and CSS. You can also use third-party libraries or frameworks to create custom visualizations. The other options are not custom visualizations, but rather variations of the built-in visualizations in Splunk. For more information, see [Custom visualizations overview].

 The correct answer is A, B, and C, because they are all ways to monitor app performance. App performance refers to how well an app performs its intended functions, such as data ingestion, search, visualization, and alerting. Monitoring app performance helps to identify and troubleshoot issues, optimize performance, and improve user experience. Using Splunk logs, using the search job inspector, and using the Monitoring Console are all methods to monitor app performance by collecting and analyzing various metrics and data related to the app. Using the storage/collections/config REST endpoint is not a way to monitor app performance, but a way to configure the KV Store collections for an app.

The correct answer is C, because /storage/collections/data/sales/smith is the REST endpoint to delete the record with a _key value of smith from the sales collection. The /storage/collections/data endpoint is used to access the KV Store data collections. The sales collection is the name of the collection, and smith is the _key value of the record to be deleted.

When added to an app’s default.meta file, export = system makes one of its views available to other apps. This means that the view is visible and searchable by all users. The other options are invalid because export = app means that the view is visible and searchable only within the app, export = none means that the view is not visible or searchable by any user, and export = view is not a valid value for the export attribute. For more information, see About configuration file structure and inheritance.

It uses the $row.field|n$ syntax to reference the value of the link field in each row of the table. This syntax is used to create dynamic links in Simple XML dashboards. The other options are incorrect because they either use invalid syntax or do not reference the link field correctly. You can find more information about dynamic drill-downs and link syntax in the Splunk Developer Guide.

The Simple XML elements that configure panel link buttons are <title>Open In Search</title> and true. The title element specifies the text that appears on the link button, and the option element enables the link button to be visible. The other elements are either irrelevant or used for different options. For more information, see Drilldown to a URL.

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 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.

A KV store collection can be associated with a namespace for users in the admin, power, and splunk-system-user roles. These roles have the capability to create and manage KV store collections. The nobody user cannot access any KV store collection, and the users in the admin and power roles alone cannot access the collections in the splunk-system-user namespace. For more information, see KV Store namespaces.

The correct answer is A, because data can be added to a KV Store collection only in JSON format. KV Store is a feature that allows Splunk to store and manage data in collections of key-value pairs. A KV Store collection is a logical grouping of key-value pairs that can be accessed and manipulated by Splunk apps. Data can be added to a KV Store collection either by using the Splunk Web interface, the Splunk REST API, or the Splunk SDKs. In all cases, the data must be formatted as JSON objects, which are collections of name-value pairs enclosed in curly braces1. The other formats, such as XML, CSV, and TXT, are not supported by KV Store.

 The correct answer is B and D, because they are the files within an app that contain permissions information. Permissions information refers to the access control settings for the app, such as who can read and write to the app, and whether the app is visible to all users or only to the app owner. The files that contain permissions information are the metadata/local.meta and metadata/default.meta files, which are located in the metadata folder of the app. The local/metadata.conf and default/metadata.conf files do not exist, and are not valid configuration files for an app.

The correct answer is B, C, and D, because they are all ways to reduce the results size in the results when the search/jobs REST endpoint is called to execute a search. The search/jobs REST endpoint is used to create, manage, and control search jobs in Splunk. The results size in the results refers to the amount of data returned by the search job, which can affect the performance and efficiency of the search. Removing unneeded fields, truncating the data using selective functions, and summarizing the data using analytic commands are all methods to reduce the results size by filtering, limiting, or aggregating the data. Using a generating search is not a way to reduce the results size, but a way to create a search job that does not use the index, but instead generates its own data3.

 The correct answer is A and B because these are the ways to get a list of search jobs. Option A is correct because you can access the Activity > Jobs page in Splunk Web to see the list of search jobs that you have run or that are shared with you. Option B is correct because you can use Splunk REST to query the /services/search/jobs endpoint to get a list of search jobs. Option C is incorrect because the /services/saved/searches endpoint returns a list of saved searches, not search jobs. Option D is incorrect because the /services/search/sid/results endpoint returns the results of a specific search job, not a list of search jobs. You can find more information about search jobs and their endpoints in the Splunk REST API Reference Manual.

The valid request arguments for the REST search endpoints are latest_time=now and earliest_time=-5h@h. These arguments specify the time range for the search, using relative or absolute time modifiers. The other arguments are invalid because they use rt (real-time) modifiers, which are not supported by the REST search endpoints. For more information, see [Specify time modifiers in your search].

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 requirements for arguments sent to the data/indexes endpoint are to specify the datatype and include the name argument. The datatype argument specifies the type of data that is being indexed, such as event, metric, or http. The name argument specifies the name of the index that is being created or updated. The other arguments are either optional or invalid. For more information, see Create an index.

The correct answer is A, because tokenn​ame∣s ensures that quotation marks surround the value referenced by the token. The |s modifier is used to escape special characters in the token value, such as quotation marks, commas, and colons. This is useful when the token value is used in a search string or a drilldown action1. The other options are incorrect because they either do not escape the special characters or add extra quotation marks.

The correct answer is B and C because these are the statements that describe one-shot searches. A one-shot search is a type of search that runs once and returns all the results at once. Option B is correct because a one-shot search can specify csv as an output format, which returns the results as comma-separated values. Option C is correct because a one-shot search streams all the results upon search completion, which means it does not return any partial results while the search is running. Option A is incorrect because a one-shot search can be executed either synchronously or asynchronously, depending on the method used. Option D is incorrect because a one-shot search cannot use auto_cancel to set a timeout limit, as this parameter is only applicable for normal searches. You can find more information about one-shot searches in the Splunk REST API Reference Manual.

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.