Highly segmented networks establish restrictive communication boundaries between systems, applications, and security zones.
Although segmentation improves containment and limits unauthorized lateral movement, it introduces additional connectivity requirements for security orchestration platforms.
Option C identifies a significant architectural constraint: SOAR integrations may require API connectivity to endpoint platforms, directory services, firewalls, and other tools located inside restricted network segments.
Firewall rules, routing limitations, proxy requirements, and authentication boundaries can prevent centrally hosted automation services from directly reaching these systems.
Option D identifies the role of an automation broker in addressing this constraint.
Splunk SOAR Automation Broker enables authorized automation actions to execute against applications and assets in private or segregated network environments.
The broker can establish the required connection from an approved network location while preserving restrictions on unsolicited inbound access.
Splunk documentation specifically describes Automation Broker support for segregated network segments.
However, not every segmented architecture strictly requires an automation broker. Direct connectivity through appropriately controlled gateways may be sufficient in some deployments.
Option D is therefore applicable to the broker-based architecture implied by the question, rather than a universal requirement.
Segmentation does not inherently simplify service accessibility, making option A incorrect. It also does not automatically reduce infrastructure failure points.
Official reference / study topic: Splunk SOAR, About Automation Broker and Automation Broker System Requirements.
===============
Submit