In ServiceNow,Access Control Rules (ACLs)determine user permissions for accessing tables, records, and fields. The evaluation order follows a structured hierarchy to ensure security and proper access control enforcement.
Table-Level Access Control- The system first checks if the user has access to the table. If the user does not have access at the table level, field-level ACLs are not evaluated.
Field-Level Access Control- If table access is granted, the system evaluates field-level access. A user must pass both the table-level and field-level conditions to access specific fields.
Row-Level Access- If there are row-level ACLs (e.g., access based on record ownership), they are also evaluated.
A). Ensures user has access to the fields in a table, before considering their access to the table- Incorrect because table access is evaluated first, not field access.
B). Ensures user can get to work as quickly as possible- Access controls prioritize security over speed, so this is not the primary result of ACL order evaluation.
C). Ensures user has access to the application, before evaluating access to a module within the application- Application access is controlled separately from ACLs and does not follow the same hierarchy.
Reference:ServiceNow KB0541355 - Access Control Evaluation Order

In ServiceNow, when building filter conditions using theCondition Builder, there are three key components:
Field (Filter Criteria):The specific database field you are filtering on.
Operator:A choice list that defines the condition (e.g., "is", "contains", "starts with").
Value:The value you are checking against.
Among these components,the Operator is always a choice list, as it provides predefined options for filtering.
The Operator determines how the Field and Value should be compared. For example:
"State is Active"(where "is" is the Operator)
"Priority is greater than 2"(where "is greater than" is the Operator)
Other components, such as Filter Criteria (fields) and Match Criteria, do not always function as choice lists.
Reference:
ServiceNow Condition Builder Documentation
ServiceNow CSA Training Material

ANatural 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.
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.
Key Features of NLQ in ServiceNow: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]
ServiceNow Product Documentation# "Natural Language Query Overview"
ServiceNow List Filters and Condition Builder# "Using Natural Language Queries for Filtering" References from Certified System Administrator (CSA) Documentation:

When movinghomepagesordashboardsbetween ServiceNow instances (e.g., from development to production), they arenot automatically includedin an update set. Instead, they must bemanually addedto the update set before migration.
C). Manually add them to the update set
Homepages and dashboards donotget included in update sets by default.
To move them, you must:
Navigate toSystem UI > Homepage Admin > PagesorPerformance Analytics > Dashboards Select the homepage or dashboard you want to move.
Use theAdd to Update Setfunction to include them in your active update set.
Once added, move the update set to another instance and commit it.
A). Create a separate update set for them
While it's a good practice to keep UI elements in separate update sets, it isnot a requirement.
Homepages/dashboards can be added toany active update setmanually.
B). They are automatically added to the update set
Incorrect-ServiceNowdoes notautomatically add homepages or dashboards to update sets.
D). They cannot be moved via update set
Incorrect-Theycanbe moved via update sets, but they must bemanually added.
References:ServiceNow Documentation:Moving Homepages and Dashboards Between Instances ServiceNow Best Practices:Working with Update Sets

In ServiceNow,User Criteriais the mechanism used to control and determine user access toknowledge bases (KBs) and knowledge articles. User criteria define which users, groups, or roles canread, write, and contributeto a knowledge base or specific articles within it.
How User Criteria Works:User Criteria are applied at both theknowledge baselevel and theknowledge articlelevel to manage access. They can be configured with specific conditions to allow or restrict access based on:
Users(specific users can be added directly)
Groups(access can be granted to a specific user group)
Roles(users with specific roles can be given access)
Advanced conditions(such as department, company, location, etc.)
A knowledge base can havemultiple user criteria, and a single user criterion can apply to multiple knowledge bases.
Read User Criteria- Determines who can view the knowledge base or an article.
Write User Criteria- Determines who can create, edit, or contribute knowledge articles.
Exclusions- You can exclude users or groups from accessing specific knowledge bases or articles even if they meet other conditions.
A: sn_kb_read, sn_article_read:
These are not standard ServiceNow permissions for controlling knowledge access.
In ServiceNow, permissions are managed through roles and user criteria, not direct ACL names like these.
B: Privacy Settings:
ServiceNow does not use "Privacy Settings" as an access control mechanism for knowledge bases.
Privacy settings might be relevant in other contexts, such asuser profiles or system preferences, but not for knowledge access control.
C: Read Access Flag:
There is no "Read Access Flag" in ServiceNow's knowledge management module.
Access is controlled viaUser Criteria, Roles, and Knowledge Base Settings.
Key Features of User Criteria in Knowledge Management:Why Other Options Are Incorrect?Official ServiceNow Documentation References:For more details, refer to the official ServiceNow documentation:
User Criteria for Knowledge Bases
Managing Knowledge Base Access
Knowledge Management User Criteria