"The forwarder/indexer relationship can be considered platform agnostic (within the sphere of supported platforms) because they exchange their data handshake (and the data, if you wish) over TCP.

The correct answer is C. MonitorNoHandle.
MonitorNoHandle is a type of input stanza that allows a Splunk forwarder to read files on Windows systems as Windows writes to them. It does this by using a kernel-mode filter driver to capture raw data as it gets written to the file1. This input stanza is useful for files that get locked open for writing, such as the Windows DNS server log file2.
The other options are incorrect because:
A: Tail Reader is not a valid input stanza in Splunk. It is a component of the Tailing Processor, which is responsible for monitoring files and directories for new data3.
B: Upload is a type of input stanza that allows Splunk to index a single file from a local or network file system. It is not suitable for files that are constantly being updated, as it only indexes the file once and does not monitor it for changes4.
D: Monitor is a type of input stanza that allows Splunk to monitor files and directories for new data. However, it may not work for files that Windows prevents Splunk from reading while they are open. In such cases, MonitorNoHandle is a better option2.
A Splunk forwarder is a lightweight agent that can forward data to a Splunk deployment. There are two types of forwarders: universal and heavy. A universal forwarder can only forward data, while a heavy forwarder can also perform parsing, filtering, routing, and aggregation on the data before forwarding it5.
An input stanza is a section in the inputs.conf configuration file that defines the settings for a specific type of input, such as files, directories, network ports, scripts, or Windows event logs. An input stanza starts with a square bracket, followed by the input type and the input path or name. For example, [monitor:///var/log] is an input stanza for monitoring the /var/log directory.
References:
1: Monitor files and directories - Splunk Documentation
2: How to configure props.conf for proper line breaking ... - Splunk Community
3: How Splunk Enterprise monitors files and directories - Splunk Documentation
4: Upload a file - Splunk Documentation
5: Use forwarders to get data into Splunk Enterprise - Splunk Documentation
6: inputs.conf - Splunk Documentation

The next step to enable the communication between the forwarder and the deployment server after installing a new forwarder with a manually created deploymentclient.conf is to restart Splunk on the deployment client.
The deploymentclient.conf file contains the settings for the deployment client, which is a Splunk instance that receives updates from the deployment server. The file must include the targetUri attribute, which specifies the hostname and management port of the deployment server. To apply the changes in the deploymentclient.conf file, Splunk must be restarted on the deployment client. Therefore, option C is the correct answer.
References: Splunk Enterprise Certified Admin | Splunk, [Configure deployment clients - Splunk Documentation]

Reference:https://docs.splunk.com/Documentation/Splunk/8.2.3/Admin/Aboutusersandroles The power role is a default Splunk role that grants users the ability to create saved searches, edit shared objects and alerts, and access advanced search commands. However, the power role does not allow users to create custom roles, which is a privilege reserved for the admin role. Therefore, option B is the correct answer. References: Splunk Enterprise Certified Admin | Splunk, [About configuring role-based user access - Splunk Documentation]

In Splunk Enterprise, when collecting data from remote Windows machines using Windows Management Instrumentation (WMI), the configurations are defined in the wmi.conf file. This file specifies the parameters for connecting to WMI providers and defines the data inputs.
The wmi.conf file is located in the $SPLUNK_HOME\etc\system\local\ directory. It contains stanzas that define global settings and input-specific configurations for WMI data collection. This setup allows Splunk to collect various types of data from remote Windows systems, such as event logs and performance metrics, without requiring a forwarder on the remote machine.
Reference:
Monitor data through Windows Management Instrumentation (WMI) - Splunk Documentation wmi.conf - Splunk Documentation