Final answer:
1, 3, 5, 8, and 15 pertain to HEC in Splunk Cloud.
Step-by-step explanation:
HEC stands for HTTP Event Collector in Splunk Cloud. Looking at the given options:
- 1) 1 Index must exist prior to HEC setup: True. At least one index must be created before setting up HEC.
- 2) 2 Index cannot exist prior to HEC setup: False. It is not mentioned that multiple indexes cannot exist prior to HEC setup.
- 3) 3 Progress can be monitored at any time: True. The progress of HEC can be monitored at any time.
- 4) 4 Only after token creation can progress be monitored: False. Progress can be monitored even before token creation.
- 5) 5 All data is encrypted in transit: True. All data sent via HEC in Splunk Cloud is encrypted in transit.
- 6) 6 Data is not encrypted in transit: False. The data is encrypted in transit.
- 7) 7 Customers cannot change the HEC network port: False. Customers can change the HEC network port.
- 8) 8 Customers can change the HEC network port: True. Customers have the flexibility to change the network port.
- 9) 9 Customers can enable HEC for Kinesis Firehose themselves: False. Enabling HEC for Kinesis Firehose requires a support ticket.
- 10) 10 Enabling HEC for Kinesis Firehose requires a support ticket: True. A support ticket is required to enable HEC for Kinesis Firehose.
- 11) 11 Indexer acknowledgement is available only for Amazon Kinesis Firehose: False. Indexer acknowledgement is not limited to Amazon Kinesis Firehose.
- 12) 12 Indexer acknowledgement is freely available: False. Indexer acknowledgement is not freely available.
- 13) 13 Default maximum content length is unlimited: False. The default maximum content length is not unlimited.
- 14) 14 Default maximum content length is 1MB: False. The default maximum content length is not 1MB.
- 15) 15 Default maximum content length is 500KB: True. The default maximum content length is 500KB.
Based on the given options, 1, 3, 5, 8, and 15 pertain to HEC in Splunk Cloud.