SNOW-CSA Flashcards — Free ServiceNow Certified System Administrator CSA Study Cards

Create a transform map that maps the source field to the target field, and use a field mapping script to convert the department name to the correct sys_id.

Option B is correct because Import Set Rows are processed through transform maps, which allow field mapping scripts to convert source values (like 'Human Resources') into the corresponding sys_id in the Department [cmn_department] table. This is the standard, supported approach for handling reference field lookups during imports, ensuring data integrity without manual intervention or post-insert processing.

Record Producer

A Record Producer is the correct self-service feature because it allows users to submit requests for new software through a catalog item without any manual intervention. It automatically creates a record (e.g., a catalog task or request) in the platform based on the user's submission, enabling a fully automated request process.

Enable personalization on the form

Personalization allows individual users to add fields to a form without affecting the form layout for all users. By enabling personalization on the incident form, the system administrator grants end users the ability to add the 'Mobile Phone' field to their own view of the form, which is stored per user in the sys_user_preference table.

The CI is classified under a different CI class in the CMDB.

When a CI is classified under a different CI class in the CMDB, the scheduled discovery job may not update it because discovery uses the IRE to match incoming data against existing CIs based on identification rules. If the CI's class differs from what the discovery payload expects, the IRE may fail to reconcile the record, or the update may be directed to a different class table, leaving the original CI unchanged. This is a common cause of apparent update failures when the CI is reachable and the discovery source is correctly configured.

Create an Approval rule with conditions on cost and department budget.

Option D is correct because Approval rules in ServiceNow are specifically designed to automate approval decisions based on conditions like cost and department budget. By creating an Approval rule on the catalog item, you can evaluate the requested cost against a threshold and check the department's budget balance via a condition script or reference to the budget table, enabling automatic approval without manual intervention.

The business rule is running on 'before query' instead of 'before insert'.

The business rule is configured to run on the 'before query' operation, which means it executes every time a query is made against the 'u_employee_data' table. This causes the condition to set the 'u_department' field to 'Engineering' for all records returned by the query, effectively filtering the result set to only those with that department. The intended behavior is to set the default department only when a new record is created, which requires the business rule to run on the 'before insert' operation instead.