How should I use these Creating and customizing tables and data practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

SNOW-CAD · topic practice

Creating and customizing tables and data practice questions

Q: Can I practise just Creating and customizing tables and data questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Creating and customizing tables and data domain.

Practise ServiceNow Certified Application Developer CAD Creating and customizing tables and data practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: Creating and customizing tables and data

Practice 10 questions Browse domain →

What the exam tests

What to know about Creating and customizing tables and data

Creating and customizing tables and data questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Creating and customizing tables and data exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Creating and customizing tables and data questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Creating and customizing tables and data explanation →

A developer is creating a custom table for tracking hardware assets. The table must have fields for asset tag, serial number, and purchase date. The developer wants to ensure that the asset tag is automatically generated using a prefix followed by an incrementing number. Which approach should the developer use?

Trap 1: Use a calculated value that dot-walks to a number table

Dot-walking is for referencing related record fields.

Trap 2: Set the default value of the asset tag field to 'AST-' + sys_id

Default values are static or scripted but cannot reliably increment.

Trap 3: Configure a dictionary override on the asset tag field to…

Dictionary overrides modify field attributes, not generate values.

Study all Creating and customizing tables and data common traps →

A
Use a calculated value that dot-walks to a number table
Why wrong: Dot-walking is for referencing related record fields.
B
Set the default value of the asset tag field to 'AST-' + sys_id
Why wrong: Default values are static or scripted but cannot reliably increment.
C
Create a business rule that calculates the asset tag using a script that increments a counter
A business rule can generate a unique, incrementing asset tag.
D
Configure a dictionary override on the asset tag field to auto-generate
Why wrong: Dictionary overrides modify field attributes, not generate values.

Full breakdown with real-world context →

Question 2hardmultiple choice

Read the full Creating and customizing tables and data explanation →

An organization has a custom table 'u_incident_task' that extends 'task'. They need to allow users to create records in this table from the 'Incidents' module. The 'u_incident_task' table should appear as a related list on the incident form. However, the related list is not showing the 'New' button. What is the most likely cause?

Trap 1: The table is in a different application scope

Scope does not prevent the New button.

Trap 2: The table does not extend 'incident'

Extending 'task' is sufficient for related lists.

Trap 3: The user does not have the required role

Roles affect access but not the button's existence.

Study all Creating and customizing tables and data common traps →

A
There is no reference field on 'u_incident_task' pointing to the incident table
A reference field is needed to associate records and enable creation.
B
The table is in a different application scope
Why wrong: Scope does not prevent the New button.
C
The table does not extend 'incident'
Why wrong: Extending 'task' is sufficient for related lists.
D
The user does not have the required role
Why wrong: Roles affect access but not the button's existence.

Full breakdown with real-world context →

Question 3easymultiple choice

Read the full Creating and customizing tables and data explanation →

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?

Trap 1: Application scope

Scope is the application containing the table.

Trap 2: Table name

Name is the internal system name.

Trap 3: Table label

Label is the human-readable name.

Study all Creating and customizing tables and data common traps →

A
Application scope
Why wrong: Scope is the application containing the table.
B
Table name
Why wrong: Name is the internal system name.
C
Table label
Why wrong: Label is the human-readable name.
D
Application module
This defines the module where the table appears.

Full breakdown with real-world context →

Question 4hardmultiple choice

Read the full Creating and customizing tables and data explanation →

A developer is working with a custom table 'u_project_task' that has a reference field 'u_project' pointing to the 'project' table. The developer wants to create a new field 'u_category' that lists values from a choice list, but the list should be filtered based on the value of 'u_project.u_type'. Which field type should be used?

Trap 1: Choice field with a static choice list

Static choices cannot be dynamically filtered.

Trap 2: Calculated value using a script

Calculated values are read-only and not selectable.

Trap 3: Reference field to a table of categories

Reference fields do not filter based on another field unless using a reference qualifier.

Study all Creating and customizing tables and data common traps →

