SNOW-CAD Creating and customizing tables and data — 25 Questions

Question 1

A developer needs to create a new table to store custom survey responses. The table should have a field to store the survey name and a field to store the response text. The developer wants to ensure that the table is available in the 'Surveys' application module. Which property must be set on the table?

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

Accepted Answer

Application module. The Application module property determines which application module a table belongs to, making it visible and accessible within that module's scope. Setting this to 'Surveys' ensures the table appears in the Surveys application module, as required by the developer.

Answer

Application scope

Answer

Table name

Answer

Table label

Question 2

A developer needs to create a new table to store custom survey responses. The table should have a field to store the survey name and a field to store the response text. The developer wants to ensure that the table is available in the 'Surveys' application module. Which property must be set on the table?

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

Accepted Answer

Extend the 'task' table. Extending the 'task' table allows the new table to inherit the assignment and state fields required by the 'task' model. This is the standard approach in ServiceNow for creating tables that leverage task-related functionality, such as assignments and workflow states.

Answer

Set the 'table' access policy to 'Internal'

Answer

Extend the 'incident' table instead of 'task'

Answer

Enable the 'Allow web service access' property on the table

Question 3

A developer created the business rule shown in the exhibit to auto-generate asset tags. However, when a new asset is created, sometimes the generated tag is a duplicate of an existing tag. What is the most likely cause?

Accepted Answer

The query uses 'CONTAINS' which may match unintended tags, and ordering by sys_created_on may not guarantee the highest number. The script uses a glide query with 'CONTAINS' to find the highest existing asset tag number, which can match unintended tags (e.g., 'TAG-10' matching 'TAG-1001'), and ordering by 'sys_created_on' does not guarantee the highest numeric suffix. This leads to duplicate tags when the generated number is already in use but not detected as the maximum.

Answer

The condition '!current.u_asset_tag' fails when the field is empty

Answer

The script does not account for records with null asset tags

Answer

The script does not handle the scenario when no asset tag exists

Question 4

You are a ServiceNow developer at a large healthcare organization. You have created a custom table 'u_medical_device' to track medical equipment. The table has fields: 'u_device_id' (string), 'u_device_type' (choice: 'Monitor', 'Ventilator', 'Pump'), 'u_location' (reference to 'u_location' table), 'u_status' (choice: 'Active', 'Inactive', 'Maintenance'), and 'u_last_calibration_date' (date). You need to implement a business rule that, when a device's status is changed to 'Maintenance', automatically sets the 'u_last_calibration_date' to the current date and creates a 'u_maintenance_log' record with a reference to the device. Additionally, you want to ensure that only users with the 'medical_device_admin' role can change the status to 'Maintenance'. You have written the business rule but it is not firing correctly. The sys_script table shows the rule is active, order 100, when 'before' query and 'after' update. The condition is: current.status.changes() && current.status == 'Maintenance'. The script sets current.u_last_calibration_date = gs.now(); and creates a GlideRecord for u_maintenance_log. However, the calibration date is not updated, and no log record is created. What is the most likely cause?

Accepted Answer

The business rule is set to run 'before' query instead of 'before' update or 'after' update.. The correct answer is B: the business rule is set to run 'before' query instead of 'before' update or 'after' update. In ServiceNow, a business rule's 'when' field must be set to 'before' or 'after' with the appropriate operation (insert, update, delete, query); a rule configured for 'before query' only fires when records are queried, not when a record is updated, so the script that sets current.u_last_calibration_date and creates the u_maintenance_log GlideRecord never executes during the status change. Option A is incorrect because gs.now() returns a GlideDateTime that ServiceNow can coerce into a date field, and it would not cause a silent failure of the entire rule. Option C is incorrect because role restrictions are enforced via ACLs, not by the business rule itself, and a missing role would block the update rather than silently skip the rule logic. Option D is incorrect because current.status.changes() returns a boolean and combining it with == in an AND condition is valid JavaScript and standard ServiceNow practice.

Answer

The script uses 'gs.now()' which returns a date-time string, but 'u_last_calibration_date' is a date field, causing a type mismatch and silent failure.

Answer

The user executing the update does not have the 'medical_device_admin' role, and the business rule lacks an ACL check.

Answer

The condition 'current.status.changes() && current.status == 'Maintenance'' is invalid because 'changes()' returns a boolean and cannot be combined with '=='.

Question 5

A developer is creating a new table 'u_incident_custom' to extend the Incident table. Which TWO configurations will ensure that the new table inherits the correct behavior and displays in the application navigator?

Accepted Answer

Set 'Application' to the desired scope and check 'Display in application navigator'. Option D is correct because setting the 'Extends' field to 'Incident' makes u_incident_custom a child table of Incident, so it inherits Incident's fields, business rules, UI policies, ACLs, and other behavior through table extension. Option A is correct because setting 'Application' to the desired scope places the table in the proper application scope, and checking 'Display in application navigator' ensures the table appears in the application navigator for that scope. Option B is not required because creating a module is a separate navigation customization, not a table configuration that makes the table inherit behavior or appear in the navigator. Option C is incorrect because the Label is only a display name and does not affect inheritance or navigator visibility. Option E is incorrect because extending 'Task' would make the table inherit Task behavior rather than Incident behavior, which does not meet the requirement.

Answer

Create a module pointing to the new table

Answer

Set 'Label' to 'Incident Custom'

Answer

Set 'Extends' to 'Task'

Question 6

A custom table 'u_incident' has a 'priority' field that should be set to 1 when the 'category' is 'Critical', otherwise 3. Which is the most efficient way to implement this default?

Accepted Answer

