Go Back on SPLK-3002 Exam
Available in 1, 3, 6 and 12 Months Free Updates Plans
PDF: $15 $60

Test Engine: $20 $80

PDF + Engine: $25 $99

SPLK-3002 Practice Test


Page 1 out of 6 Pages

Which of the following are characteristics of ITSI service dependencies? (select all that apply)


A. If a primary service has a dependent service KPI and the KPI's importance level is changed, the dependency is broken.


B. It is best practice to use the dependent service's built-in 'ServiceHealthScore' KPI to reflect impact to the primary service.


C. Setting the dependent service KPI importance level will be treated as any other KPI in the primary service's health score.


D. Impactful dependent services should only be configured to one primary service to avoid false negatives in Multi KPI Alerts.





B.
  It is best practice to use the dependent service's built-in 'ServiceHealthScore' KPI to reflect impact to the primary service.


C.
  Setting the dependent service KPI importance level will be treated as any other KPI in the primary service's health score.


Explanation:

In the context of Splunk IT Service Intelligence (ITSI), service dependencies allow for the modeling of relationships between services, where the health of one service (dependent) can affect the health of another (primary).

B.It is best practice to use the dependent service's built-in 'ServiceHealthScore' KPI to reflect impact to the primary service:Utilizing the 'ServiceHealthScore' KPI of a dependent service as part of the primary service's health calculation is a recommended practice. This approach ensures that changes in the health of the dependent service directly influence the primary service's overall health score, providing a more holistic view of service health within the IT environment.

C.Setting the dependent service KPI importance level will be treated as any other KPI in the primary service's health score:When a dependent service's KPI is incorporated into a primary service, the importance level assigned to this KPI is factored into the primary service's overall health score calculation just like any other KPI. This means that the impact of the dependent service on the primary service can be weighted according to the business significance of the relationship between the services.

The other options are not accurate representations of ITSI service dependencies. Changes in KPI importance levels do not break dependencies, and there is no restriction on configuring impactful dependent services to only one primary service, as dependencies can be complex and multi-layered across various services.

Which of the following is a recommended best practice for service and glass table design?


A. Plan and implement services first, then build detailed glass tables.


B. Always use the standard icons for glass table widgets to improve portability.


C. Start with base searches, then services, and then glass tables.


D. Design glass tables first to discover which KPIs are important.





A.
  Plan and implement services first, then build detailed glass tables.


Explanation:

Reference:

[Reference: https://docs.splunk.com/Documentation/ITSI/4.10.2/SI/GTOverview, A is the correct answer because it is recommended to plan and implement services first, then build detailed glass tables that reflect the service hierarchy and dependencies. This way, you can ensure that your glass tables provide accurate and meaningful service-level insights. Building glass tables first might lead to unnecessary or irrelevant KPIs that do not align with your service goals. References: Splunk IT Service Intelligence Service Design Best Practices]

Which of the following are deployment recommendations for ITSI? (Choose all that apply.)


A. Deployments often require an increase of hardware resources above base Splunk requirements.

B. Deployments require a dedicated ITSI search head.


C. Deployments may increase the number of required indexers based on the number of KPI searches.


D. Deployments should use fastest possible disk arrays for indexers.





A.
  Deployments often require an increase of hardware resources above base Splunk requirements.
B.
  Deployments require a dedicated ITSI search head.


C.
  Deployments may increase the number of required indexers based on the number of KPI searches.


Explanation:

You might need to increase the hardware specifications of your own Enterprise Security deployment above the minimum hardware requirements depending on your environment. Install Splunk Enterprise Security on a dedicated search head or search head cluster. The Splunk platform uses indexers to scale horizontally. The number of indexers required in an Enterprise Security deployment varies based on the data volume, data type, retention requirements, search type, and search concurrency.

Reference:

[Reference: https://docs.splunk.com/Documentation/ES/latest/Install/DeploymentPlanning, A, B, and C are correct answers because ITSI deployments often require more hardware resources than base Splunk requirements due to the high volume of data ingestion and processing. ITSI deployments also require a dedicated search head that runs the ITSI app and handles all ITSI-related searches and dashboards. ITSI deployments may also increase the number of required indexers based on the number and frequency of KPI searches, which can generate a large amount of summary data. References: ITSI deployment overview, ITSI deployment planning]

Which capabilities are enabled through “teams”?


A. Teams allow searches against the itsi_summary index.


B. Teams restrict notable event alert actions.


C. Teams restrict searches against the itsi_notable_audit index.


D. Teams allow restrictions to service content in UI views.





D.
  Teams allow restrictions to service content in UI views.


Explanation:

D is the correct answer because teams allow you to restrict access to service content in UI views such as service analyzers, glass tables, deep dives, and episode review. Teams alsocontrol access to services and KPIs for editing and viewing purposes. Teams do not affect the ability to search against the itsi_summary index, restrict notable event alert actions, or restrict searches against the itsi_notable_audit index. References: Overview of teams in ITSI

What can a KPI widget on a glass table drill down into?


A. Another glass table.


B. A Splunk dashboard.


C. A custom deep dive.


D. Any of the above.





D.
  Any of the above.


Explanation:

In Splunk IT Service Intelligence (ITSI), a KPI widget on a glass table can be configured to drill down into a variety of destinations based on the needs of the user and the design of the glass table. This flexibility allows users to dive deeper into the data or analysis represented by the KPI widget, providing context and additional insights. The destinations for drill-downs from a KPI widget can include:

A. Another glass table, offering a different perspective or more detailed view related to the KPI.

B. A Splunk dashboard that provides broader analysis or incorporates data frommultiple sources.

C. A custom deep dive for in-depth, time-series analysis of the KPI and related metrics.

This versatility makes KPI widgets powerful tools for navigating through the wealth of operational data and insights available in ITSI, facilitating effective monitoring and decision-making.


Page 1 out of 6 Pages