A
Choice field with a dependent choice list
Dependent choice lists allow filtering based on a parent field.
B
Choice field with a static choice list
Why wrong: Static choices cannot be dynamically filtered.
C
Calculated value using a script
Why wrong: Calculated values are read-only and not selectable.
D
Reference field to a table of categories
Why wrong: Reference fields do not filter based on another field unless using a reference qualifier.

Full breakdown with real-world context →

Question 5mediummultiple choice

Read the full NAT/PAT explanation →

A company has a custom table 'u_employee' with fields: 'first_name', 'last_name', 'department'. They want to create a unique index on the combination of 'last_name' and 'department' to prevent duplicate entries. Where should this index be defined?

Trap 1: In the table schema map

Schema maps are for integration, not indexing.

Trap 2: In the dictionary entry for each field

Indexes are not defined per field.

Trap 3: In the sys_dictionary table directly

sys_dictionary stores field definitions, not indexes.

Study all Creating and customizing tables and data common traps →

A
In the table schema map
Why wrong: Schema maps are for integration, not indexing.
B
In the table's dictionary record via the Indexes related list
Indexes are added to the table's dictionary.
C
In the dictionary entry for each field
Why wrong: Indexes are not defined per field.
D
In the sys_dictionary table directly
Why wrong: sys_dictionary stores field definitions, not indexes.

Full breakdown with real-world context →

Question 6hardmulti select

Read the full Creating and customizing tables and data explanation →

A developer needs to create a new table that will store confidential employee feedback. The table must have the following characteristics: (1) Only authorized HR users can read the records. (2) The table should use the 'task' model to leverage assignment and state fields. (3) The table should be accessible via web services for integration. Which TWO actions are required to meet these requirements?

Trap 1: Set the 'table' access policy to 'Internal'

Internal restricts all non-admin access.

Trap 2: Extend the 'incident' table instead of 'task'

Incident adds unwanted incident-specific behavior.

Trap 3: Enable the 'Allow web service access' property on the table

Web service access is controlled by ACLs, not a table property.

Study all Creating and customizing tables and data common traps →

A
Set the 'table' access policy to 'Internal'
Why wrong: Internal restricts all non-admin access.
B
Extend the 'incident' table instead of 'task'
Why wrong: Incident adds unwanted incident-specific behavior.
C
Enable the 'Allow web service access' property on the table
Why wrong: Web service access is controlled by ACLs, not a table property.
D
Extend the 'task' table
Task provides assignment and state fields.
E
Create ACLs on the table to restrict read access to HR users
ACLs enforce record-level security.

Full breakdown with real-world context →

Question 7mediummulti select

Read the full Creating and customizing tables and data explanation →

A developer is creating a custom table 'u_project_risk' to track risks associated with projects. The table must: (1) Automatically set the 'state' field to 'Open' when a new record is created. (2) Prevent deletion of records if the state is 'Closed'. (3) Display a warning message when a user changes the state from 'In Progress' to 'Closed'. Which THREE approaches should the developer use?

Trap 1: Create a before business rule to check state on update

A before business rule runs before save, but a before delete rule is needed for deletion.

Trap 2: Define a reference qualifier on the 'project' field

Reference qualifiers filter reference fields.

Study all Creating and customizing tables and data common traps →

A
Set a default value for the 'state' field to 'Open'
Default value sets initial state.
B
Create a before business rule to check state on update
Why wrong: A before business rule runs before save, but a before delete rule is needed for deletion.
C
Create a client script that shows a warning on state change
An onChange client script can show a message.
D
Create a business rule that aborts the delete operation on condition state='Closed'
A before delete business rule can abort.
E
Define a reference qualifier on the 'project' field
Why wrong: Reference qualifiers filter reference fields.

Full breakdown with real-world context →

Question 8mediummultiple choice

Read the full Creating and customizing tables and data explanation →

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?

Exhibit

Refer to the exhibit.

Table: u_custom_asset
Fields:
  u_asset_tag: string (max length 50)
  u_serial_number: string (max length 100)
  u_model: reference to cmdb_model
  u_cost: currency

