In ServiceNow,Tagsallow users tocategorize and grouprecords in a list. Tagged records arevisible to othersif set to public or shared with specific users or groups.
A: Tags
Tags help usersorganize and quickly locaterecords.
Tags can beprivate (Me)orshared (Everyone, Groups, or Specific Users).
Example:
A support team might tagcritical incidentswith "Urgent" for easy tracking.
B: History
TheHistorymodule showsrecently accessed recordsbut does not categorize or share records.
C: Favorites
Favoritesallow users tobookmark specific records or listsfor quick access, but they areprivateand not shared with others.
D: Activity Formatter
TheActivity Formattertrackschanges and updatesin a record (e.g., who modified the record, comments added), but it does notcategorize or sharerecords.
References:ServiceNow Documentation:Using Tags in Lists
ServiceNow User Guide:Managing and Sharing Tags

InServiceNow Access Control Rules (ACLs), if an administrator wants to grant access toall rows and all fieldsof a custom table (e.g.,customertable) to specific roles (customer_table_adminandcustomer_table_user), they should create an ACL rule using theformat:
##tablename.*
For theCustomer Table, the correct ACL format is:
##customer.*
This rule allows bothcustomer_table_adminandcustomer_table_userfull accessto all fields and records in thecustomertable.
A). customer.all
Incorrect syntax; ServiceNow does not use.allin ACL rules.
C). customer.field
This would applyonly to a specific field, not all rows and fields.
D). customer.none
No such ACL naming convention exists in ServiceNow.
Reference:ServiceNow CSA Documentation - Creating and Managing ACL Rules ServiceNow Product Documentation - Table-Level and Field-Level ACLs(https://docs.servicenow.com)

In ServiceNow,Table Access Control (ACL) rulesdefine the permissions for accessing records within a table.
When a user attempts to access a record, ServiceNow processesACL rules in a specific orderto determine if the user has the necessary permissions.
Specific Table Name ACLs
ServiceNowfirst checks ACL rulesthat are defined for the exact table being accessed.
If there are multiple ACL rules for the same table, ServiceNow evaluates themfrom most specific to least specific(i.e., field-level ACLs before table-level ACLs).
Parent Table Name ACLs(If applicable)
If the table inherits from another table (e.g.,Incident inherits from Task), ServiceNownext checks ACL ruleson theparent table.
This ensures that inherited rules are properly applied.
Wildcard ACLs (*)(Any table)
If no explicit ACL rule is found for the table or its parent, ServiceNow checkswildcard ACL rules (*), which apply toall tables.
Wildcard ACLs act as alast resortwhen no table-specific rules exist.
Order of Processing ACL Rules:
(A) any table name (wildcard), parent table name, table name - Incorrect Wildcard rules (*) areprocessed last, not first.
(B) table name, parent table name, any table name (wildcard) - Correct
This follows the correctprocessing order:
First:ACLs for the specific table
Second:ACLs for the parent table (if applicable)
Third:Wildcard ACLs (*)
(C) parent table name, table name, any table name (wildcard) - Incorrect Parent table ACLs arechecked aftertable-specific ACLs, not before.
(D) any table name (wildcard), table name, parent table name - Incorrect Wildcard ACLs (*) arealways processed last, so this order is incorrect.
Explanation of Each Option:
Field-level ACLs(column-specific) take precedence overtable-level ACLs.
If multiple ACL rules apply,all must evaluate totruefor access to be granted.
Explicit Deny:If an ACL rule explicitlydenies access, the user is denied, even if another ACL grants access.
Always Test ACLs:Use the "Security Debugging" feature (/sys_security_acl_list.do) to verify how ACLs are applied.
Additional Notes & Best Practices:
ServiceNow Docs: How Access Control Rules Work
https://docs.servicenow.com
ServiceNow Community: Understanding ACL Processing Order
https://community.servicenow.com
References from Certified System Administrator (CSA) Documentation:

In ServiceNowKnowledge Management, access to knowledge articles is controlled through access settings in theKnowledge Baserecord. The"Can Read"tab is used to specify which users, groups, or roles canview knowledge articlesin a particular Knowledge Base.
#Why "Can Read"?
TheCan Readlist defines theusers, groups, or roles that can access and view articlesin a specific Knowledge Base.
This ensures thatsensitive or restricted knowledge is only available to authorized users.
If no restrictions are set in theCan Readtab, the knowledge base ispublicly accessibleto all users.
#Steps to Configure "Can Read" Permissions:
Navigate toKnowledge Management > Knowledge Bases.
Open a specificKnowledge Base record.
Go to theCan Readtab.
Add the users, groups, or roles that should be able to read the articles.
Save the record.
#Incorrect Options Explained:
A). Access List- No such tab exists in Knowledge Management.
B). Can Access- Incorrect name; the correct tab isCan Read.
C). Accessible to- Does not exist in the Knowledge Base settings.
#Reference:
ServiceNow Knowledge Management User Roles
Managing Knowledge Base Access