SPLK-2001 Exam Dumps - Splunk Certified Developer Exam

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 D, because ensuring components have no Common Vulnerabilities and Exposures (CVE) vulnerabilities is a security best practice for developing Splunk apps. CVE is a list of publicly disclosed information security vulnerabilities and exposures1. Splunk recommends using tools such as npm audit, retire.js, and snyk to scan your app components for CVE vulnerabilities2.

The correct answer is B because the best way to identify processor bottlenecks of a search is to use the search job inspector. The search job inspector is a tool that provides detailed information about the performance and resource consumption of a search job, such as CPU time, memory usage, scan count, and event count. The search job inspector can help you identify which parts of your search are causing processor bottlenecks and how to optimize them. Option A is incorrect because using the REST API does not provide as much information as the search job inspector. Option C is incorrect because using the Splunk Monitoring Console does not provide information about individual search jobs, but rather about the overall health and performance of your Splunk deployment. Option D is incorrect because searching the Splunk logs using index=“internal” does not provide information about processor bottlenecks, but rather about errors and warnings that occurred during the search execution. You can find more information about the search job inspector in the Splunk Developer Guide.

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