Business rule: Before insert on u_custom_asset
Script:
(function executeRule(current, previous /*null when async*/) {

    if (!current.u_asset_tag) {
        var gr = new GlideRecord('u_custom_asset');
        gr.addQuery('u_asset_tag', 'CONTAINS', 'AST-');
        gr.orderByDesc('sys_created_on');
        gr.query();
        if (gr.next()) {
            var lastTag = gr.u_asset_tag.toString();
            var num = parseInt(lastTag.substring(4)) + 1;
            current.u_asset_tag = 'AST-' + num;
        } else {
            current.u_asset_tag = 'AST-1000';
        }
    }

})(current, previous);

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

Empty string is falsy, so condition works.

Trap 2: The script does not account for records with null asset tags

It queries existing tags.

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

It sets 'AST-1000' if no tag found.

Study all Creating and customizing tables and data common traps →

A
The condition '!current.u_asset_tag' fails when the field is empty
Why wrong: Empty string is falsy, so condition works.
B
The script does not account for records with null asset tags
Why wrong: It queries existing tags.
C
The script does not handle the scenario when no asset tag exists
Why wrong: It sets 'AST-1000' if no tag found.
D
The query uses 'CONTAINS' which may match unintended tags, and ordering by sys_created_on may not guarantee the highest number
CONTAINS can match multiple patterns, and ordering by creation time may not reflect the highest number.

Full breakdown with real-world context →

Question 9hardmultiple choice

Read the full Creating and customizing tables and data explanation →

A developer implemented the client script shown in the exhibit to auto-populate the assigned-to field based on the task type. However, when the task type is changed, the assigned-to field is not updated. The server-side script 'TaskTypeAjax' is correctly defined and returns a valid sys_id. What is the most likely reason for the failure?

Exhibit

Refer to the exhibit.

Table: u_incident_task
Fields:
  u_incident: reference to incident
  u_task_type: choice (Investigation, Resolution, Documentation)
  u_assigned_to: reference to sys_user
  u_state: choice (Open, In Progress, Closed)

Client script: onChange on u_task_type
Script:
function onChange(control, oldValue, newValue, isLoading, isTemplate) {
    if (isLoading || newValue == '') {
        return;
    }
    var ga = new GlideAjax('TaskTypeAjax');
    ga.addParam('sysparm_name', 'getDefaultAssignedTo');
    ga.addParam('sysparm_task_type', newValue);
    ga.getXMLAnswer(function(answer) {
        if (answer) {
            g_form.setValue('u_assigned_to', answer);
        }
    });
}

Trap 1: The client script does not check if oldValue is different from…

It doesn't check, but that wouldn't prevent execution.

Trap 2: The client script returns on isLoading, preventing execution

It returns during loading, but onChange triggers after loading.

Trap 3: A UI policy is overriding the assigned-to field

UI policies run client-side but wouldn't prevent the setValue.

Study all Creating and customizing tables and data common traps →

A
The client script does not check if oldValue is different from newValue
Why wrong: It doesn't check, but that wouldn't prevent execution.
B
The Script Include 'TaskTypeAjax' is not client-callable
It must be marked as client-callable in its definition.
C
The client script returns on isLoading, preventing execution
Why wrong: It returns during loading, but onChange triggers after loading.
D
A UI policy is overriding the assigned-to field
Why wrong: UI policies run client-side but wouldn't prevent the setValue.

Full breakdown with real-world context →

Question 10hardmultiple choice

Read the full Creating and customizing tables and data explanation →

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?

Trap 1: The script uses 'gs.now()' which returns a date-time string, but…

ServiceNow automatically converts date-time strings to date when assigning to a date field. This is not the cause.

Trap 2: The user executing the update does not have the…

While role-based access is required, the business rule itself does not enforce roles; ACLs would. The rule should fire regardless of role, but the status change might be blocked by an ACL. However, the question states the rule is not firing correctly, implying the script doesn't run.

Trap 3: The condition 'current.status.changes() && current.status ==…

