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 A and D, because configuring a WMI input and using a Windows universal forwarder are the ways to collect event logs from a remote Windows machine using a standard Splunk installation and no customization. WMI input is a type of input that collects Windows Management Instrumentation (WMI) data from remote Windows machines. Windows universal forwarder is a lightweight version of Splunk that can forward data from Windows machines to Splunk indexers.

The correct answer is B, C, and D, because they are all security best practices for Splunk app development. Storing passwords in clear text in .conf files is not a security best practice, because it exposes the passwords to unauthorized access or leakage. Implementing security in software development lifecycle means applying security principles and practices throughout the app development process, from design to deployment. Manually testing application with the controls listed in the OWASP Security Testing Guide helps to identify and mitigate common security risks and vulnerabilities in web applications. Using a dynamic scanner such as OWASP ZAP to scan web application components for vulnerabilities helps to automate the security testing and find potential issues that might be missed by manual testing.

The correct answer is B, because the tstats command can be used to perform statistical queries on indexed fields in TSIDX files. TSIDX files are files that store the index data for Splunk, such as the events, timestamps, and fields. Indexed fields are fields that are extracted and stored in the TSIDX files at index time, which makes them faster to search than non-indexed fields. The tstats command is a search command that performs statistical calculations on indexed fields, such as count, sum, avg, and so on. The tstats command is faster than the stats command, which performs statistical calculations on any fields, because it does not need to retrieve the events from the index, but only the fields from the TSIDX files. The other options are not search commands that can be used to perform statistical queries on indexed fields in TSIDX files. The stats command performs statistical calculations on any fields, not just indexed fields. The tscollect command collects the results of a transforming search and writes them to a TSIDX file. The transaction command groups events into transactions based on common values.

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

The log file that contains logs that are most relevant to Splunk Web is web_service.log. This log file records information about the web server that runs Splunk Web, such as requests, responses, errors, and performance. The other log files contain logs that are related to other aspects of Splunk, such as audit.log for security events, metrics.log for performance metrics, and splunkd.log for Splunk daemon activity. For more information, see [About Splunk log files].