Define a default value script in the dictionary for the priority field. A dictionary default value script runs server-side whenever a new record is created without an explicitly provided value, making it the most efficient and centralized way to set a conditional default. It avoids the overhead of a Business Rule execution on every insert and keeps the logic attached to the field definition itself. This is the ServiceNow-recommended pattern for simple default-value logic.

Answer

Create a Business Rule on 'Before Insert' that sets the priority

Answer

Create a Client Script that runs onLoad and sets priority

Answer

Use a UI Policy to set priority based on category

Question 7

Which TWO are required for a reference field to automatically filter its choices based on the value of another field on the form (cascading)?

Accepted Answer

The reference qualifier must be a script that uses the parent field's value. Option B is correct because a cascading reference field works by applying a reference qualifier (a dynamic filter, typically written as a script or using a qualifier with a variable) that reads the current value of the parent field and uses it to constrain the lookup results. Option E is correct because for the dependent reference field to filter based on another field's value, both the parent field supplying the value and the reference field being filtered must be present on the same form so the qualifier can access the parent value at runtime. Option A is not required because the parent field does not have to be a reference field; it can be any field type (for example, a choice or string field) whose value is used in the qualifier. Option C is not required as a separate condition because the qualifier can reference values from the current record even when fields are arranged across different form sections or views, and the essential requirement is that the parent value is available, not merely co-location. Option D is not required because the reference table does not need a field with the same name as the parent field; the qualifier script explicitly maps the parent value to the appropriate field on the reference table.

Answer

The dependent field (parent) must be a reference field

Answer

Both fields must be on the same form

Answer

The reference table must have a field with the same name as the parent field

Question 8

Which THREE are benefits of extending a table rather than creating a new table from scratch?

Accepted Answer

Supports creating multiple child tables from the same parent. Option B is correct because table extension allows a single parent table to serve as the base for many child tables, each inheriting the parent's schema while remaining distinct, which is a core benefit of the extension model. Option C is correct because extending a table automatically carries over all fields and relationships defined on the parent, so the child table starts with the full parent data model without manual re-creation. Option E is correct because the child table can define its own additional fields on top of the inherited ones, and these new fields exist only on the child, leaving the parent table unchanged. Option A is not marked correct because inheritance of business rules and client scripts is not the defining benefit described here and is not guaranteed in the same way as field and relationship inheritance. Option D is not marked correct because child records do not automatically appear in parent-table reports; reporting on parent data does not inherently include child records unless explicitly configured.

Answer

Automatically inherits all business rules and client scripts from the parent

Answer

Child records automatically appear in reports on the parent table

Question 9

Refer to the exhibit. A developer created this dictionary override for a new field. When saving, an error occurs. What is the cause?

Accepted Answer

Integer fields do not support the max_length property. In ServiceNow dictionary overrides, the max_length attribute is only valid for string-type fields (string, translated_text, etc.). Integer fields store numeric values and their size is governed by the underlying database column type, so specifying max_length on an integer field causes the dictionary save to fail validation. Removing max_length (or converting the field to a string type) resolves the error.

Answer

The label 'Custom Count' contains spaces

Answer

internal_type should be 'integer' not 'integer' (typo)

Answer

The JSON properties must be in alphabetical order

Question 10

A developer creates a new custom table 'u_ticket' by extending the 'Task' table. Which field will be automatically inherited from the Task table?

Accepted Answer

State. When a custom table extends the Task table, it automatically inherits all fields from the Task table, including State, Number, Assignment group, and Short description. Therefore, every option listed is a field that is automatically inherited.

Question 11

A developer notices that a custom table 'u_project' is not appearing in the 'Create New' menu even though the application scope is set correctly. The table has been created with the 'Create without application' flag unchecked. What is the most likely cause?

Accepted Answer

The 'Create new record' property is set to false.. The 'Create new record' property on a table controls whether users can create records directly from the 'Create New' menu in the ServiceNow UI. When this property is set to false, the table is hidden from the Create New menu even if the application scope is correct and the table is extensible. This is a UI-level access control, not a security or scope issue.

Answer

The 'Extensible' property is set to false.

Answer

The 'Allow Configuration' property is set to false.

Answer

The table's roles are not assigned to the developer.

Question 12

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 13

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'.. Option B is correct because ServiceNow's Import Set functionality includes a 'Create table automatically' option that generates a new table (with columns mapped from the CSV fields) during the import process, making it a legitimate way to create a custom table. Option D is correct because the 'Create Table' module under System Definition is the standard, supported UI path for defining a new custom table, where you specify the table label, name, and extend options. Option A is incorrect because client scripts run in the browser and cannot create database tables; table creation requires server-side schema operations. Option C is incorrect because directly inserting into sys_db_object bypasses the proper table-creation APIs and does not create the required dictionary entries, so it is not a valid supported method. Option E is incorrect because a database view is a read-only join of existing tables and cannot be used as the basis for creating a new 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 14

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

Accepted Answer

Mandatory. In ServiceNow, dictionary entries control field-level behavior, and three attributes that directly affect how a field behaves are Mandatory (B), Default value (C), and Calculated (D). Mandatory (B) forces a value to be entered before a record can be saved, enforcing data completeness at the field level. Default value (C) pre-populates the field with a specified value when a new record is created, controlling the field's initial content. Calculated (D) makes the field's value derive automatically from a calculation or script rather than user input, changing how the field is populated. Display (A) is not a dictionary attribute that governs field behavior, and Reference qualifier (E) is a related but distinct setting applied to reference fields rather than one of these three core behavioral attributes.

Answer

Display

Answer

Reference qualifier

Question 15

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 16

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 17

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 18

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 19

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 20

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