The condition is valid. 'changes()' returns true if the field has changed, and '==' compares the new value. This is a common pattern.

Study all Creating and customizing tables and data common traps →

A
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.
Why wrong: ServiceNow automatically converts date-time strings to date when assigning to a date field. This is not the cause.
B
The business rule is set to run 'before' query instead of 'before' update or 'after' update.
A 'before' query rule runs when the record is retrieved from the database, not when it is updated. For the logic to execute on update, the rule should be set to 'before' update or 'after' update.
C
The user executing the update does not have the 'medical_device_admin' role, and the business rule lacks an ACL check.
Why wrong: While role-based access is required, the business rule itself does not enforce roles; ACLs would. The rule should fire regardless of role, but the status change might be blocked by an ACL. However, the question states the rule is not firing correctly, implying the script doesn't run.
D
The condition 'current.status.changes() && current.status == 'Maintenance'' is invalid because 'changes()' returns a boolean and cannot be combined with '=='.
Why wrong: The condition is valid. 'changes()' returns true if the field has changed, and '==' compares the new value. This is a common pattern.

Full breakdown with real-world context →

Question 11mediummulti select

Read the full Creating and customizing tables and data explanation →

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?

Trap 1: Create a module pointing to the new table

Modules are for custom navigation; the table will appear automatically under its parent if configured.

Trap 2: Set 'Label' to 'Incident Custom'

Label is for display only and does not affect inheritance.

Trap 3: Set 'Extends' to 'Task'

Extending Task would not inherit Incident-specific behavior like state model.

Study all Creating and customizing tables and data common traps →

A
Set 'Application' to the desired scope and check 'Display in application navigator'
This ensures the table is scoped correctly and appears in the navigator.
B
Create a module pointing to the new table
Why wrong: Modules are for custom navigation; the table will appear automatically under its parent if configured.
C
Set 'Label' to 'Incident Custom'
Why wrong: Label is for display only and does not affect inheritance.
D
Set 'Extends' to 'Incident'
Extending the parent table ensures inheritance of fields, business rules, and ACLs.
E
Set 'Extends' to 'Task'
Why wrong: Extending Task would not inherit Incident-specific behavior like state model.

Full breakdown with real-world context →

Question 12easymultiple choice

Read the full Creating and customizing tables and data explanation →

You are a ServiceNow developer at a company that manages IT assets. You are asked to create a new table called 'u_software_license' to track software licenses. The table must have fields for license name, vendor, purchase date, expiration date, cost, and number of seats. Additionally, the table must be accessible from the 'Software' module in the application navigator. You have created the table with the appropriate fields. However, after creating the table, it does not appear in the 'Software' module. You verify that the table is set to extend 'Task' and that the application scope is correct. What is the most likely reason the table does not appear in the module?

Trap 1: The table name 'u_software_license' is not compatible with the…

Table name does not affect navigator visibility.

Trap 2: A module has not been created to reference the new table.

Modules are separate; the table will appear under its parent's module if the checkbox is checked.

Trap 3: The table extends 'Task' instead of 'Software', so it cannot appear…

Extending Task does not prevent display; many tables extend Task and appear in modules.

Study all Creating and customizing tables and data common traps →

A
The table name 'u_software_license' is not compatible with the Software module.
Why wrong: Table name does not affect navigator visibility.
B
The 'Display in application navigator' checkbox is not checked on the table configuration.
This checkbox must be checked for the table to appear in the navigator.
C
A module has not been created to reference the new table.
Why wrong: Modules are separate; the table will appear under its parent's module if the checkbox is checked.
D
The table extends 'Task' instead of 'Software', so it cannot appear in the Software module.
Why wrong: Extending Task does not prevent display; many tables extend Task and appear in modules.

Full breakdown with real-world context →

Question 13mediumdrag order

Read the full Creating and customizing tables and data explanation →

Drag and drop the steps to create a UI Action in ServiceNow into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 14mediummatching

Read the full Creating and customizing tables and data explanation →

Match each ServiceNow update set state to its meaning.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Update set is being worked on

All changes have been captured and committed locally

