How Do Indicator Frequencies and Breakdowns Work in Performance Analytics?
Select the statements which correctly describe the respective Performance Analytics object behavior. (Choose two.)
Community Votes
50% of anonymous learners picked answer AD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests precise knowledge of PA indicator lifecycle rules, commonly trapping candidates who assume strict frequency matching or confuse automated indicator query logic with manual breakdown mappings.
Master how ServiceNow Performance Analytics decouples indicator aggregation frequencies from source collection schedules and handles breakdown configurations. Community consensus confirms that indicators can aggregate data at different intervals than their sources, and monthly sources remain compatible with daily collection jobs.
Option CD is frequently selected due to outdated UI annotations suggesting rigid frequency alignment and a misconception that all indicators require explicit breakdown mappings.
Community Discussion (3 comments)
- A - annotation in Indicator source form "Indicator sources can only be selected in indicators if this setting matches the frequency of the indicator." +C +D
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option A is accurate because Performance Analytics allows indicators to aggregate data at frequencies independent of their underlying sources, such as collecting daily metrics and rolling them up into a weekly indicator. Option D is correct since collection jobs can be scheduled at any interval regardless of the source's defined frequency, with the platform intelligently handling skipped or accumulated runs. This flexibility ensures administrators can align data ingestion with system load rather than being constrained by business reporting cycles.Why the Other Options Are Wrong
Option B is false because breakdowns define segmentation rules and can be assigned to indicators at any time, well before the first collection cycle executes. Option C incorrectly claims that automated indicators require breakdown mappings; automated indicators dynamically query the ServiceNow database using configured queries, eliminating the need for static mapping tables used exclusively in manual indicators. Administrators should configure breakdowns early in the setup phase to avoid unnecessary rework during collection cycles.Community Comment Notes
Candidates frequently debate this item, with votes split evenly between AD and CD. Comment [3] correctly validates A and D by highlighting the platform's ability to collect daily while aggregating weekly. Comment [2] references an older form annotation that incorrectly implied strict frequency matching, leading some to choose C and D. Comment [1] reinforces AD as the verified answer based on official training materials and hands-on PDI testing.Official Reference
- https://docs.servicenow.com/bundle/vancouver-platform-performance-analytics/page/product/performance-analytics/task/t_CollectingDataWithIndicatorSources.html
- https://docs.servicenow.com/bundle/vancouver-platform-performance-analytics/page/product/performance-analytics/concept/c_Breakdowns.html
- https://docs.servicenow.com/bundle/vancouver-platform-performance-analytics/page/product/performance-analytics/concept/c_AutomatedVsManualIndicators.html
Exam Strategy
Focus on memorizing the behavioral differences between automated and manual indicators, particularly regarding data sourcing and aggregation flexibility. When evaluating frequency-related options, remember that collection jobs and indicator rollups operate on independent schedules, allowing for optimized system performance without breaking reporting requirements.
Related Analysis
Practice All CAS-PA Questions
Access 79 questions with complete answers and detailed explanations.
View Full CAS-PA Practice Test →