SNOW-CAD Creating and customizing tables and data Practice Test 2 — 15 Questions

Question 1

A ServiceNow instance has a custom table 'u_staff' extended from the User table. A business rule on the 'User' table updates the 'Active' field. When updating a user record, the business rule does not fire for records in 'u_staff'. What is the most likely reason?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Business rules on the User table do not fire on child table records. Business rules on a parent table (User) do not automatically fire on child table records (u_staff) unless the business rule is configured to run on descendant tables. By default, business rules operate only on the table they are defined on. Option A is incorrect because permission is not the issue; the rule simply isn't triggered. Option C is incorrect because even without a specific condition, the rule won't fire on child tables. Option D is incorrect because ordering affects execution order, not whether the rule fires at all.

Answer

The user does not have permission to run business rules on the 'u_staff' table

Answer

The business rule has a condition that only allows running on User table records

Answer

The business rule ordering is set too low and is being skipped

Question 2

A company needs to create a lookup table to store status codes for incident classification. Which approach is best practice?

Accepted Answer

Use a Choice field with the status codes and labels. Using a Choice field is standard for static lists. Option A is wrong because creating a table is overkill for simple lists. Option C is wrong because it loses referential integrity. Option D is wrong because creating a custom table with a reference field on the Incident table adds unnecessary complexity when a simple Choice field suffices.

Answer

Create a new table using the Label field type

Answer

Store the status codes as a single line of text field

Answer

Create a custom table with a reference field on the Incident table

Question 3

An administrator notices that a custom table called 'u_equipment' does not appear in the 'New Record' context menu of the application navigator. What is the most likely cause?

Accepted Answer

The table was not added to an application menu in the navigation module. Custom tables must be added to an application menu in the navigation module to appear in the 'New Record' context menu. Option B is incorrect because tables extended from a parent table can appear independently if configured. Option C is incorrect because business rules do not affect navigator menu visibility; they only influence record creation actions. Option D is incorrect because the 'Create new' option is not inherited from the parent table; it requires explicit configuration.

Answer

The table is extended from a table that is not in the navigator

Answer

The table has a business rule that prevents new record creation

Answer

The 'Create new' option is inherited from the parent table

Question 4

When creating a custom table to extend an existing table, which TWO considerations should be evaluated to ensure optimal performance and maintainability? (Choose two.)

Accepted Answer

The number of records in the parent table may impact query performance when retrieving child records. Option D is correct because when a custom table extends a parent table, queries that retrieve child records typically join or reference the parent, so a large parent table (many records) can slow those queries and must be evaluated for performance. Option E is correct because each additional field on the extended table increases the row width, index/storage overhead, and form/query complexity, so adding too many fields degrades performance and maintainability. Option A is not required: while custom table names often follow naming conventions like a prefix, a 'u_' prefix is not a universal technical requirement for extending a table. Option B is not required: creating the table in a global scope is not a standard requirement for extending an existing table and does not by itself ensure access or performance. Option C is not required: a reference field back to the parent is not mandatory for a table extension, since the extension relationship is defined by the table hierarchy, not by an explicit reference field.

Answer

The table must have a unique name starting with 'u_'

Answer

The table should be created in the global scope to ensure universal access

Answer

The table must have a reference field back to the parent table

Question 5

An administrator is designing a data model to manage vendor contracts. The solution must allow contracts to be associated with multiple departments and multiple vendors. Which THREE approaches are valid to model this many-to-many relationship in ServiceNow? (Choose three.)

Accepted Answer

Create an intermediate table 'ContractDepartment' with reference fields to Contract and Department. Option A is correct because creating an intermediate (junction) table such as 'ContractDepartment' with reference fields to both Contract and Department is the canonical relational way to model a many-to-many relationship in ServiceNow, allowing one contract to link to many departments and vice versa. Option C is correct because a GlideList field on the Contract table stores a delimited list of references to multiple Department records in a single field, which ServiceNow supports for representing multiple related records. Option D is correct because a Multi-reference field (sys_multi_reference) is specifically designed to reference multiple records from another table, such as multiple departments from a Contract record. Option B is not correct because a single reference field can only point to one department record, so it cannot represent multiple departments. Option E is not correct because storing comma-separated sys_ids in a String field is a manual, non-relational workaround that breaks referential integrity and does not leverage ServiceNow's reference or multi-reference capabilities.

Answer

Create a single 'Department' field on the Contract table and use it to store all department records

Answer

Use a 'String' field on the Contract table to store a comma-separated list of department sys_ids

Question 6

