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

Question 1

Which table property can be set to limit the creation of new records to certain roles?

Accepted Answer

Create access. The 'Create access' property on a table specifies which roles are allowed to create new records. Option A is incorrect: 'Allow attachment' controls whether users can add attachments to records, not creation. Option B is incorrect: 'Abbreviated table' sets a short name or prefix for the table, not access control. Option D is incorrect: 'Effective access' is a read-only property showing the user's current access rights, not a setting to restrict creation.

Answer

Allow attachment

Answer

Abbreviated table

Answer

Effective access

Question 2

A developer creates a scheduled job that updates a custom table's records. The job runs successfully but the table's 'Updated' field does not reflect the correct time. What could be the reason?

Accepted Answer

The script used 'setWorkflow(false)' which bypasses the auto-update of the 'Updated' field.. The 'Updated' field is set automatically when a record is updated through the UI, but if the update is done via direct database update (e.g., using GlideRecord without setWorkflow(true)), the system might not update the field. Also, conditional or dirty flag may not set. However, the most likely is that the update script used setWorkflow(false) or bypassed the auto-update mechanism. Option A is wrong because performance of the job is not related. Option C is wrong because Access controls do not affect system fields like 'Updated'. Option D is wrong because the job's schedule time is irrelevant.

Answer

The scheduled job's schedule interval is longer than the update frequency.

Answer

The table does not have the appropriate record-level ACLs.

Answer

The scheduled job runs too fast for the system to record the update.

Question 3

Which TWO of the following are valid methods to create a custom table in ServiceNow?

Accepted Answer

Importing a CSV file via Import Set and selecting 'Create table automatically'.. Correct: B and D. Option B is valid because importing a CSV via an Import Set with the 'Create table automatically' option generates a new table based on the data structure. Option D is valid because the 'Create Table' module in System Definition provides a standard UI to create custom tables. Incorrect options: A is wrong because client scripts run in the browser and cannot create database tables. C is wrong because directly inserting into 'sys_db_object' bypasses required table creation processes and is not supported. E is wrong because a database view is a virtual representation of data from existing tables, not a physical table.

Answer

Using a client script to create a table on the fly.

Answer

By updating the 'sys_db_object' table directly with a new entry.

Answer

Using a database view to combine existing tables and then creating a table from the view.

Question 4

Which THREE of the following attributes can be set on a dictionary entry to affect how a field behaves?

Accepted Answer

Mandatory. Options B, C, and D are correct dictionary attributes that affect field behavior. 'Mandatory' (B) forces the field to be required. 'Default value' (C) sets an initial value for the field. 'Calculated' (D) enables a scripted calculated value, directly affecting how the field's value is determined. Option A ('Display') is a dictionary attribute that primarily controls which field to display in a reference field, not directly affecting field behavior. Option E ('Reference qualifier') is also a dictionary attribute, but it filters the records shown in a reference field, affecting record selection rather than the field's own behavior.

Answer

Display

Answer

Reference qualifier

Question 5

Which TWO of the following are valid table types in ServiceNow?

Accepted Answer

Extendible. Options D and E are correct. 'Extendible' (tables that can be extended) and 'Database view' (virtual tables based on SQL views) are valid table types in ServiceNow. Option A is incorrect because 'Dictionary' is a table that stores system metadata, not a table type. Option B is incorrect because 'Application' is not a table type; applications contain tables. Option C is incorrect because 'UI page' is a UI component, not a table type.

Answer

Dictionary

Answer

Application

Answer

UI page

Question 6

An administrator needs to create a custom table to store project-related information. The table must allow records to be assigned to a specific user. Which field type should be used for the assignment field to ensure proper integration with ServiceNow's assignment rules and notifications?

Accepted Answer

Reference to the User table. Reference to the User table. To assign a record to a specific user, a reference field pointing to the User table is appropriate. ServiceNow's assignment rules and notifications can be configured to trigger based on changes to this user reference field, ensuring proper integration. Option D (Assignment group) assigns to a group, not an individual, so it does not meet the requirement.

