InServiceNow, afilter conditionis used toquery data from tables. It consists of three main components:
1. Column (Field)Represents the database column (or field) that is being filtered.
Example:Priority,State,Assigned To
In ServiceNow UI, this appears as thefirst dropdownin a filter condition.
2. OperatorDefines the comparison condition for the filter.
Examples:is,is not,greater than,contains,starts with
In ServiceNow UI, this appears as themiddle dropdownin a filter condition.
3. ValueSpecifies the criteria being matched against the column.
Example:High,Closed,John Doe
In ServiceNow UI, this is thethird input fieldin a filter condition.
Example of a Filter Condition in ServiceNow UI:Column (Field)
Operator
Value
Priority
is
High
State
is not
Resolved
This filter will returnrecords where:
ThePriorityfield is set toHigh
TheStatefield is NOTResolved
B: Match CriteriaIncorrect-No such term exists in ServiceNow filters.
C: FieldIncorrect- "Field" is another word for "Column", but "Column" is the correct term in ServiceNow filter conditions.
Incorrect Answer Choices Analysis:
ServiceNow Docs - Filtering Data#How to Create Filters in ServiceNow
ServiceNow Docs - Query Builder and Operators#Building Filter Queries
Official ServiceNow Documentation References:

In ServiceNow, anUpdate Setis a mechanism used to package and transfer customizations from one instance to another. TheDefault Update Setis automatically created for every instance and captures all unassigned configuration changes. However, it is considered abest practice not to use the Default Update Set for moving customizations between instances.
Lack of Organization & Traceability
The Default Update Set collects all modifications automatically, making it difficult to track specific changes related to a particular project or feature.
If multiple administrators or developers work in an instance, their changes will all be mixed together in the Default Update Set, leading to confusion and conflicts.
Risk of Losing Changes
Default Update Sets are not automaticallycomplete. Since users can forget to mark their customizations explicitly for an update set, some changes might not get captured.
If a system admin forgets to move a customization into a named update set, those changes may not be included in the migration process.
Cannot Be Moved Between Instances
The Default Update Setcannot be retrieved or movedbetween instances because it is system-managed. This makes itimpossibleto use it for transferring customizations effectively.
Named Update Sets, on the other hand, allow developers to package only the required changes for controlled migration.
Best Practice: Use Named Update Sets
It is highly recommended to create anamed Update Set(e.g., "Incident_Enhancements_Q1_2025") for each set of related changes.
This provides a structured way to track, test, and promote configurations fromdevelopment # test # production environmentsin a controlled manner.
A: Merge Default Update Sets before moving between instancesIncorrect - The Default Update Set cannot be moved between instances, so merging it would not serve any purpose.
B: Submit Default Update Set to Application RepositoryIncorrect - The Application Repository is used forScoped Applications, not for update sets. The Default Update Set is system-managed and should not be used for structured deployments.
D: Keep Default Update Set to a maximum of 20 records, for troubleshooting purposesIncorrect - While keeping the Default Update Set small might be useful for tracking small changes, there is no such best practice limit of "20 records." It is still not recommended for migrations.
ServiceNow Product Documentation - Update Sets Best Practices#Update Set Best Practices ServiceNow Community Best Practices - Managing Update Sets#Managing Update Sets Reasons Why You Should Not Use the Default Update Set for Moving Between Instances:Incorrect Answer Choices Analysis:Official ServiceNow Documentation References:Conclusion:The correct answer isC. You should not use the Default Update Set for moving between instances.The best practice is to always createnamed Update Setsto ensure controlled, traceable, and reliable migrations of customizations between ServiceNow instances.

The System Administrator (admin) role is the most powerful and common role in ServiceNow, providing access to nearly all platform features, functions, and data. Users with this role have full control over system configurations, user management, security settings, application access, and more.
Key Capabilities of the "admin" Role:
Full system access to all applications, modules, tables, and records.
Ability to configure and customize the platform.
Create, update, and delete records in any table.
Manage roles and users, including assigning roles to others.
Configure Access Control Rules (ACLs) to define security policies.
Why the other options are incorrect:
A . Security Admin [security_admin] → Incorrect. The security_admin role is primarily for managing security settings and access control rules. While powerful, it does not inherently provide access to all platform functions like the admin role does.
B . Sys Admin [sys_admin] → Incorrect. There is no such role as "sys_admin" in ServiceNow. The correct role is admin.
C . Admin [sn_admin] → Incorrect. sn_admin is not a standard ServiceNow role. The official role is simply admin.
Reference:
ServiceNow Developer Glossary
ServiceNow Role Documentation

When an item isordered from the Service Catalog, two main records are created in ServiceNow:
sc_req_item(Requested Item - RITM)
Representseach individual itemin the order.
Tracks the approval process, fulfillment, and delivery for that specific item.
sc_task(Service Catalog Task - SCTASK)
Used toassign workto different fulfillment teams (e.g., IT, HR).
A singlesc_req_itemmay generate multiplesc_taskrecords.
A user orders aMacBook Profrom the Service Catalog.
ARequest (REQ#)is created.
ARequested Item (RITM#)is generated to track the MacBook order.
One or moreService Catalog Tasks (SCTASK#)are created for fulfillment (e.g., Procurement, Shipping).
C). A change record
Change records (chg_request) are created only if thecatalog item is linked to Change Management, which is not always the case.
D). An Incident record
Incidents (incident) are created forissues or break/fix cases, not for service requests.
E). A problem record
Problem records (problem) are used forroot cause analysis, not service catalog requests.
Reference:ServiceNow CSA Documentation - Service Catalog & Request Fulfillment ServiceNow Product Documentation - Request, RITM, and SCTASK Relationships(https://docs.servicenow.
com)
Final answer: A, B (A record ofsc_task, A record ofsc_req_itemtable)