A company uses an import set to bring in hardware asset data from an external inventory system. The staging table 'u_hardware_staging' maps fields to the 'alm_hardware' table via a transform map. Recently, the import set started failing with the error 'Invalid reference field value: 'PO123' for field 'purchase_order''. The 'purchase_order' field on 'alm_hardware' is a reference to the 'purchase_order' table, and the staging field contains the purchase order number (e.g., 'PO123'). The transform map has a field map that uses the 'Find' and 'Map' functionality to match the purchase order number. The 'purchase_order' table uses the 'number' field as the display value. Which change should the administrator make to fix the error?

Accepted Answer

In the transform map, enable 'Find map for each record' and set the match field to 'number' on the purchase_order table. The error occurs because the transform map's 'Find' and 'Map' field map is trying to resolve the reference by matching the staging value 'PO123' against the purchase_order table's sys_id (the default reference target) rather than its number field. Enabling 'Find map for each record' and setting the match field to 'number' tells the transform to look up the purchase_order record by its number value, producing a valid sys_id for the reference field.

Answer

Modify the staging table to include the sys_id of the purchase order instead of the number

Answer

Change the field map to use 'Direct' instead of 'Find' and 'Map'

Answer

Create a database view between the staging table and the purchase_order table to auto-populate the reference

Question 7

A ServiceNow administrator is responsible for setting up a custom table called 'u_incident_change' to track incidents that require a change request. Each 'u_incident_change' record must be linked to exactly one incident and one change request. The administrator creates two reference fields: 'incident_ref' pointing to the 'Incident' table, and 'change_ref' pointing to the 'Change Request' table. However, after deployment, users report that when they create a new 'u_incident_change' record from an incident form (using a related list), the 'incident_ref' field is automatically populated, but the 'change_ref' field is empty. The users want to be able to create a change request directly from that same form and have the reference automatically filled. What configuration should the administrator use to achieve this?

Accepted Answer

Create a UI Action labeled 'Create Change Request' on the incident form that runs a script to create a new 'u_incident_change' record with both references populated and then opens the change request form. A UI Action on the incident form can run a script that creates the u_incident_change record with incident_ref set to the current incident, opens a new change request form, and on submit populates change_ref, then links the two. This is the only option that provides the interactive flow users need to create a change request directly from the incident form and have both references populated. It matches ServiceNow's standard pattern for cross-table creation from a form.

Answer

Configure the related list to automatically create the 'u_incident_change' record with both references when a change request is added

Answer

Use a business rule on the 'u_incident_change' table that auto-populates the 'change_ref' when the record is created from a related list

Answer

Add a reference field on the Incident table that points to the 'u_incident_change' table

Question 8

A small business uses ServiceNow to manage IT assets. They have a custom table 'u_company_asset' with fields for asset name, serial number, purchase date, and a reference field 'assigned_to' pointing to the User table. The administrator is asked to add a new field called 'Category' that will contain a short list of categories: Desktop, Laptop, Server, Network. The categories will not change frequently. The administrator also needs to ensure that when a user selects a category, a corresponding icon appears next to the field in the form. What is the most efficient way to accomplish this?

Accepted Answer

Create a Choice field with the four categories, and then configure a UI policy to show different icons based on the selected value. A Choice field provides a drop-down list for predefined values that rarely change, and a UI policy can be configured to display different icons based on the selected category. Option A is wrong because a List Collector is used for multiple selections, not a single category. Option C is wrong because creating a custom table is unnecessary overhead for a fixed list. Option D is wrong because a single-line text field does not enforce predefined values.

Answer

Use a List Collector field to allow multiple categories

Answer

Create a custom table 'u_category' and a reference field on 'u_company_asset' pointing to it

Answer

Use a single-line text field and manually enter the categories

Question 9

A developer encounters the following error when a scheduled job executes. The job queries the 'u_my_table' table. What is the most likely cause?

Accepted Answer

The field u_extra_field was recently deleted from the table.. The error occurs because the scheduled job references the field 'u_extra_field' in its query against the 'u_my_table' table. When that field is deleted from the table definition, any script or job that attempts to read or write to that field will fail with a 'column not found' or similar database error. This is the most direct cause among the options, as the job was previously working and the error appeared after a schema change.

Answer

The table name is misspelled in the script.

Answer

The script include has a syntax error.

Answer

The field u_extra_field exists but is not indexed.

Question 10

A developer creates a custom table named 'u_support_case' that does not extend any existing table. Users report that they can open records but cannot attach files or post comments to a case. Which configuration change will enable these collaboration features with the least administrative effort?

