B. Access Control Rules

Data Policies enforce data consistency rules but do not manage user access.

Access Control Rules (ACLs) determine who can access which records and fields based on roles, conditions, or scripts.

Business Rules automate logic on the server side but do not handle permissions.

UI Policies affect the form UI, not user access rights.

C. sys_user_grmember

sys_user_group stores group records, not memberships.

sys_user_role stores user-role assignments.

sys_user_grmember stores relationships between users and groups.

sys_group_member is not a valid table in the platform.

C. Update Sets

Cloning copies the entire instance, not just selected changes.

Import Sets are used to load external data, not configuration.

Update Sets capture and move configuration changes between instances.

IntegrationHub is used for outbound integrations and automation.

C. onLoad

onChange runs when a field value changes.

onSubmit runs when a user submits the form.

onLoad runs when the form is initially loaded in the browser.

onEdit is not a valid client script type.

B. To convert data from an import set into target table records

UI changes are unrelated to transform maps.

Transform maps define field mappings and transformation logic during data import.

Access restrictions are managed by ACLs, not transform maps.

Scheduling is handled by Scheduled Data Imports.

C. admin

• user_admin manages users and groups but not the full platform.
• itil is scoped to ITSM processes like Incident and Change.
• admin is the highest level role with unrestricted platform access.
• snc_platform_owner is not a standard role in the base platform.

C. Search and access modules and applications

User management is done through User Administration modules.

Flow Designer is used for building flows.

The Application Navigator is used to browse and search for applications and modules.

Activity streams are accessed through record forms.

C. A catalog item used to create records in a specific table

Variable sets are reusable groups of variables.

Flows are built in Flow Designer and are unrelated to catalog items.

Record Producers create records in a table like Incident or Change through the catalog.

UI Actions are buttons and links, not catalog items.

D. Form Sections

Field types define data types, not layout.

Dictionary overrides change field behavior in child tables.

UI Actions add buttons or links to forms.

Form Sections organize fields into logical groups on the form.

C. Schema Map

Flow Designer is used for building logic, not viewing table relationships.

Dictionary Entries define field attributes but do not show visual relationships.

Schema Map provides a graphical view of table relationships.

Update Set Viewer shows update records, not data structure.

C. Create Access Control Rules with role and condition-based logic

Access Control Rules (ACLs) are the primary mechanism in ServiceNow for controlling access to data at the record and field levels. In this scenario, the administrator needs to restrict creation of HR Case records to users with the hr_case_writer role and allow HR managers to read all records but only update those they own. ACLs support this use case by allowing conditions and scripts that can:
Check for specific roles (e.g., hr_case_writer for create access),
Evaluate record ownership (e.g., allow write access only if created_by == current user),
Differentiate between read and write permissions.
Other options, like UI Policies and Business Rules, manage form behavior and automation but do not enforce security. Data Policies ensure data consistency, not access control.

B. Use a Transform Map with field mappings and scripts if needed

Transform Maps are specifically designed in ServiceNow to map fields from an import set table to fields in a target table, such as sys_user. They allow administrators and developers to:

• Manually map mismatched field names (e.g., map email_address → email, login → user_name),
• Use transformation scripts to apply custom logic when necessary,
• Reuse and maintain mappings for recurring imports.

Modifying CSV headers (Option A) can be error-prone and not scalable. Data Policies (Option C) are meant to enforce field-level data rules, not perform field name translation. Re-entering data manually (Option D) is inefficient and defeats the purpose of using import sets.