In ServiceNow, the impersonation feature allows users to temporarily act as another user without having to log out and log back in. This is particularly useful for testing and troubleshooting.
Why is "impersonator" the Correct Answer?
Allows Users to Switch Between Accounts Without Logging Out
Users with the impersonator role can impersonate other users from the User Menu (top-right of the screen).
This allows them to see what the other user sees, including roles, permissions, and UI settings.
Commonly Used in Testing and Troubleshooting
Helps test permissions, workflows, and security settings without needing multiple login sessions.
QA and testing teams often use impersonation to validate how different users interact with the system.
Does Not Grant Admin-Level Permissions
Unlike the admin role, impersonator only allows switching between users, without providing system-wide control.
How to Impersonate a User in ServiceNow:
Click on your profile icon (top-right corner).
Select Impersonate User from the dropdown.
Search for and select the user to impersonate.
ServiceNow will reload, and you will now be acting as that user.
Incorrect Answer Choices Analysis:
A . service_desk
❌ Incorrect - This is a functional role for Service Desk agents but does not allow impersonation.
C . admin
❌ Incorrect - While admins can impersonate users, the admin role is not required for impersonation. The impersonator role alone is sufficient.
D . incognito
❌ Incorrect - No such role exists in ServiceNow.
Official ServiceNow Documentation Reference:
ServiceNow Docs - Impersonation Feature
📖 How to Impersonate a User
ServiceNow Docs - Roles and Permissions
📖 Understanding the Impersonator Role
Conclusion:
The correct answer is:
✅ B. impersonator
The impersonator role allows users to switch between user accounts without logging out, making it ideal for testing and troubleshooting.

In ServiceNow,Business Rulesare server-side scripts that executeat specific timesrelative to database operations. The"When" settingdetermineswhenthe Business Rule runs in relation to a record action (Insert, Update, Delete, Query).
Why is Option A Correct?Before
Executesbeforea record is saved to the database.
Used tovalidate data, modify values, or prevent an action(e.g., stopping an invalid update).
After
Executesaftera record is inserted, updated, or deleted.
Commonly used fortriggering notificationsor creating related records.
Async (Asynchronous)
Runsaftera database operation but executes inthe background.
Ideal forlong-running or performance-heavy tasks(e.g., integrating with external systems).
Display
Executesbefore a form loads, allowing modifications to fieldsbefore they are displayedto the user.
Typically used forpre-filling form fieldsbased on user roles or conditions.
Why Are the Other Options Incorrect?B. Prior to, Synchronous, on Update
"Prior to"is not a valid Business Rule execution timing.
"Synchronous"is a general term but isnot a specific execution timing optionin Business Rules.
"on Update"is a database operation,not an execution timing.
C). Insert, Update, Delete, Query
These aredatabase operationsthat trigger Business Rules,not execution timings.
Execution timing determineswhen(before, after, etc.), while these determinewhat triggers it.
D). Before, Synchronous, Scheduled Job, View
"Synchronous"is not a Business Rule timing option.
"Scheduled Job"refers toScheduled Jobs(not Business Rules).
"View"is a UI-related concept,not a Business Rule execution timing.
ServiceNow Business Rules - How They Work
ServiceNow Best Practices - Business Rule Execution Timing
ServiceNow Developer Documentation - Before, After, Async, and Display Business Rules References to Official Certified System Administrator (CSA) Documentation:

A Natural Language Query (NLQ) allows users to filter list data using plain English instead of using the traditional condition builder. NLQ interprets human-readable search terms and translates them into system queries, making it easier for non-technical users to retrieve information without having to understand the underlying database structure.
Key Features of NLQ in ServiceNow:
User-friendly: Users can type a question in normal language (e.g., "Show me all open incidents assigned to me").
Automatic Query Conversion: The system translates the NLQ into a structured query that ServiceNow understands.
Faster Search & Filtering: It helps in quickly filtering and finding records without manually setting conditions.
Works on Lists: NLQ is used primarily in list views where users need to filter or search records.
Example Usage:
If a user enters "Show me all open incidents for John Doe", the NLQ engine will convert it into a structured query like:
[State = Open] AND [Assigned To = John Doe]
Reference from Certified System Administrator (CSA) Documentation:
ServiceNow Product Documentation → "Natural Language Query Overview"
ServiceNow List Filters and Condition Builder → "Using Natural Language Queries for Filtering"