In ServiceNow Platform Analytics, the Precision setting controls how numeric values are rounded and abbreviated when displayed in Score widgets . When Precision is set to 0 , the platform displays values using compact notation (such as k for thousands or M for millions) with no decimal places .

For a stored value of 7423.3 , Precision 0 causes the value to be rounded to the nearest thousand and displayed as 7k . Platform Analytics does not display the full raw number unless compact notation is disabled or precision is increased. Option B (7000) and option D (7423) represent numeric rounding but not the compact display format used by score widgets. Option C is incorrect because Precision 0 explicitly removes decimals and applies abbreviation.

ServiceNow documentation confirms that score widgets use precision-based compact formatting , making 7k the correct displayed value when Precision is set to 0.

ServiceNow best practice recommends running Performance Analytics data collections using a dedicated service account specifically created for analytics processing. This ensures consistent permissions, predictable access to data, and improved auditability.

Running collections as individual admins can introduce permission inconsistencies if roles change. The maint account is intended for system upgrades and maintenance, not scheduled analytics jobs. A dedicated Performance Analytics service account minimizes operational risk and aligns with ServiceNow security and governance guidelines.

ServiceNow documentation emphasizes the importance of service accounts for background processing, making option C the correct and recommended choice.

A Historical Collection Job is designed to collect past data for a defined historical period and is typically executed one time or on demand . Unlike scheduled collection jobs (daily, weekly, or monthly), historical jobs are not intended to run repeatedly.

ServiceNow documentation specifies that historical collections are initiated manually to backfill data for indicators that were created after records already existed. Running them on a recurring schedule could lead to duplicated or incorrect data. Therefore, the correct configuration is Once or On Demand , making option A the correct answer.

In Responsive Canvas dashboards, when a Time Series widget contains multiple elements, the Show multiple elements as property controls how those elements are visualized. Setting this property to Aggregate combines the values of all returned elements into a single trend line , which is exactly the desired outcome when viewing a combined trend for High and Critical priority incidents.

Applying an elements filter (option D) limits which elements are displayed but does not combine them into one trend. Setting the property to Separate (option C) explicitly shows individual trend lines for each element. Manually adding elements (option B) still results in multiple distinct series unless aggregation is enabled. According to ServiceNow Platform Analytics documentation, aggregation is the correct method for consolidating multiple indicator elements into one unified visualization on a dashboard.

In Performance Analytics scripted indicators, certain system-provided variables are automatically available without being explicitly defined in the Fields list. The variables score_start and score_end represent the start and end timestamps of the reporting period for which the indicator score is being calculated. These variables are essential for time-aware calculations and historical accuracy.

Fields such as sys_created_on and sys_updated_on must be explicitly added to the Fields list if they are used in scripts. collection_job_start and collection_job_end are not available script variables in indicator calculations. ServiceNow documentation clearly identifies score_start and score_end as built-in variables available to Performance Analytics scripts, making options B and F the correct answers.

The Visualization Library is the Platform Analytics feature that enables visualizations to be reused and shared across any dashboard . When a visualization (such as a time series, scorecard, or breakdown visualization) is saved to the Visualization Library, it becomes a reusable analytics component that can be added to multiple dashboards without duplicating configuration. This ensures consistency in metrics, reduces maintenance overhead, and supports centralized governance of analytics content.

Dashboard Sharing, by contrast, controls who can view or edit a dashboard , not how individual visualizations are reused across dashboards. Roles such as pa_kpi_signals_admin or report_admin provide administrative capabilities but do not enable cross-dashboard visualization reuse. According to ServiceNow Platform Analytics documentation, the Visualization Library is specifically designed to store, manage, and distribute analytics visualizations so they can be embedded in dashboards throughout the platform. This feature is essential in enterprise analytics implementations where the same KPIs and indicators must appear consistently across multiple dashboards and user audiences.

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.

A scripted Breakdown Mapping is required when there is no direct field relationship between the Indicator source data and the Breakdown source table. In such cases, standard field mapping cannot resolve how indicator records should be categorized, so a script is needed to programmatically determine the correct breakdown value.

Mapping to a Sys ID field (option B) is supported through standard mappings. Database views (option C) can still be mapped if fields are accessible. Dot-walked fields (option D) are commonly supported without scripting. According to ServiceNow Platform Analytics documentation, scripted mappings are specifically intended for complex or indirect relationships , making option A the correct answer.