SPLK-3002 practice question 1 of 15

What are valid considerations when designing an ITSI Service? (Choose all that apply.)

Full set: 90 questions
Answer options
A: Service access control requirements for ITSI Team Access should be considered, and appropriate teams provisioned prior to creating the ITSI Service. Correct answer
B: Entities, entity meta-data, and entity rules should be planned carefully to support the service design and configuration. Correct answer
C: Services, entities, and saved searches are stored in the ITSI app, while events created by KPI execution are stored in the itsi_summary index. Correct answer
D: Backfill of a KPI should always be selected so historical data points can be used immediately and alerts based on that data can occur.
Correct Answer:
A. Service access control requirements for ITSI Team Access should be considered, and appropriate teams provisioned prior to creating the ITSI Service.; B. Entities, entity meta-data, and entity rules should be planned carefully to support the service design and configuration.; C. Services, entities, and saved searches are stored in the ITSI app, while events created by KPI execution are stored in the itsi_summary index.
Explanation

Before creating a service, plan team-based access so the correct permissions are applied. Entity definitions and rules must also be designed in advance because services reference entities for KPI scoping. Configuration objects (services, entities, saved searches) reside in the ITSI app’s KV-store; KPI executions write their results to the itsisummary index. These are core design considerations in Splunk documentation.

Why Incorrect

D. Blanket backfill is discouraged; unnecessary backfill strains resources and can trigger retroactive alerts. Use it only when historical KPI data is essential.

References

1. Splunk Docs, “Create and manage teams in ITSI”, para 2: plan team access before service creation.

2. Splunk Docs, “Plan entities and entity rules”, first section.

3. Splunk Docs, “Overview of the itsisummary index”, para 1: storage locations for configuration vs. KPI data.

Scroll to Top