Thekey differencebetweenReportingandPerformance Analytics (PA)is how they handle data over time.
Showsreal-time datafrom tables.
Runs queries on dataat the momentthe report is generated.
Cannot analyze historical trendsunless data is manually stored.
Used forstatic reports, lists, charts, or dashboards.
Capturessnapshotsof data at scheduled intervals (e.g., daily, weekly).
Tracks trends and KPIs (Key Performance Indicators)over time.
Helps organizationsforecast and analyze historical patterns.
Used forbusiness intelligence and proactive decision-making.
ReportingPerformance Analytics (PA)
Incorrect Answer Choices Explanation:B. Performance Analytics can show trends; Reports cannot.
Reporting can show trends usingaggregated data(e.g., grouped by date), butPA is specifically designedfor tracking trends over time.
C). Reports can be run on a scheduled basis; Performance Analytics cannot.
BothReports and PA can be scheduledto run at regular intervals.
D). Performance Analytics data can be published to Dashboards; Reports cannot.
Reportscanbe published todashboards, just like Performance Analytics.
E). Performance Analytics shows KPIs; Reporting does not.
Reports candisplay KPIsusing calculated metrics and aggregations, butPA is optimizedfor KPI tracking over time.
Performance Analytics vs. Reporting
ServiceNow Reporting Overview
Official CSA Documentation Reference:

InServiceNow Flow Designer, adata pillrepresentsvariables, record fields, or outputs from previous stepsthat can be used dynamically in the flow.
Data pillsallow flow designers to referencerecord datawithout manually specifying table fields.
Dragging a data pillonto a flow step ensures that the correct values areautomatically mappedfrom the referenced record.
This is the recommended method for using record datawithin a flow.
Why is Option D Correct?
Why Are the Other Options Incorrect?A. Drag the table icon onto the flow definition IncorrectbecauseFlow Designer does not use table iconsfor referencing records.
Instead, it utilizesdata pills and actionsto retrieve and manipulate record data.
B: Use the condition builder to specify the desired values
Incorrectbecause thecondition builderis used fordecision logic(e.g., If-Else conditions), not for referencing record data.
C: Specify the source table on the data pill related list
Incorrectbecause youcannot manually specifya table in a data pill.
Data pills areautomatically createdwhen an action retrieves data from a record.
E: Add the table reference using the slush bucket
Incorrectbecauseslush bucketsare used in ServiceNow for selecting multiple items (e.g., roles, groups),not for referencing record data in a flow.
ServiceNow Flow Designer - Using Data Pills
ServiceNow Flow Designer - Best Practices for Record Referencing
ServiceNow ITSM - Automating Workflows with Flow Designer
References to Official Certified System Administrator (CSA) Documentation:

Abusiness rulein ServiceNow is a server-side script written inJavaScriptthat executes when a record is inserted, updated, deleted, or queried. Business rules allow for automation and enforcement of business logic without requiring manual intervention.
Business rules arenot tied to formsbut instead runon the server-sidewhen a database operation occurs. They can be configured to execute:
Beforea record is saved (Before Business Rule)
Aftera record is saved (After Business Rule)
Asynchronously(Async Business Rule)
Before a query is run on the database(Query Business Rule)
Explanation of the Correct answer:B. A business rule can be a piece of JavaScript(Correct) Business rules are written inJavaScript, allowing administrators to define custom logic that executes on the server.
These scripts can modify data, enforce rules, validate fields, or trigger other workflows.
Example JavaScript snippet for a business rule:
if(current.state=='3'&& current.priority!='1') {
current.priority='1';
gs.addInfoMessage("Priority set to High because state is Resolved.");
}
This rule ensures that if an incident's state is changed toResolved, its priority is automatically set to High.
Why the Other Options Are Incorrect:A. A business rule must run before a database action occurs (Incorrect) Business rulescan run before a database action occurs, but they can also executeafterorasynchronously.
Business rules have four execution types:
Before- Runs before the record is inserted/updated in the database.
After- Runs after the record is committed to the database.
Async- Runs in the background after the transaction completes.
Query- Runs before data is returned to a user (modifies query results).
C: A business rule must not run before a database action occurs (Incorrect) This is false because some business rulesdo run beforea database action (e.g., aBefore Business Rulecan validate data before saving).
D: A business rule monitors fields on a form (Incorrect)
Business rulesdo not monitor form fields directly. Instead, they execute based on database operations.
If real-time monitoring of form fields is needed,Client Scripts(not Business Rules) are used for this purpose.
Automaticallyassigning prioritybased on ticket severity.
Preventing updates to certain records if a condition is not met.
Sending email notifications when a record changes.
Modifying data before it is saved to enforce business policies.
Example Use Cases for Business Rules:
References:ServiceNow Documentation: Business Rules Overview
ServiceNow CSA Learning Path: Business Rule Fundamentals
ServiceNow Docs: Server-Side Scripting in Business Rules