Final answer:
Role Inheritance in Splunk means that a new custom role inherits the index settings and all capabilities of its parent role. However, inherited capabilities can be adjusted through the UI or command line. Inheritance is not limited to default Splunk Cloud roles, as custom roles can also utilize this feature.
Step-by-step explanation:
The implications of Role Inheritance when creating a custom role in Splunk are as follows:The new role inherits the index settings of the parent role. This includes access to the same data sets that the original role could view. The new role has all the capabilities of the inherited role, meaning it contains all the permissions and access rights of the parent role. If you wish to turn off inherited capabilities, it is possible to do so through the user interface (UI) or the command line, not limited to command line access only. Inheritance in Splunk roles is not restricted to just those built into Splunk Cloud by default; custom roles can inherit from other roles as well. When creating a custom role, it's important to review and adjust the inherited capabilities and index settings to ensure they align with the intended use of the new role.
Role inheritance in creating a custom role has several implications:If you wish to turn off capabilities inherited from the original role, you must do so by command line access only.The new role inherits the index settings. This means that any changes made to the index settings of the original role will be inherited by the new role.The new role has all the capabilities of the inherited role. This means that the new role can perform all the same actions and tasks as the original role.Inheritance is only available for roles built into Splunk Cloud by default. This means that you cannot inherit roles that are not built into Splunk Cloud.