In which type of Splunk deployment would you find modular and scripted inputs running on a separate instance?

In a typical Splunk deployment architecture, modular and scripted inputs are often handled differently based on the deployment type. In an On-Premise deployment, you can configure inputs to run on any designated instance, including a dedicated instance specifically for data ingestion. This setup allows for greater flexibility in resource utilization and enables you to separate concerns—keeping your search head and indexer responsibilities distinct from data collection tasks.

By running these inputs on a separate instance, you ensure that your data ingestion processes do not interfere with search performance, allowing resources to be allocated appropriately. This separation can enhance the overall performance and reliability of your Splunk environment.

In contrast, while Splunk Cloud and Hybrid deployments can also support modular and scripted inputs, the flexibility to configure them specifically on distinct instances may be more limited due to the managed nature of Splunk Cloud or the structure of Hybrid setups, which may involve some combination of cloud and on-prem resources managed cohesively rather than distinctly. This makes On-Premise the most suitable environment for dedicated configurations of modular and scripted inputs on separate instances.