Explanation
Auto-refresh applies to inline searches and saved searches, and post-processing searches are refreshed when their base searches are refreshed. Enabling auto-refresh for a report does not require editing XML, but rather using the Edit Schedule option in the report menu. Each post-processing search using the same base search cannot have a different refresh time, but rather inherits the refresh time of the base search. For more information, see Set up auto-refresh for dashboard panels.

Explanation
The Splunk REST endpoint that is used to create a KV store collection is /storage/collections/config. This endpoint lets you create, update, or delete a KV store collection. The other endpoints are either invalid or used for different purposes. For more information, see Use the Splunk REST API to access the KV Store.

Explanation
The correct answer is A, C, and D because these are the valid values for the sharing property of the Access Control List (ACL) when updating a knowledge object via REST. The sharing property determines the scope of the knowledge object and who can access it. The value of the User is not valid for the sharing property. You can find more information about the ACL and its properties in the Splunk REST API Reference Manual.

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