Answer

Manager

Answer

Integer

Answer

Assignment group

Question 7

A developer writes a script to display the department name of the caller on a custom form. The script uses: gs.getUser().getDepartment().getName(). However, the script throws a null pointer exception for some users. Which is the most likely cause and solution?

Accepted Answer

Some users do not have a department assigned, and the script does not check for null. The NullPointerException suggests that getDepartment() returned null for users without a department. Option A is wrong because the script is syntactically correct. Option B is wrong because reference exists. Option C is wrong because department records exist.

Answer

The Department table is empty

Answer

The script uses incorrect dot-walking syntax; use getValue('department') instead

Answer

The user table does not have a department reference field

Question 8

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?

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 9

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 10

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 11

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. Options D and E are correct. When extending a table, the number of records in the parent table can impact query performance when retrieving child records because child tables inherit the parent table's data, and queries may need to scan the parent table as well. Adding too many fields to an extended table can degrade performance (more data to store and process) and increase complexity (harder to maintain relationships and ACLs). Option A is incorrect because while ServiceNow suggests a naming convention with 'u_' for custom tables, it is not a strict requirement for performance or maintainability. Option B is incorrect because the table should be created in the same scope as the application it belongs to, not necessarily global scope. Option C is incorrect because a reference field back to the parent table is not required; the table extension itself establishes the relationship via inheritance.

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 12

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. Options A, C, and D are valid approaches for modeling a many-to-many relationship in ServiceNow. Option A creates an intermediate table with reference fields, which is a standard relational method. Option C uses a GlideList field, which allows storing multiple references in a single field and can be used for many-to-many relationships. Option D uses a multi-reference field, which is specifically designed for many-to-many relationships. Option B is invalid because a single 'Department' field cannot store multiple records. Option E is invalid because storing comma-separated sys_ids in a String field is not a recommended practice and breaks data integrity.

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 13

A large enterprise runs a ServiceNow instance with a heavily customized Task table. The 'Task' table has been extended to create 'u_WorkOrder', which is used by over 50,000 active records. Recently, users complain that when they open a WorkOrder record, the form takes more than 10 seconds to load. On investigation, you discover that the 'u_WorkOrder' table has 150 fields, many of which are UI policies and client scripts that trigger on load. Additionally, there is a business rule that runs 'after query' and dot-walks through multiple related tables (e.g., calling 'current.assigned_to.department.manager.email' in a loop for each record). The instance uses SQL Server as its database. Which action would most effectively reduce the form load time without losing required functionality?

Accepted Answer

Rewrite the after query business rule to use GlideAggregate or avoid dot-walking in loops, and consider caching the dot-walked data. The most effective because it directly addresses the root cause: the after query business rule performing expensive dot-walking for every record. Rewriting it to use GlideAggregate or caching the dot-walked data will significantly reduce query time. Option A is wrong because changing the order of the business rule does not reduce its workload; it still runs after query. Option C is wrong because removing fields may cause loss of required functionality and does not target the primary performance issue (the business rule). Option D is wrong because converting to after update changes the trigger but does not solve the load-time problem; form load is a query action, not an update.

Answer

Change the order of the business rule to 100 so that it runs after other rules

Answer

Remove 50 of the 150 fields from the table to reduce data retrieval

Answer

Convert the after query business rule to an after update business rule

Question 14

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 transform map needs to find the purchase order record by its 'number' field (display value). Enabling 'Find map for each record' and setting the match field to 'number' on the purchase_order table allows the transform to resolve the reference. Option B is incorrect because the staging table should contain the number, not the sys_id, as the import source provides readable values. Option C is incorrect because using 'Direct' would attempt to set the reference field with the number string, which is invalid. Option D is incorrect because database views do not apply to transform mappings.

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 15

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 with a script creates the change request and sets the reference fields accordingly. Option B is wrong because referenced records don't auto-populate. Option C is wrong because business rules run on records, not UI. Option D is wrong because related lists don't create records with cross-reference.

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