CIS-PA Dumps with Practice Exam Questions Answers

In Responsive Canvas dashboards, when a Time Series widget contains multiple elements, theShow multiple elements asproperty controls how those elements are visualized. Setting this property toAggregatecombines the values of all returned elements into asingle 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 toSeparate(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.

A single Breakdown can be reused across multiple indicators—even when those indicators are based on different facts tables—by creating aseparate Breakdown Mapping for each indicator facts table.

The Breakdown defineswhatis being analyzed, while the Breakdown Mapping defineshowthe indicator facts relate to the breakdown source. Because different facts tables may store data differently, each requires its own mapping configuration. A scripted mapping is only required when no direct relationship exists, not simply because facts tables differ. ServiceNow documentation clearly states that reuse across facts tables is achieved through multiple mappings, making option D the correct answer.

When creating a breakdown based on theage of a task, the correctFacts tablefor the Breakdown Source isBucket [pa_buckets]. In Platform Analytics, age-based breakdowns (such as 0–5 days, 6–10 days, etc.) are not derived directly from the Task table. Instead, they usebucketed data, which is generated bybucket groupsduring data collection.

Thepa_bucketstable stores the calculated bucket values for records at collection time, making it the authoritative facts table for age, duration, and numeric range breakdowns. Bucket Groups define how values are grouped, while the Bucket table stores the actual bucket assignments used in analytics. The Task table itself cannot be used as the facts table for age breakdowns because Platform Analytics requires pre-aggregated, time-aware bucket data to ensure historical accuracy. The Choice table is only used for choice list values and is unrelated to numeric or age-based breakdowns. ServiceNow documentation clearly states that bucket-based breakdowns must reference thepa_bucketstable to function correctly and produce accurate time series analytics.

Performance Analytics Spotlightis a feature that provides aranked list of recordsbased onmultiple weighted conditions, helping users focus on the most critical records that require attention. Spotlight differs from traditional reports and time-series analytics because it evaluates records dynamically using scoring logic rather than historical aggregation.

Option A describes dashboard visualizations such as time series or scorecards. Option B refers to record views, not analytics. Option D describes Performance Analytics indicators, which track trends over time. ServiceNow documentation clearly defines Spotlight as a prioritization tool that ranks records using configurable rules and weights, making option C the correct and complete description.

AHistorical Collection Jobis designed to collect past data for a defined historical period and is typically executedone timeoron 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 isOnce or On Demand, making option A the correct answer.