SNOW-CAD Creating and customizing tables and data — Timed 10 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?

10 minute time limit — choose an answer to begin.

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?

10 minute time limit — choose an answer to begin.

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.