InServiceNow,Business Rulesareserver-side scriptsthat execute when a record is created, updated, deleted, or queried. The"When"setting in a Business Rule determineswhen the rule runs in relation to database operations.
BeforeExecutes before a record is inserted, updated, or deleted.
Used forvalidations, data modifications, and setting field valuesbefore saving.
AfterExecutes after a record has been committed to the database.
Used fortriggering notifications, writing logs, or updating related records.
Async(Asynchronous)Executes after a short delay, allowing the main transaction to complete first.
Used forlong-running processes like API calls, email sending, or external system updates.
DisplayExecutes before the record is sent to the client (UI).
Used topopulateg_scratchpadfor client-side scripts.
The Four Timing Options for Business Rules:
Example Use Cases for Business Rule Timings:Business Rule Timing
When It Runs
Use Case
Before
Before saving to the database
Validate data, auto-populate fields
After
After saving to the database
Send notifications, update related records
Async
Shortly after the transaction completes
Call an external API, send an email
Display
Before the form loads
Pass server data to client-side scripts (g_scratchpad)
A: Insert, Update, Delete, QueryIncorrect- These aredatabase operations, not the execution timing options for Business Rules.
C: Prior to, Synchronous, on UpdateIncorrect- These termsdo not matchthe standard ServiceNowBusiness Rule timing settings.
D: Before, Synchronous, Scheduled Job, ViewIncorrect- "Scheduled Job" isnota Business Rule timing option (it is part ofScheduled Script Executions).
Incorrect Answer Choices Analysis:
ServiceNow Docs - Business Rules Overview#Understanding Business Rules
ServiceNow Docs - Best Practices for Business Rules#Best Practices for Business Rules Official ServiceNow Documentation References:

Table Builderis aServiceNow featurethat allows administrators tomodify table structures, configure forms, and manage relationshipswithin a visual interface.
When modifying form layouts inTable Builder, administrators can:
#Add, remove, or rearrange fieldson the form.
#Create new form sectionsto organize fields logically.
#Configure default valuesand field properties.
#Manage related listsand relationships between tables.
Option B (Changing the database schema)is incorrect because modifying form layouts does not require schema changes (though Table Builder can modify schemas, it's not necessary for layout changes).
Option C (Editing system scripts)is incorrect because form layout changes do not require scripting.
Option D (Altering the page header theme)is incorrect because themes affect the UI appearance, not form structure.
#Reference:ServiceNow Platform Fundamentals - Table Builder & Form Configuration

The Dependency View provides a visual representation of the relationships between configuration items (CIs) in ServiceNow. It allows you to see how CIs are connected and how changes to one CI may impact others.
References:
ServiceNow Product Documentation: Configuration item relationships in the CMDB - https://docs.servicenow.
com/bundle/vancouver-servicenow-platform/page/product/configuration-management/concept
/c_CIRelationships.html
ServiceNow Community: How to display dependencies for CIs in the Dependency View - https://www.
servicenow.com/community/service-management-forum/load-a-specific-dependency-view-map/m-p/410421

InServiceNow Flow Designer, aflowis an automated process that consists of actions, conditions, and triggers.
Two key componentsdetermine when a flow should run:
Trigger
Defineswhenthe flow should execute.
Examples:
When arecord is created/updated/deleted.
When anAPI call is received.
On ascheduled basis.
Condition
Specifiesadditional criteriathat must be met for the flow to proceed.
Examples:
If thepriority is High.
If thestatus is Resolved.
Aflowis designed tosend an email notificationwhen ahigh-priority incident is assigned.
Trigger:"Incident table # When a record is updated."
Condition:"Priority = High AND State = Assigned."
A). Trigger and Condition Pill
No such term as "Condition Pill"exists in Flow Designer.
B). Scope and Trigger Condition
"Scope" defines theapplication boundary, not when a flow runs.
D). Trigger Criteria and Clock
"Clock" is not usedfor defining flow execution.
E). Condition and Table
Atable does not define when a flow runs; it only stores records.
Reference:ServiceNow CSA Documentation - Flow Designer: Triggers & Conditions ServiceNow Product Documentation - Automating Workflows with Flow Designer(https://docs.servicenow.
com)

InServiceNow, theNumber Maintenanceapplication is used toconfigure and modify numbering formats for specific tables. This application allows administrators to control how records are numbered across different modules.
Customization of Number Formats
Administrators can defineprefixes, number sequences, and suffixesfor records in different tables.
Example:INC0001001forIncidents,REQ0002001forRequests.
Resetting or Adjusting Number Sequences
You can manually adjust the numbering sequence if needed.
Example: Resetting incident numbering to start from a specific value.
Supports Multiple Tables
Works for standard tables likeIncidents, Problems, Requests, Change Requests, etc.
Can also be configured forcustom tables.
Application Navigation
Path:
Go toAll # System Definition # Number Maintenance
Locate the table and modify its numbering settings.
Key Features of Number Maintenance:Why Option A (Number Maintenance) is Correct?"Number Maintenance" is the official ServiceNow application for managing number formats per table.
Why Other Options Are Incorrect?B. System Maintenance- Incorrect; no such module in ServiceNow manages numbering formats.
C: Table Maintenance- Incorrect; this does not exist as an application in ServiceNow.
D: Record Maintenance- Incorrect; not a valid ServiceNow feature for modifying number formats.
ServiceNow Docs - Number Maintenance Configurationhttps://docs.servicenow.com ServiceNow Learning - Customizing Numbering Schemes ServiceNow System Definition - Number Format Best Practices References from Certified System Administrator (CSA) Documentation: