SPLK-3002 無料問題集「Splunk IT Service Intelligence Certified Admin」

（A）A Splunk dashboard.

（B）A custom deep dive.

（C）Any of the above.

（D）Another glass table.

（A）Multi-KPI alerts.

（B）Aggregation policies.

（C）Correlation searches.

（D）notable_event_grouping.conf

（A）Teams allow searches against the itsi_summary index.

（B）Teams restrict notable event alert actions.

（C）Teams allow restrictions to service content in UI views.

（D）Teams restrict searches against the itsi_notable_audit index.

（A）power

（B）itoa_analyst

（C）admin

（D）itoa_admin

（A）SplunkWeb (8089), SplunkD (8088), and HTTP Collector (8000)

（B）SplunkWeb (8000), SplunkD (8089), and HTTP Collector (8088)

（C）SplunkWeb (8405), SplunkD (8519), and HTTP Collector (8628)

（D）SplunkWeb (8088), SplunkD (8089), and HTTP Collector (8000)

（A）Configure -> Policies -> Smart Mode -> Enable, select "fields", click "Save"

（B）Edit the notable event view, enable smart mode, select "fields", and click "Save"

（C）Enable grouping in Notable Event Review, select "Smart Mode", select "fields", and click "Save"

（D）Edit the aggregation policy, enable smart mode, select fields to analyze, click "Save"

（A）If this value is set to 0, the scheduler may skip scheduled execution periods.

（B）If this value is set to 0, the scheduler might skip some execution periods to make sure that the scheduler is executing the searches running over the most recent time range.

（C）If this value is set to 0, the scheduler bases its determination of the next scheduled search execution time on the current time.

（D）If this value is set to 0, the scheduler bases its determination of the next scheduled search on the last search execution time.

（A）Entities should be noted based upon Service KPI requirements such as 'by host' or 'by product line'.

（B）Entity meta-data for info and aliases should be identified and recorded as requirements.

（C）Entities identified should be included in the entity filtering requirements, such as 'by processld' or 'by host'.

（D）Entities must be identified for every Service KPI defined and recorded in requirements.

（A）Multiple entities can share the same alias value, but must have different role values.

（B）An abstract (pseudo/logical) entity can be used to split by for a KPI, although no entity rules or filtering can be used to limit data to a specific service.

（C）To automatically restrict the KPI to only the entities in a particular service, select "Filter to Entities in Service".

（D）Entities must be IT devices, such as routers and switches, and must be identified by either IP value, host name, or mac address.