Which Indicator should be excluded from a Historic Data Collection because its scores cannot be accurately collected?
Answer : C
Historic Data Collection is designed to accurately reconstruct past indicator scores based on historical records. Indicators that rely on calculated age values, such as summed age of open problems, cannot be accurately reconstructed because age is a time-relative value that depends on the exact moment of calculation.
Count-based indicators (options A, B, and D) can be recalculated historically by evaluating record states at specific points in time. However, summing age values requires knowing the precise age of each record at each historical interval, which is not reliably reproducible. ServiceNow documentation explicitly warns against using historic data collection for age-based and duration-sum indicators, making option C the correct exclusion.
Question 2
How many queries are performed against the database when a Daily Data Collection job is executed?
Answer : B
During a Daily Data Collection job, Platform Analytics executes one database query per Indicator Source, not per indicator. Multiple indicators can reference the same indicator source, allowing the platform to reuse the result set and calculate multiple scores from a single query.
This design is a key performance optimization in Platform Analytics. Executing queries per indicator would significantly increase database load, especially in large implementations. ServiceNow documentation explicitly states that indicator sources are the unit of data retrieval during collection, making option B the correct and documented answer.
Question 3
What is the default aggregation for the Metric tile in a Data Visualization?
Answer : A
In Platform Analytics data visualizations, the Metric tile is designed to display a single summarized value. By default, the aggregation used for a Metric tile is COUNT. This means the tile displays the total number of records or scores returned by the data source unless the aggregation is explicitly changed by the user.
COUNT is the most commonly used aggregation because Metric tiles are often used to show key headline numbers such as total incidents, open requests, or completed tasks. Other aggregations like AVERAGE, MIN, or SUM are available options, but they must be manually selected during configuration. ServiceNow documentation confirms that COUNT is the default aggregation applied to Metric visualizations, making option A the correct answer.
Question 4
Which Breakdown is most likely to use a Bucket Group as its Breakdown Source?
Answer : A
A Bucket Group is used in Platform Analytics to categorize numeric or time-based values into ranges. The Hour of day breakdown is a classic example of this usage, as it groups records into defined hourly ranges (for example, 00--01, 01--02, and so on).
Priority, Business Service, and Assignment Group are categorical fields that use direct field mappings and do not require bucket logic. Bucket Groups are specifically intended for non-categorical data such as time, age, duration, or numeric ranges. ServiceNow documentation explicitly identifies time-based breakdowns, such as hour of day or age ranges, as appropriate use cases for Bucket Groups. Therefore, option A is the correct answer.
Question 5
Where should you navigate to activate a Performance Analytics Content Pack?
Answer : C
Performance Analytics Content Packs provide prebuilt indicators, breakdowns, dashboards, and jobs for specific applications such as Incident, Problem, or Change Management. To activate these packs, administrators navigate to Performance Analytics > Add Content Pack. This interface lists all available analytics content packs and allows administrators to preview and activate them.
Option A refers to Solution activation, which is unrelated to Performance Analytics content. Option B is used for application plugins, not analytics packs. Option D does not exist as a valid navigation path for Performance Analytics. ServiceNow documentation explicitly identifies Performance Analytics > Add Content Pack as the correct location to install analytics content, making option C the verified answer.
Question 6
What is the primary function of the analytics_filter_admin role in Analytics Center?
Answer : B
The analytics_filter_admin role is responsible for governing dashboard filters within Analytics Center. Users with this role can create, edit, delete, and manage filters, as well as add filters to the filter library for reuse across dashboards.
This role does not control visualization design, breakdown security, or data validation. Its purpose is to ensure consistent and controlled use of filters across analytics experiences. ServiceNow documentation explicitly associates this role with filter administration, making option B the correct answer.
Question 7
Which scenarios require the use of a scripted Breakdown Mapping?
Answer : A
A scripted Breakdown Mapping is required when the breakdown value cannot be obtained through a direct field mapping or simple reference relationship. Categorizing requests based on the number of times they were updated requires calculating a value dynamically (for example, counting updates from the audit history), which is not stored as a single field on the record. Because this value must be derived programmatically, a scripted mapping is necessary.
Options B and C use existing fields (category, priority) that can be mapped directly without scripting. Option D uses age ranges, which are handled through Bucket Groups and the pa_buckets table, not scripted mappings. ServiceNow documentation clearly states that scripted mappings are intended for calculated, derived, or indirect values, making option A the correct answer.
All Official Question Types