When creating acustom table in ServiceNow, the platform automatically assigns a table name prefixed with" u_"to differentiatecustomtables fromout-of-the-box (OOB) tables.
The default prefix"u_"is applied to allcustom global tables.
The table name follows the format:"u_" + [custom name].
Example:
If you create a table named"abc", the system assigns it the table name:u_abc.
All custom tables created by usersautomatically receive the "u_" prefix.
Prevents conflicts withServiceNow's internal tables.
Ensurescustom tables are easy to identify.
Naming Convention for Custom Tables:Why "C. u_abc" is Correct?
A: snc_abc - Incorrect
"snc_" is not used for custom tables; it is reserved forinternal ServiceNow functionality.
B: abc - Incorrect
Custom tablesdo not use raw names; they always include a prefix (u_).
D: sys_abc - Incorrect
"sys_" is reserved forsystem tables(e.g.,sys_user,sys_db_object).
Explanation of Incorrect Options:
ServiceNow Docs: Creating Custom Tables
ServiceNow CSA Study Guide - Table Administration
ServiceNow Product Documentation: Understanding Table Naming Conventions References from Certified System Administrator (CSA) Documentation:

Access Control Rules (ACLs)inServiceNowdeterminewho can access a record, table, or field. They are evaluated in aspecific orderto ensure security.
Table-Level ACLs are evaluated first
ServiceNowfirst checks if the user has permission to access the table itself.
If the user doesnothave access at thetable level, no further checks are performed.
Field-Level ACLs are evaluated next
Once table access is granted, ServiceNow checksif the user has permission to access individual fields.
More specific ACLs override broader ones(e.g.,incident.short_descriptiontakes priority overincident.*).
Order of Specificity (Most Specific to Least Specific)
Field-Specific ACL(incident.short_description.read)
Wildcard Field ACL(incident.*.read)
Table-Level ACL(incident.read)
Wildcard Table ACL(*.read)
ACL Evaluation Order in ServiceNow:This ensures thatspecific rules take precedence over general rulesfor enhanced security.
Example of ACL Evaluation in Incident Table:ACL Rule Type
Example ACL
Evaluation Order
Field-Specific
incident.short_description.read
First (Most Specific)
Wildcard Field
incident.*.read
Second
Table-Level
incident.read
Third
Wildcard Table
*.read
Last (Most General)
A: Field-level - most general to most specific; then Row-level - most specific to most generalIncorrect- Field- level ACLs arenot evaluated first; table-level ACLs are checked before field-level.
B: Table-level - most specific to most general; then Row-level - most specific to most generalIncorrect-"Row- level" is not a correct termin ServiceNow ACL processing.
D: Field-level - most specific to most general; then Table-level - most specific to most generalIncorrect-Table- level ACLs are always evaluated before field-level ACLs.
Incorrect Answer Choices Analysis:
ServiceNow Docs - Access Control Evaluation Order#How ACLs Are Processed ServiceNow Docs - Managing ACLs in ServiceNow#Best Practices for ACLs Official ServiceNow Documentation References:
Conclusion:The correct answer is:
C: Table-level - most specific to most general; then Field-level - most specific to most general Thisensures that general table permissions are granted before checking field-level access,following a structured and secure approachto access control in ServiceNow.

InServiceNow Knowledge Management, access towho can write articlesin aknowledge baseis controlled using the"Can Contribute"permission.
The"Can Contribute"tab allows administrators to specifywhich users or groups can create, edit, and manage knowledge articleswithin a specific knowledge base.
For example:
If a user isgranted "Can Contribute" access, they canwrite and editknowledge articles.
If a useronly has "Can Read" access, they canviewarticles butcannotcreate or modify them.
A). Can Read-Defines whocan viewknowledge articles, butnot who can writethem.
B). Can Write-No such tab exists in ServiceNow knowledge base settings. Instead, the correct term is"Can Contribute." D). Can Author-"Can Author" is not an official permission setting in ServiceNow. The correct term is"Can Contribute." E). Cannot Author-No such option exists in ServiceNow Knowledge Base permissions.
Reference:ServiceNow CSA Documentation - Knowledge Base Permissions
ServiceNow Product Documentation - Managing Knowledge Contributors(https://docs.servicenow.com)

Detailed Explanation:
In ServiceNow, users with the Impersonate role can impersonate other users to troubleshoot and validate user permissions and experiences. However,System Administratoraccounts cannot be impersonated to maintain security and prevent unintended administrative access. This restriction ensures that sensitive administrative functions are secure and can only be accessed directly. (Reference: ServiceNow Documentation - User Impersonation and Security Restrictions)

In ServiceNow, afilter conditionconsists of three primary components:
Field- The specific column (attribute) in a table that you want to filter by.
Example:State,Priority,Category,Created Date
Operator- Defines the comparison condition between theFieldand theValue.
Example:is, is not, contains, starts with, greater than, less than
Value- The actual data that the filter is looking for.
Example:High (for Priority), New (for State), IT Support (for Category) Example of a Filter Condition in ServiceNow:If you want to filter Incident records where theStateisNew, the filter condition would be:
Field:State
Operator:is
Value:New
A). Table-
A table is where data is stored, but it isnota component of a filter condition.
Filters are appliedona table but do not include the table itself in the condition.
ServiceNow Docs: Filtering Data in Lists and Reportshttps://docs.servicenow.com/en-US/bundle/utah- platform-user-interface/page/use/using-lists/concept/filtering-lists.html ServiceNow CSA Official Training Guide (Filtering and Searching Data) Why the Other Option is Incorrect?References from Certified System Administrator (CSA) Documentation:
This confirms thatField, Operator, and Valueare the three core components of a filter condition.