Discount Offer
Go Back on SPLK-2001 Exam
Available in 1, 3, 6 and 12 Months Free Updates Plans
PDF: $15 $60

Test Engine: $20 $80

PDF + Engine: $25 $99



Pass exam with Dumps4free or we will provide you with three additional months of access for FREE.

SPLK-2001 Practice Test


Page 1 out of 14 Pages

Which of the following are types of event handlers? (Select all that apply.)


A. Search


B. Set token


C. Form input


D. Visualization





B.
  Set token

C.
  Form input

Explanation: The types of event handlers are set token and form input. Set token event handlers let you set or unset tokens based on user interactions, such as clicking on a chart or selecting a value from a dropdown. Form input event handlers let you create interactive forms that use tokens to pass values between inputs and searches. The other options are not event handlers, but rather components of a dashboard.

Suppose the following query in a Simple XML dashboard returns a table including hyperlinks:

<search>
<query>index news sourcetype web_proxy | table sourcetype title link
</query>
</search>
Which of the following is a valid dynamic drilldown element to allow a user of the dashboard to visit the hyperlinks contained in the link field?


A. <option name “link.openSearch.viewTarget">$row.link$</option>


B.

<drilldown>
<link target="“" blank"="">$$row.link$$
</drilldown>


C.

<drilldown>
<link target="_blank">$row.link|n$</link>
</drilldown>


D.

<drilldown>
<link target “_blank">http://localhost:8000/debug/refresh</link>
</drilldown>





C.
  
<drilldown>
<link target="_blank">$row.link|n$</link>
</drilldown>


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

In a DELETE request, what would omitting the value of _key from the REST endpoint do?


A. Clean the KV store, deleting all content.


B. Produce the syntax error “Key value missing”.


C. Cause all records in a collection to be deleted.


D. Mean that the _key value must be passed as an argument.





C.
  Cause all records in a collection to be deleted.

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

When using the Splunk Web Framework to create a global search, which is the correct post-process syntax for the base search shown below?
var searchmain = new SearchManager{{ id: “base-search”,
search: “index= internal | head 10 | fields “*”, preview: true,
cache: true
}};


A. var mypostproc1 = new PostProcessManager {{ id: “post1”,
managerid: “base-search”,
search: “| stats count by sourcetype”
}};


B. var mypostproc1 = new PostProcessManager{{ id: “post1”,
managerid: “base”,
search: “| stats count by sourcetype”
}};


C. var mypostproc1 = new PostProcess{{ id: “post1”,
managerid: “base-search”,
search: “| search stats count by sourcetype”
}};


D. You cannot create global searches in the Splunk Web Framework.





A.
  var mypostproc1 = new PostProcessManager {{ id: “post1”,
managerid: “base-search”,
search: “| stats count by sourcetype”
}};

Explanation: The correct answer is A, because the correct post-process syntax for the base search shown below is var mypostproc1 = new PostProcessManager {{ id: “post1”, managerid: “base-search”, search: “| stats count by sourcetype” }}. The PostProcessManager is a JavaScript object that creates a post-process search that runs on the results of a base search. The PostProcessManager requires three parameters: id, managerid, and search. The id is a unique identifier for the post-process search. The managerid is the id of the base search that the post-process search depends on. The search is the post-process search string that runs on the base search results. The other options are incorrect because they either use the wrong managerid, the wrong object name, or the wrong search string.

How can hiding or showing a panel by clicking on a chart or a table on the same form be performed?


A. By using vent drilldown.


B. By using workflow action.


C. By using contextual drilldown.


D. By using visualization drilldown.





D.
  By using visualization drilldown.

Explanation: By using visualization drilldown, you can hide or show a panel by clicking on a chart or a table on the same form. Visualization drilldown lets you define a drilldown action that affects a different panel on the same dashboard. You can use the set or unset tokens to control the visibility of the target panel.


Page 1 out of 14 Pages