Update set has been applied to the target instance

Update set will not be committed

Update set is being tested for conflicts

Question 15easymultiple choice

Read the full Creating and customizing tables and data explanation →

A company needs to store data about employee certifications. Each employee may have multiple certifications. Which approach is best practice?

Trap 1: Add a multi-select field to the User table to store certification…

Multi-select fields are not suitable for storing related records; they store simple lists.

Trap 2: Extend the User table to store certification fields directly

Extending User adds all User fields, many unnecessary for certifications.

Trap 3: Create a database view that joins User and certification data

Views are read-only and cannot be used for data input.

Study all Creating and customizing tables and data common traps →

A
Add a multi-select field to the User table to store certification IDs
Why wrong: Multi-select fields are not suitable for storing related records; they store simple lists.
B
Create a new custom table with a reference field to the User table
Allows multiple certifications per user without inheriting unwanted fields.
C
Extend the User table to store certification fields directly
Why wrong: Extending User adds all User fields, many unnecessary for certifications.
D
Create a database view that joins User and certification data
Why wrong: Views are read-only and cannot be used for data input.

Full breakdown with real-world context →

Question 16mediummultiple choice

Read the full Creating and customizing tables and data explanation →

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?

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

Works but less efficient than dictionary default script; adds separate rule.

Trap 2: Create a Client Script that runs onLoad and sets priority

Client-side only, can be bypassed, and does not guarantee server-side default.

Trap 3: Use a UI Policy to set priority based on category

UI Policies do not set field values; they only show/hide fields.

Study all Creating and customizing tables and data common traps →

A
Create a Business Rule on 'Before Insert' that sets the priority
Why wrong: Works but less efficient than dictionary default script; adds separate rule.
B
Create a Client Script that runs onLoad and sets priority
Why wrong: Client-side only, can be bypassed, and does not guarantee server-side default.
C
Use a UI Policy to set priority based on category
Why wrong: UI Policies do not set field values; they only show/hide fields.
D
Define a default value script in the dictionary for the priority field
Executes at database level with no extra rule overhead.

Full breakdown with real-world context →

Question 17hardmultiple choice

Read the full Creating and customizing tables and data explanation →

A custom table 'u_asset' extends the 'cmdb_ci' table. Users report that the 'manufacturer' field is not visible on the 'u_asset' form. What is the most likely cause?

Trap 1: The manufacturer field is not part of the cmdb_ci table

Manufacturer is a standard field on the cmdb_ci table.

Trap 2: An ACL on the u_asset table hides the manufacturer field

Possible but less common; ACLs typically control read/write, not form visibility.

Trap 3: The dictionary entry for manufacturer has mandatory set to false

Mandatory only affects submission validation, not visibility.

Study all Creating and customizing tables and data common traps →

A
The manufacturer field is not part of the cmdb_ci table
Why wrong: Manufacturer is a standard field on the cmdb_ci table.
B
The u_asset form layout does not include the manufacturer field
Child table forms are separate and must be configured to show inherited fields.
C
An ACL on the u_asset table hides the manufacturer field
Why wrong: Possible but less common; ACLs typically control read/write, not form visibility.
D
The dictionary entry for manufacturer has mandatory set to false
Why wrong: Mandatory only affects submission validation, not visibility.

Full breakdown with real-world context →

Question 18mediummulti select

Read the full Creating and customizing tables and data explanation →

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

Trap 1: The dependent field (parent) must be a reference field

The parent field can be any type, e.g., a choice or string.

Trap 2: Both fields must be on the same form

Necessary but not sufficient; the qualifier script must also be present.

Trap 3: The reference table must have a field with the same name as the…

No such requirement.

Study all Creating and customizing tables and data common traps →

A
The dependent field (parent) must be a reference field
Why wrong: The parent field can be any type, e.g., a choice or string.
B
The reference qualifier must be a script that uses the parent field's value
This script dynamically filters the choices based on the parent field.
C
Both fields must be on the same form
Why wrong: Necessary but not sufficient; the qualifier script must also be present.
D
The reference table must have a field with the same name as the parent field
Why wrong: No such requirement.
E
The form must include the parent field and the reference field
Both fields must be on the form for the parent value to be accessible.

