SPLK-2002(205Q) · Question #11
Which of the following are client filters available in serverclass.conf? (Select all that apply.)
A (DNS name), B (IP address), and D (Platform/machine type) are all correct. Splunk's serverclass.conf lets you target deployment clients using three filter mechanisms: hostname/DNS patterns (via whitelist/blacklist entries matching client names), IP address ranges or exact…
Question
Which of the following are client filters available in serverclass.conf? (Select all that apply.)
Options
- ADNS name.
- BIP address.
- CSplunk server role.
- DPlatform (machine type).
Explanation
A (DNS name), B (IP address), and D (Platform/machine type) are all correct. Splunk's serverclass.conf lets you target deployment clients using three filter mechanisms: hostname/DNS patterns (via whitelist/blacklist entries matching client names), IP address ranges or exact IPs, and machine type filters (via machineTypesFilter, e.g., linux-x86_64, windows-x86_64). These filters control which forwarders receive a given server class's apps.
C is wrong because Splunk server role (indexer, search head, etc.) is not a supported filter in serverclass.conf. Roles are a concept for clustering and distributed search, not for deployment server targeting. You cannot say "send this app only to indexers" natively through serverclass.conf filters.
Memory tip: Think "DIP" - DNS, IP, Platform - the three ways the deployment server knows who a client is. Role is a logical concept the deployment server doesn't track.
Topics
Community Discussion
No community discussion yet for this question.