SPLK-1003 · Question #127
An add-on has configured field aliases for source IP address and destination IP address fields. A specific user prefers not to have those fields present in their user context. Based on the default pro
The correct answer is B. Option B. To disable field aliases in a Splunk user's local context, the user must override the FIELDALIAS stanza with an empty value in their local props.conf. Option B correctly applies this override using the proper stanza syntax.
Question
An add-on has configured field aliases for source IP address and destination IP address fields. A specific user prefers not to have those fields present in their user context. Based on the default props.conf below, which SPLUNK_HOME/etc/users/buttercup/myTA/local/props.conf stanza can be added to the user's local context to disable the field aliases?
Exhibit
Options
- AOption A
- BOption B
- COption C
- DOption D
How the community answered
(39 responses)- A13% (5)
- B79% (31)
- C5% (2)
- D3% (1)
Why each option
To disable field aliases in a Splunk user's local context, the user must override the FIELDALIAS stanza with an empty value in their local props.conf. Option B correctly applies this override using the proper stanza syntax.
This option uses incorrect syntax or a wrong directive name that does not properly override the FIELDALIAS setting inherited from the add-on's default props.conf.
In Splunk, a FIELDALIAS defined in an add-on's default props.conf can be disabled in a user's local context by adding a FIELDALIAS-<alias_name> = stanza set to an empty value in SPLUNK_HOME/etc/users/buttercup/myTA/local/props.conf. This empty-value override follows Splunk's configuration layering rules and effectively removes the alias from the user's context without modifying the shared add-on configuration.
This option likely attempts to remove the alias using an unsupported configuration key or invalid stanza format that Splunk does not recognize for disabling field aliases.
This option uses incorrect formatting or targets the wrong configuration scope, so it fails to nullify the inherited FIELDALIAS for the user's local context.
Concept tested: Overriding field aliases in user-level props.conf
Source: https://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Addaliasestofields
Topics
Community Discussion
No community discussion yet for this question.
