CAS Performance Analytics - ServiceNow Practice Test 2026
Performance Analytics has its own language: indicators, breakdowns, widgets, thresholds, forecasting, and collection jobs. These 216 questions focus on how the pieces work together in practice. The explanations help when two answers both sound technically possible.
What's included
- 216 questions on indicators, breakdowns, widgets, dashboards, and forecasting
- Source links point back to the official ServiceNow documentation
- Every answer choice gets a reason, not only the winner
- Aligned to the Zurich release and the current 2026 blueprint
- Lifetime access. No 30-day expiry. Updates stay free.
- Written by an author who only ships a cert after passing it first try
- Full refund available through Udemy for 30 days
15 Free Preview Questions
Answer 5 questions free. Enter your email to continue through question 15. The full course has 216 questions on Udemy.
- AData Visualization
- BConfigure Breakdowns and Breakdown Sources
- CConfigure Indicators and Indicator Sources
- DArchitecture and Deployment
Show full explanation
Correct Answer
C) Configure Indicators and Indicator Sources
Source
ServiceNow CAS-PA Mainline Blueprint | Google fallback
Expert Explanation
The CAS-PA Mainline Blueprint published by ServiceNow breaks the exam into several Learning Domains, each with a defined percentage weight. Configure Indicators and Indicator Sources consistently holds the largest share. This makes sense architecturally: indicators are the atomic unit of Performance Analytics. Every dashboard widget, every target, every signal, and every breakdown depends on a properly configured indicator and its underlying indicator source. Without mastering indicator types (automated, formula, manual, derived), candidates cannot effectively work with any downstream PA feature. The blueprint reflects this dependency by assigning the most exam questions to this domain.
Why the Others Are Wrong
A) Data Visualization covers dashboards, widgets, and reporting presentation layers. It is tested but weighted lower because visualization is a consumption layer that sits on top of the indicator foundation.
B) Configure Breakdowns and Breakdown Sources addresses how scores are segmented by dimensions like assignment group, category, or priority. Breakdowns are important but secondary to the indicators they decompose.
D) Architecture and Deployment deals with data collection scheduling, PA table structures, content packs, and system properties. This domain provides the infrastructure context but carries less weight than the hands-on indicator configuration domain.
Memory Tip
Think of it as a pyramid: Indicators form the base (largest area and highest weight), Breakdowns sit in the middle, Visualizations and Architecture occupy the top. The base always carries the most weight.
Real-World Example
When a ServiceNow PA administrator begins a new implementation, the first task is always defining which KPIs (indicators) to track and configuring their indicator sources. Only after indicators produce reliable scores can the team add breakdowns, build dashboards, set targets, and configure signals. The exam blueprint mirrors this real-world implementation order by weighting indicator configuration most heavily.
- AEnable the property "Allow formula component to be NULL".
- BSet the system property "Value when nil" to 0.
- CAdd a conditional JavaScript statement in the formula to return 0 if the value of Number of Resolved Incidents is 0.
- DEnable the property "Render continuous lines".
Show full explanation
Correct Answer
C) Add a conditional JavaScript statement in the formula to return 0 if the value of Number of Resolved Incidents is 0
Source
ServiceNow Docs - Formula Indicators | Google fallback
Expert Explanation
PA formula indicators execute their expressions during each data collection cycle. When a formula divides by a component indicator whose collected value is zero, the PA engine cannot produce a numeric result and records 'No Score' for that period. The correct fix is to embed conditional JavaScript logic directly in the formula field. PA formulas support basic JavaScript constructs including if/else statements and ternary operators. By checking whether the denominator component equals zero before performing the division, you ensure the formula always returns a valid numeric score. This approach is superior to display-layer workarounds because the actual score record in the pa_scores tables contains a real value of 0, which means downstream aggregations, targets, signals, and reporting all function correctly.
Why the Others Are Wrong
A) 'Allow formula component to be NULL' addresses scenarios where a contributing indicator has no score at all (NULL), not where it has a score of zero. A zero-value score and a missing score are different conditions in the PA engine.
B) 'Value when nil' is a display-level property that substitutes a visual value when no score exists. It does not prevent the 'No Score' from being recorded during collection. Reports and widgets might show 0, but the underlying data remains incomplete.
D) 'Render continuous lines' is a widget visualization property that draws connecting lines across missing data points. It has no relationship to formula calculation logic.
Memory Tip
When you see 'No Score' in PA, think 'calculation problem' not 'display problem'. Fix calculations at the formula level with JavaScript conditionals, not at the display level with cosmetic properties.
Real-World Example
A service desk manager tracks first-contact resolution percentage. On weekends, the denominator (total resolved incidents) might be zero because no tickets were resolved. Without the JavaScript guard, the weekend data points show 'No Score', breaking trend analysis and causing gaps in executive dashboards. Adding the conditional check produces a clean 0% for those periods, maintaining a complete time series that accurately reflects the weekend inactivity.
- AThe table remains the sole repository for RaptorDB operations.
- BThe table is converted to an offline data repository.
- CThe scores are migrated automatically to the pa_scores_l1 and pa_scores_l2 tables.
- DData is permanently flushed to optimize database storage.
Show full explanation
Correct Answer
C) The scores are migrated automatically to the pa_scores_l1 and pa_scores_l2 tables
Source
ServiceNow Docs - PA Score Tables Architecture | Google fallback
Expert Explanation
The Washington DC release introduced a significant architectural improvement to PA scoring tables. Historically, all scores (aggregate and breakdown-level) were stored in a single pa_scores table. As instances accumulated years of data across hundreds of indicators with multiple breakdown levels, this table could grow to tens or hundreds of millions of rows, causing severe query performance degradation. The new architecture splits scores into pa_scores_l1 (containing aggregate scores without breakdown elements, used by most dashboard queries) and pa_scores_l2 (containing breakdown-level detail scores). For instances with fewer than 43 million total scores, this migration happens automatically during the upgrade. Larger instances require a planned migration approach coordinated with ServiceNow support due to the volume of data involved.
Why the Others Are Wrong
A) Sole repository for RaptorDB operations mischaracterizes the change. The whole point of the Washington DC update is to move away from the single-table model. RaptorDB column-store indexing is a separate optimization that complements but does not replace the table-split migration.
B) Offline data repository implies the data becomes inaccessible for real-time queries. The migrated data in pa_scores_l1 and pa_scores_l2 remains fully online and is actively queried by dashboards, widgets, and reports.
D) Permanently flushed would mean data loss. ServiceNow never destroys historical PA scores during an upgrade. Data integrity is maintained throughout the migration process.
Memory Tip
Think L1 = Level 1 = top-level aggregates (fast queries), L2 = Level 2 = breakdown detail (granular analysis). The split mirrors how users consume data: most look at the summary first, then drill down.
Real-World Example
A large enterprise with 500 indicators, 10 breakdowns each, and 3 years of daily collection had a pa_scores table exceeding 200 million rows. Dashboard load times exceeded 30 seconds. After the Washington DC migration, L1 queries for aggregate scores hit a much smaller table, reducing dashboard load times to under 3 seconds. L2 queries for breakdown detail only execute when users explicitly drill down, distributing the query load efficiently.
- AAt least 30 days
- BAt least 3 months
- CAt least 6 months
- DAt least 12 months
Show full explanation
Correct Answer
D) At least 12 months
Source
ServiceNow Docs - PA Forecasting | Google fallback
Expert Explanation
PA forecasting uses statistical algorithms (including linear regression, exponential smoothing, and Holt-Winters seasonal models) to project future indicator values based on historical score data. For these algorithms to produce reliable predictions, they need enough data to capture the full range of patterns that affect the metric. ServiceNow recommends at least 12 months because most business metrics exhibit annual seasonality. Incident volumes spike during certain months. Change request volumes follow fiscal year cycles. HR case volumes increase around annual enrollment periods. Without a full year of data, the forecasting engine cannot distinguish between a genuine upward trend and a seasonal spike, leading to inaccurate projections. The 12-month recommendation also provides enough data points for the confidence interval calculations that accompany forecast lines on time series widgets.
Why the Others Are Wrong
A) 30 days provides only about 30 daily data points. This is statistically insufficient for any meaningful time series forecasting. The model cannot identify patterns beyond very short-term fluctuations.
B) 3 months gives roughly 90 daily data points. While better, this period cannot capture quarterly or annual seasonality. A forecast based on summer data would not anticipate winter patterns.
C) 6 months captures half-year patterns but misses the full annual cycle. Important annual events (fiscal year transitions, holiday seasons, annual audits) that significantly impact many KPIs would be absent from the training data.
Memory Tip
Think 12 for 12: 12 months gives you 12 monthly data points at minimum, covering all four seasons and all annual business cycles. The number matches the calendar year itself.
Real-World Example
An IT service desk activated PA forecasting after 3 months of data collection. The forecast predicted a steady decline in incident volume. However, the 3 months happened to be July through September (summer months with lower staffing and activity). When October arrived, incident volumes surged due to new project deployments and fiscal year-end changes. The forecast was completely wrong. After accumulating 12 months of data, the forecast correctly anticipated the Q4 spike and Q3 dip, giving leadership accurate capacity planning projections.
- AThe entire data collection job aborts immediately.
- BThe record is automatically assigned to a newly generated dynamic bucket.
- CThe record is processed but placed into the 'Unassigned' or empty breakdown element category.
- DThe system automatically alters the maximum value of the highest bucket to accommodate the record.
Show full explanation
Correct Answer
C) The record is processed but placed into the 'Unassigned' or empty breakdown element category
Source
ServiceNow Docs - Bucket Groups | Google fallback
Expert Explanation
Bucket Groups in PA convert continuous numeric variables into discrete categories for breakdown analysis. For example, 'Incident Age (Days)' might have buckets: 0-1, 2-3, 4-7, 8-14, 15-30. During data collection, the PA engine evaluates each record's value and assigns it to the matching bucket. When a value falls outside all defined ranges (such as an incident aged 45 days when the highest bucket only goes to 30), the engine does not discard the record or halt processing. Instead, it classifies the record under the unassigned/empty breakdown element. This is the same category used for any record that cannot be mapped to a specific breakdown element. The design philosophy is to never lose data during collection while making it visible to administrators that their bucket configuration may need adjustment. Monitoring the unassigned category size helps PA administrators identify when bucket ranges need expansion.
Why the Others Are Wrong
A) Collection job aborts would be catastrophic for data integrity. A single out-of-range record would prevent thousands of valid records from being collected. PA is designed for resilience, not fragility.
B) Dynamic bucket generation would create unpredictable breakdown structures. Each collection cycle could produce different bucket elements, making time series comparison meaningless. Bucket groups are intentionally static configurations.
D) Automatic maximum value alteration would change the semantic meaning of existing buckets without administrator awareness. Historical comparisons would become invalid if bucket boundaries shifted between collection cycles.
Memory Tip
Think of buckets like mailbox slots: if a package is too big for any slot, it goes to the 'unassigned' holding area. Nothing gets thrown away, and the mailbox slots stay the same size until someone manually adjusts them.
Real-World Example
A PA administrator configured an 'Incident Resolution Time (Hours)' bucket group with ranges: 0-4, 5-8, 9-24, 25-72. A major outage resulted in several incidents taking over 200 hours to resolve. During data collection, these records were placed in the unassigned category. The administrator noticed a growing unassigned count on the breakdown widget, investigated, and added a '73+' bucket to properly categorize long-running incidents going forward.
- ATo clear outdated caching issues on the dashboard.
- BTo populate the new indicators with past data, providing immediate insight into existing trends.
- CTo populate the Performance Analytics tables with data going forward on a daily basis.
- DTo automatically build new unassigned breakdown elements.
Show full explanation
Correct Answer
B) To populate the new indicators with past data providing immediate insight into existing trends
Source
ServiceNow Docs - Historic Data Collection | Google fallback
Expert Explanation
Analytics and Reporting Solutions (content packs) deliver ready-made PA configurations including indicators, indicator sources, breakdowns, and dashboards for specific ServiceNow applications like ITSM, HRSD, or CSM. When you activate a content pack, all these configuration records are created, but the indicators have zero collected scores. Without historical data, the dashboards would show blank widgets with no trend lines, baselines, or comparative analysis. Running Historic Data Collection immediately solves this by retroactively processing existing records (incidents, changes, requests) through the newly created indicator sources, generating scores for past periods. This backfill operation means that within hours of activating a content pack, stakeholders can view 6-12 months of trend data, identify existing patterns, set meaningful targets, and make data-driven decisions. Without this step, organizations would need to wait months before the indicators accumulated enough daily scores to be useful.
Why the Others Are Wrong
A) Clearing caching issues conflates two unrelated concerns. Cache management and data collection are independent processes in the PA architecture. Content pack activation does not create caching problems that need resolution.
C) Populating tables going forward describes the standard daily scheduled collection job, not historic data collection. The daily job runs automatically and does not need manual triggering. The question asks specifically about the historic job and why it should run immediately after activation.
D) Building unassigned breakdown elements is not a goal of historic data collection. Unassigned elements are an incidental classification for records that do not match breakdown element criteria.
Memory Tip
Content packs install the 'skeleton' (indicators, dashboards). Historic Data Collection adds the 'muscle' (actual score data). You need both for the PA body to function immediately.
Real-World Example
An organization activated the ITSM content pack on a Monday. Without running historic collection, the Incident Management dashboard showed empty charts. The ITSM manager was disappointed because leadership expected immediate insights. After running Historic Data Collection with a 12-month lookback, the dashboard populated with a full year of incident trends, resolution time patterns, and SLA compliance data. The ITSM manager presented the dashboard to leadership the same week with actionable trend analysis.
- Apa_admin
- Bpa_power_user
- Creport_admin
- Dinteractive_filter_user
Show full explanation
Correct Answer
C) report_admin
Source
ServiceNow Docs - Interactive Filters | Google fallback
Expert Explanation
Interactive Filters are a dashboard-level feature within the ServiceNow Reporting framework that allow end users to dynamically filter the data displayed across multiple widgets simultaneously. When a user selects a value in an Interactive Filter (such as choosing 'Network' from a Category filter), all widgets on the dashboard that are configured to respond to that filter update their displayed data accordingly. Creating a new Interactive Filter definition, which includes specifying the source table, field, and filter behavior, requires the report_admin role. This role governs administrative access to the reporting platform, including report definitions, dashboard layouts, and interactive filter configurations. The distinction between PA roles (pa_admin, pa_power_user) and reporting roles (report_admin) is important for the exam because PA and Reporting are separate but complementary modules.
Why the Others Are Wrong
A) pa_admin governs PA-specific objects: indicators, indicator sources, breakdowns, targets, signals, and data collection. Interactive Filters sit in the Reporting module, outside PA's administrative scope.
B) pa_power_user is a PA role for creating and managing PA configurations. It does not extend to the Reporting module's Interactive Filter creation capability.
D) interactive_filter_user is not a real ServiceNow role. ServiceNow does not have a dedicated role with this name. Access to use (not create) interactive filters is generally available to any user who can view the dashboard.
Memory Tip
Interactive Filters live in the Reporting world, not the PA world. Report features need report roles. If the feature starts with a reporting concept (dashboards, filters, reports), think report_admin.
Real-World Example
A PA administrator (pa_admin role) built a dashboard with incident trend widgets. She wanted to add an Interactive Filter for 'Assignment Group' so managers could filter the entire dashboard to their team. When she navigated to create the Interactive Filter, she received an access denied error. After the ServiceNow admin granted her the report_admin role, she could create the filter definition and add it to the dashboard layout.
- ATargets
- BContributing Indicators
- CBreakdowns
- DSignals
Show full explanation
Correct Answer
A) Targets, B) Contributing Indicators, C) Breakdowns
Source
ServiceNow Docs - Formula Indicators | Google fallback
Expert Explanation
The formula indicator form in ServiceNow PA contains several related lists that allow administrators to configure all aspects of the formula indicator's behavior. The three key related lists are: (1) Contributing Indicators, which defines the component indicators whose scores feed into the formula expression using variable names enclosed in double brackets; (2) Breakdowns, which specifies how the formula indicator's results can be decomposed by dimensional attributes like assignment group or category; and (3) Targets, which sets performance goal thresholds displayed as reference lines on time series visualizations. These three related lists cover the formula's inputs (contributing indicators), its dimensional analysis capability (breakdowns), and its performance measurement context (targets). Understanding these related lists is essential for configuring and troubleshooting formula indicators.
Why the Others Are Wrong
D) Signals are not configured via a related list on the indicator form. Signals are separate configuration records (pa_signals table) that reference an indicator. The relationship is managed from the signal side, not the indicator side. When you want to create a signal for a formula indicator, you navigate to the Signals module and create a new signal record pointing to the indicator.
Memory Tip
Think of a formula indicator's related lists as the 'TCB' trio: Targets (goals), Contributing (inputs), Breakdowns (dimensions). T-C-B covers the three things every formula needs: what feeds it, how to slice it, and what success looks like.
Real-World Example
A PA administrator creates a formula indicator for SLA Achievement Rate. In the Contributing Indicators related list, she adds 'Met SLA Count' and 'Total SLA Count' as components. In the Breakdowns related list, she adds 'Service' and 'Priority' so managers can see achievement by service offering and urgency level. In the Targets related list, she sets a 95% target threshold. The resulting dashboard widget shows the trend line with breakdown drill-down capability and a clear target reference line.
- AKeyword List
- BBreakdown
- CWord Cloud
- DTime series
Show full explanation
Correct Answer
C) Word Cloud
Source
ServiceNow Docs - PA Text Analytics | Google fallback
Expert Explanation
Text Analytics in Performance Analytics extends PA beyond numeric KPIs into natural language analysis. It processes text fields from ServiceNow records (such as incident short descriptions, problem descriptions, or customer feedback) to identify frequently occurring words and phrases. The Word Cloud visualization is the signature display type for Text Analytics widgets. It renders extracted terms in varying sizes where larger text indicates higher frequency. This visualization type allows analysts to quickly spot trending topics, common issues, or recurring themes without manually reading through thousands of text records. Word Clouds are specifically designed for text frequency data and are one of the available visualization options when configuring a PA widget with a Text Analytics indicator source. Standard PA visualization types like time series, bar charts, and donuts work with numeric scores, while Word Clouds work with text frequency data.
Why the Others Are Wrong
A) Keyword List is not a defined visualization type in PA Text Analytics widgets. While the underlying analysis does extract keywords, the visualization that displays them is called Word Cloud, not Keyword List.
B) Breakdown is a data segmentation concept, not a visualization type. Breakdowns describe how data is sliced (by group, category, location), while visualization types describe how data is rendered (chart, cloud, table).
D) Time series plots numeric scores against time periods. Text Analytics data is not numeric trending data; it is text frequency data. Time series charts cannot meaningfully represent word frequency distributions.
Memory Tip
Text Analytics = Text visualization. Word Cloud is the only visualization type in the options that is inherently designed for text data. If you see 'text' in the question, look for the answer that is about visualizing words, not numbers.
Real-World Example
An IT service desk manager uses a Text Analytics widget with Word Cloud visualization on the incident dashboard. The Word Cloud analyzes the short_description field of all P1 incidents from the past month. The largest words are 'VPN', 'timeout', and 'authentication', immediately revealing that VPN connectivity issues dominate critical incidents. This insight drives the manager to prioritize VPN infrastructure improvements without needing to read through hundreds of individual incident descriptions.
- AViewed
- BCollection Inserts
- CViews
- DTarget Gap
- EDiagnostic Status
- FRelated Dashboards
Show full explanation
Correct Answer
A) Viewed, C) Views
Source
ServiceNow Docs - Platform Analytics Library | Google fallback
Expert Explanation
The Zurich release enhanced the Platform Analytics Library with new columns specifically designed to help administrators audit and clean up their indicator inventory. Over time, PA implementations accumulate hundreds of indicators, many of which may no longer be relevant or actively used. Before Zurich, identifying unused indicators required manually checking each indicator against dashboard configurations and user access logs. The two new columns solve this: 'Viewed' is a boolean that indicates whether the indicator has been accessed (viewed on a dashboard or report) within the tracking period, and 'Views' provides the numeric count of how many times the indicator was viewed. Together, these columns enable administrators to sort and filter the indicator library to quickly find indicators with zero views, which are prime candidates for deactivation. Deactivating unused indicators reduces data collection overhead, improves collection job performance, and simplifies the PA environment.
Why the Others Are Wrong
B) Collection Inserts is not a standard column in the Platform Analytics Library for this purpose. Data collection metrics exist elsewhere in the PA diagnostic tools but were not added as library columns for utilization auditing.
D) Target Gap measures performance against goals (actual vs. target). It tells you how well a metric is performing, not whether anyone is looking at it.
E) Diagnostic Status relates to PA troubleshooting and health checks, not to indicator utilization tracking.
F) Related Dashboards would show configuration relationships but not actual usage. An indicator could be on a dashboard that nobody visits, so dashboard association alone does not prove utilization.
Memory Tip
The two new columns both relate to 'viewing': 'Viewed' (yes/no - has anyone looked-) and 'Views' (how many times-). One is the boolean flag, the other is the counter. Both answer the same question from different angles: is this indicator being consumed-
Real-World Example
A PA administrator inherited an instance with 800 active indicators. Data collection jobs took over 4 hours to complete. Using the new Zurich 'Viewed' and 'Views' columns in the Platform Analytics Library, she filtered for indicators with 0 views in the past 90 days and found 340 indicators that nobody had accessed. After confirming with stakeholders, she deactivated those indicators, reducing data collection time to under 90 minutes and freeing up significant database storage.
- AIt is a time series type widget.
- BThe Indicator in the Widget has no configured Breakdowns.
- C“Follow Element” is not checked in the Widget data settings.
- DThe Widget is prevented from seeing the data due to Element security.
- EThe Breakdown used by the Widget is using a different Breakdown Source.
- FThe Widget is configured to follow an Interactive Filter.
Show full explanation
Correct Answer
B) The Indicator in the Widget has no configured Breakdowns, C) 'Follow Element' is not checked in the Widget data settings, D) The Widget is prevented from seeing the data due to Element security
Source
ServiceNow Docs - Dashboard Breakdown Source | Google fallback
Expert Explanation
The Dashboard Breakdown Source is a dashboard-level control that, when set, filters all responsive widgets to show data for a specific breakdown element (such as a particular assignment group or category). For a widget to respond to this control, three conditions must be met: (1) the widget's indicator must have the relevant breakdown configured, (2) the 'Follow Element' setting must be enabled in the widget's data configuration, and (3) the current user must have element security permissions to view the selected breakdown element's data. If any of these three conditions fails, the widget will not follow the Dashboard Breakdown Source. The indicator's breakdown configuration determines capability (can it break down by this dimension-). The Follow Element setting determines intent (should it respond to dashboard-level selections-). Element security determines permission (is the user allowed to see this breakdown element's data-).
Why the Others Are Wrong
A) Time series widget type does not prevent following the breakdown source. All widget visualization types (time series, single score, dial, bar chart, pie chart) can follow the Dashboard Breakdown Source when properly configured.
E) Different Breakdown Source does not prevent following. The Dashboard Breakdown Source applies to all widgets that have the matching breakdown configured, regardless of which breakdown source the widget uses internally.
F) Following an Interactive Filter is independent of following the Dashboard Breakdown Source. These are complementary filtering mechanisms, not mutually exclusive ones.
Memory Tip
Three reasons a widget ignores the Dashboard Breakdown Source map to 'Can-Will-May': Can it- (breakdown must be configured), Will it- (Follow Element must be checked), May it- (element security must allow it).
Real-World Example
A dashboard has a breakdown source set to 'Assignment Group: Network Team'. Widget A (incident count) follows correctly because its indicator has the Assignment Group breakdown, Follow Element is checked, and the user has network team element access. Widget B (change success rate) shows all groups because Follow Element is not checked. Widget C (P1 incident count) shows no data because element security blocks the user from seeing Network Team data. Widget D (customer satisfaction) shows its aggregate score because its indicator has no Assignment Group breakdown configured.
- AVia Virtual Agent
- BVia Connect Chat
- CBy email notification
- DBy text message
Show full explanation
Correct Answer
C) By email notification
Source
ServiceNow Docs - PA Signals | Google fallback
Expert Explanation
PA Signals monitor indicator scores against defined thresholds and notify responsible users when conditions are met (such as 'Incident backlog exceeds 500' or 'SLA achievement drops below 90%'). When a signal fires, the responsible user receives an initial email notification describing the condition. If the signal remains in an unresolved state (the responsible user has not opened and addressed it), the PA signal framework sends periodic email reminders to ensure the condition does not go unnoticed. The reminder frequency can be configured in the signal settings. Email was chosen as the notification channel because it provides a persistent, documented record of the alert that reaches users on any device (phone, laptop, tablet) without requiring them to be actively using the ServiceNow platform. This is especially important for executive stakeholders who may not log into ServiceNow daily but need to be aware of critical KPI threshold breaches.
Why the Others Are Wrong
A) Virtual Agent is designed for interactive self-service conversations, not for delivering system-generated performance alerts. Its conversational model is not suited for one-way threshold breach notifications.
B) Connect Chat is a synchronous messaging tool that requires users to be online in the platform. Signal reminders need to reach users regardless of their online status, which is why asynchronous email is preferred.
D) Text message is not the out-of-box notification method for PA signals. While SMS integrations are possible through the Notify plugin, PA signals use email as the standard reminder channel.
Memory Tip
Signals send 'S-E-mails': Signal Email reminders. When in doubt about PA notification methods, email is almost always the answer for system-generated alerts.
Real-World Example
A service delivery manager is the responsible user for a signal that monitors 'Average Incident Resolution Time'. When resolution time exceeds the 4-hour threshold, she receives an email alert. She is traveling and does not address it. Two days later, the system sends a reminder email noting the signal is still unresolved. She sees the reminder on her phone, logs into ServiceNow from her laptop, investigates the root cause (a staffing gap on the night shift), and resolves the signal by documenting the corrective action taken.
- AThe Analytics Center replaces the classic Performance Analytics application.
- BThe Platform Analytics Workspace is a paid application.
- CThe Platform Analytics Workspace lets you manage Next Experience data visualizations and dashboards.
- DYou can configure the Analytics Center to be accessible from any ServiceNow Workspace.
Show full explanation
Correct Answer
C) The Platform Analytics Workspace lets you manage Next Experience data visualizations and dashboards, D) You can configure the Analytics Center to be accessible from any ServiceNow Workspace
Source
ServiceNow Docs - Analytics Center | Google fallback
Expert Explanation
The Platform Analytics Workspace and Analytics Center represent ServiceNow's evolution of the PA user experience into the Next Experience UI framework. The Platform Analytics Workspace provides a dedicated environment for managing Next Experience dashboards and data visualizations, which use the modern UI components (UX Framework) rather than the classic UI dashboard technology. The Analytics Center takes this further by making analytics capabilities available within any ServiceNow Workspace application. This means an ITSM agent working in the ITSM Workspace can access relevant PA dashboards and data visualizations without leaving their primary work context. The key architectural principle is integration and accessibility: analytics should be available where users work, not siloed in a separate application. Both components coexist with the classic PA application, providing a modern alternative without removing the traditional tools that administrators rely on for configuration.
Why the Others Are Wrong
A) Replaces the classic PA application is incorrect because ServiceNow follows a coexistence strategy. The classic PA modules remain functional for indicator configuration, data collection management, breakdown setup, and other administrative tasks. The new experiences enhance data consumption and visualization, not replace administrative capabilities.
B) Paid application is incorrect. The Platform Analytics Workspace is included with PA entitlements and does not require an additional purchase. ServiceNow includes workspace-based analytics experiences as part of the platform's evolution toward the Next Experience UI.
Memory Tip
Think of it as 'old and new coexist': Classic PA handles configuration (admin), Analytics Workspace handles visualization (Next Experience), and Analytics Center handles accessibility (any workspace). None replaces the others.
Real-World Example
An organization uses ITSM Workspace as the primary interface for their service desk agents. The PA administrator configures the Analytics Center to appear as a module within the ITSM Workspace. Now, agents can click into the Analytics Center directly from their workspace to view incident trend dashboards, SLA performance charts, and team workload visualizations without switching to the classic UI or navigating to a separate application. The same Analytics Center is also added to the CSM Workspace for customer service managers to access their own analytics views.
- AExecuting scripted breakdown mappings via natural language.
- BAdding a generated data visualization directly to a dashboard.
- CSharing the exploration with tagged users for collaboration.
- DSummarizing the entire exploration via Generative AI.
- EModifying the underlying RaptorDB column-store index.
- FResetting KPI Signal baselines automatically.
Show full explanation
Correct Answer
B) Adding a generated data visualization directly to a dashboard, C) Sharing the exploration with tagged users for collaboration, D) Summarizing the entire exploration via Generative AI
Source
ServiceNow Docs - Now Assist for Platform Analytics | Google fallback
Expert Explanation
Now Assist for Platform Analytics brings Generative AI capabilities to the data exploration experience. The Explorations interface allows users to ask natural language questions about their data and receive AI-generated visualizations and insights. Three advanced capabilities stand out: First, users can add any AI-generated visualization directly to an existing dashboard, converting ad-hoc discoveries into persistent reporting assets without manually recreating the widget configuration. Second, explorations can be shared with tagged users, enabling collaborative analytics where team members contribute to and build upon each other's data investigations. Third, the Generative AI can summarize an entire exploration session, distilling multiple queries and visualizations into a coherent narrative of findings. These capabilities represent a significant shift from traditional PA workflows where insights required manual configuration, individual analysis, and separate documentation of findings.
Why the Others Are Wrong
A) Executing scripted breakdown mappings is an administrative configuration task that requires technical PA knowledge. Natural language exploration is designed for data consumption and insight generation, not for executing PA administrative scripts.
E) Modifying RaptorDB column-store indexes is a deep infrastructure operation that should never be exposed through a natural language interface. Database index management requires careful performance analysis and is handled at the platform level.
F) Resetting KPI Signal baselines is an administrative action with significant implications for alert accuracy. Automatic resets through an exploration interface could disrupt established monitoring thresholds.
Memory Tip
The three correct capabilities follow the 'Create-Share-Summarize' pattern: create a visualization and add it to a dashboard, share the exploration with colleagues, and summarize findings with AI. These are all collaborative output actions, not administrative configuration actions.
Real-World Example
A service delivery manager opens Explorations and asks, 'Show me the trend of P1 incidents by category over the past 6 months.' Now Assist generates a time series chart showing a spike in network-related P1s. She asks a follow-up question about resolution times for network incidents and gets another visualization. She adds both visualizations directly to her executive dashboard (capability B), shares the exploration with the network team lead for investigation (capability C), and generates an AI summary of the entire exploration to include in her weekly status report (capability D).
- A0 - This must be checked to collect any Breakdowns.
- BThere is no limit on the levels of Breakdowns collected.
- C2 - Two levels of Breakdowns are always collected by default.
- D1 - Without the matrix, a single level of Breakdowns is collected.
Show full explanation
Correct Answer
D) 1 - Without the matrix a single level of Breakdowns is collected
Source
ServiceNow Docs - Collect Breakdown Matrix | Google fallback
Expert Explanation
The 'Collect breakdown matrix' checkbox on the indicator record controls the depth of breakdown data collection. When unchecked (the default for most indicators), PA collects scores at a single breakdown level. This means if an indicator has three breakdowns configured (Assignment Group, Category, and Priority), the collection job generates three independent sets of breakdown scores: one set showing scores by each Assignment Group element, one set by each Category element, and one set by each Priority element. When the matrix IS checked, PA collects all possible two-way combinations: scores by Assignment Group AND Category, scores by Assignment Group AND Priority, and scores by Category AND Priority. This produces a much larger volume of score records but enables drill-down analysis across multiple dimensions simultaneously. The single-level default balances analytical capability with data volume management, as the number of matrix combination scores can grow exponentially with each added breakdown.
Why the Others Are Wrong
A) 0 levels incorrectly states that breakdowns require the matrix property to be collected at all. Single-level breakdowns are always collected for configured breakdowns regardless of the matrix setting. The matrix property only controls multi-level cross-tabulation.
B) No limit overstates the collection scope. Even with the matrix enabled, the practical limit is the combinations of configured breakdowns. Without the matrix, the limit is explicitly one level.
C) 2 levels by default describes what happens when the matrix IS enabled, not when it is disabled. Two-level combination collection is the matrix behavior, which is the opposite of the unchecked state.
Memory Tip
No Matrix = No Mixing. Without the matrix checkbox, breakdowns are collected individually (level 1), never mixed together (level 2+). The matrix creates the 'mix' of breakdown combinations.
Real-World Example
An indicator tracking 'Open Incident Count' has three breakdowns: Assignment Group (50 groups), Priority (5 levels), and Category (20 categories). With single-level collection (matrix unchecked), each collection cycle produces: 50 + 5 + 20 = 75 breakdown score records plus the aggregate. With the matrix enabled, the combinations explode: 50x5 + 50x20 + 5x20 = 1,350 matrix score records in addition to the 75 single-level scores. For daily collection over a year, this difference scales from 27,375 to 520,125 additional records. The matrix should only be enabled when cross-dimensional analysis (such as 'show me P1 incidents specifically for the Network team') is a confirmed business requirement.
Free exam updates. No spam. Unsubscribe anytime.
You scored 0/15 on the 15-question preview.
The full course keeps the same answer breakdown style across all 216 questions.
Your first exam attempt is free. Your second costs $350.
Many students also study:
Compare all 18 practice tests, or use the cert quiz to plan what to study next.
Looking for a different certification-
Browse all 18 practice tests →