Accepted Answer

Re-create u_support_case as a table that extends the Task table and migrate the existing records.. Extending the Task table is the standard way to give a custom table the same collaboration features that task-based records have. Because attachments, comments, and the activity stream are provided through the task hierarchy, the custom table inherits them automatically. This avoids building custom fields or related lists and keeps the data model consistent with other task-like records.

Answer

Create new attachment and comment fields on u_support_case and add them to the form layout.

Answer

Add a many-to-many related list between u_support_case and the Attachments table on the form.

Answer

Enable the 'Enable attachments' and 'Enable comments' system properties globally for all custom tables.

Question 11

A developer creates a custom table 'u_contract' in a scoped application. The table has a reference field 'u_vendor' that points to the Vendor [u_vendor] table, which is in a different scope. Users report that the vendor field sometimes displays a raw sys_id instead of the vendor name. What is the most likely cause?

Accepted Answer

The u_vendor table does not have a display value defined, so the reference field falls back to the sys_id.. A reference field renders the display value of the referenced record. When the target table has no display value configured, ServiceNow falls back to the sys_id. Setting a meaningful display value on the Vendor table, such as the vendor name, corrects the raw sys_id display for all references to that table.

Answer

The reference field was created with the wrong reference qualifier, which forces sys_id display.

Answer

Cross-scope access to the Vendor table is blocked, so the reference field cannot resolve the display value.

Answer

The Vendor table uses a sys_id as its display value by default, and no other field has been promoted.

Question 12

A developer is configuring a custom table 'u_support_case' and needs to ensure that when a case is created, the 'opened_at' field is automatically set to the current date and time. The developer wants this to happen without any user interaction and without writing a business rule. Which table configuration should the developer use?

Accepted Answer

Set the 'opened_at' field's Default value to 'javascript:gs.nowDateTime()'.. Setting a JavaScript default value of gs.nowDateTime() on the field dictionary automatically populates the field with the current date and time on insert, regardless of how the record is created. This is a server-side, declarative approach that requires no user interaction or business rule. The other options either do not exist, only affect the form, or are less direct for this specific requirement.

Answer

Create a UI Policy that sets the 'opened_at' field to the current date and time on form load.

Answer

Set the 'opened_at' field's Default value to 'javascript:gs.now()'.

Answer

Enable the 'Auto-set' attribute on the 'opened_at' field.

Question 13

A developer is creating a new custom table 'u_book' and wants to ensure that every record has a unique identifier that is automatically generated and displayed in a human-readable format. Which field should the developer configure as the table's display value?

Accepted Answer

String field named 'title'. The display value is the field that represents a record in lists, references, and other UI elements. A String field named 'title' provides a human-readable name that uniquely identifies the book in most cases. While the Number field can generate unique numbers, it is not typically the display value; the sys_id is not human-readable, and the Created field is not unique. Therefore, the 'title' field is the best choice.

Answer

Number field

Answer

Created field

Answer

Sys_id field

Question 14

A developer is creating a new custom table 'u_equipment_checkout' to track equipment loans. The table must store a checkout date, a due date, and a reference to the equipment item. The developer wants to ensure that the due date automatically defaults to seven days after the checkout date when a new record is created. Which two approaches are valid for setting this default? (Choose two.)

Accepted Answer

Create a before insert business rule that sets the due date based on the checkout date.. A before insert business rule runs server-side before saving, so it can calculate the due date from the checkout date and set it on the record. A dictionary default value script is also a valid server-side mechanism that can set the due date when the record is created. Both approaches work for all record creation paths, unlike client-side or after-update options.

Answer

Add a UI policy that sets the due date field to read-only and calculates its value.

Answer

Create an onLoad client script that sets the due date when the form opens.

Answer

Create an after update business rule that sets the due date after the record is saved.

Question 15

A developer needs to create a custom table that extends the Task [task] table. The developer wants to add a new field that should be visible on the form and list, and must be able to be set via a business rule. Which two actions should the developer perform? (Choose two.)

Accepted Answer

Add the field to the form layout using the Form Designer.. To add a new field to a custom table that extends Task, the developer must first create the field on the custom table via the Dictionary. Then, to make it visible on the form, the field must be added to the form layout using the Form Designer. These two actions ensure the field exists and is accessible on the form. Adding to the list layout is also useful but not one of the two primary actions for form visibility.

Answer

Create a new field on the parent Task table.

Answer

Add the field to the list layout using the List Designer.

Answer

Create a new table that extends the custom table.