Full breakdown with real-world context →

Question 19hardmulti select

Read the full Creating and customizing tables and data explanation →

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

Trap 1: Automatically inherits all business rules and client scripts from…

Business rules and scripts are inherited, but they can be overridden, and not all are automatically applied without checking conditions.

Trap 2: Child records automatically appear in reports on the parent table

Reports require explicit inclusion of child tables via filters.

Study all Creating and customizing tables and data common traps →

A
Automatically inherits all business rules and client scripts from the parent
Why wrong: Business rules and scripts are inherited, but they can be overridden, and not all are automatically applied without checking conditions.
B
Supports creating multiple child tables from the same parent
Multiple child tables can extend a single parent, enabling data polymorphism.
C
Inherits all fields and relationships from the parent table
Child table automatically gets all parent fields and relationships.
D
Child records automatically appear in reports on the parent table
Why wrong: Reports require explicit inclusion of child tables via filters.
E
Can add new fields specific to the child without modifying the parent
Extending allows customization of child only.

Full breakdown with real-world context →

Question 20easymulti select

Read the full Creating and customizing tables and data explanation →

Which THREE statements are true about database views in ServiceNow?

Trap 1: Database views can reference tables from different instances or…

Views are limited to tables within the same instance.

Trap 2: Database views can be updated via business rules

Views are read-only; data modifications are not allowed.

Study all Creating and customizing tables and data common traps →

A
Database views can have fields from multiple tables
Views can join multiple tables and include fields from each.
B
Database views can reference tables from different instances or databases
Why wrong: Views are limited to tables within the same instance.
C
A database view can be used as a source for reports
Reports can be built on views like regular tables.
D
Database views are read-only
Views cannot be updated directly.
E
Database views can be updated via business rules
Why wrong: Views are read-only; data modifications are not allowed.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Creating and customizing tables and data sessions

Start a Creating and customizing tables and data only practice session

Every question in these sessions is drawn from the Creating and customizing tables and data domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Creating and customizing tables and data questions →Mixed SNOW-CAD session

Frequently asked questions

What does the SNOW-CAD exam test about Creating and customizing tables and data?: Creating and customizing tables and data questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Creating and customizing tables and data questions in a focused session?: Yes — the session launcher on this page draws every question from the Creating and customizing tables and data domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other SNOW-CAD topics?: Use the topic links above to move to related areas, or go back to the SNOW-CAD question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the SNOW-CAD exam covers. They are not copied from any real exam or dump site.

Creating and customizing tables and data only

10 questions 20 questions 30 questions 50 questions

Mixed SNOW-CAD session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All SNOW-CAD questions Creating and customizing tables and data domain overview SNOW-CAD exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Creating and customizing tables and data practice questions

What to know about Creating and customizing tables and data

Common Creating and customizing tables and data exam traps

Creating and customizing tables and data questions

A company has a custom table 'u_employee' with fields: 'first_name', 'last_name', 'department'. They want to create a unique index on the combination of 'last_name' and 'department' to prevent duplicate entries. Where should this index be defined?

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?

Exhibit

Exhibit

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?

Drag and drop the steps to create a UI Action in ServiceNow into the correct order.

Match each ServiceNow update set state to its meaning.

A company needs to store data about employee certifications. Each employee may have multiple certifications. Which approach is best practice?

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?

A custom table 'u_asset' extends the 'cmdb_ci' table. Users report that the 'manufacturer' field is not visible on the 'u_asset' form. What is the most likely cause?

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

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

Which THREE statements are true about database views in ServiceNow?

Track your progress over time

Start a Creating and customizing tables and data only practice session

Related SNOW-CAD topic practice pages

Working with Data practice questions

Platform Features and Integration practice questions

Integrating and managing application data practice questions

Automating application logic with business rules and scripts practice questions

Application development using ServiceNow Studio practice questions