ServiceNow CAD Practice Test

ServiceNow Certified Application Developer (CAD)

ServiceNow CAD overview

  • 196 practice questions
  • 33 flashcards
  • 6 study guide topics
  • 39 key terms

What you'll study

  • Platform Overview and Application Design15%
  • Data Model and Database Design20%
  • Application User Interface (Forms, Lists, UI Policies)15%
  • Business Logic and Scripting (Client and Server Side)25%
  • Application Security (Roles, ACLs, Scoped Application Security)10%
  • Application Deployment, Integration, and Maintenance15%

The ServiceNow Certified Application Developer (CAD) is a vendor credential for practitioners who build custom applications on the ServiceNow platform rather than simply administer existing ones. Where an admin-focused certification tests configuration of what is already there, the CAD tests whether you can take an application from idea to working instance: model the data, build the forms and lists users actually touch, write the client- and server-side logic that makes it behave, secure it with roles and ACLs, and move it cleanly between environments.

It suits developers, technical consultants, and administrators transitioning into build work. JavaScript fluency helps, but the exam is at least as much about platform-specific judgment - business rule versus flow, UI policy versus client script, which GlideRecord pattern will not fall over at volume - as about syntax recall.

Preparation is mostly hands-on. Request a Personal Developer Instance, build a small scoped application end to end, and deliberately break it. Pair that with the published exam blueprint and official product documentation for each domain, and spend extra time on the areas you instinctively avoid. Questions are scenario-driven multiple choice, so recognising the idiomatic ServiceNow solution matters more than memorising method signatures.

This guide is independent study material. It is not affiliated with, endorsed by, or published by ServiceNow.

Common mistakes

Starting to build tables, roles and scripts before creating (and selecting) a scoped custom application, so everything lands in the global scope.

Candidates want to see something working quickly and skip the design/scope step; later questions about cross-scope access, application-scoped record visibility, and 'Accessible from' settings then become guesswork because their mental model was built in global.

What to do instead

Before adding any record, create the app (System Applications > Studio or New Application), confirm the application picker in the header shows that scope, and explicitly walk through which records need to live in the scope vs. be shared from global.

Using a String field where a Reference field is correct, or writing a display name into a reference field (and comparing a reference field to a name in a query) instead of the 32-character sys_id.

Candidates design from what the user sees on the form, not from what is stored in the column; the form shows the display value, which hides the fact that the underlying value is a GUID.

What to do instead

Decide reference vs. choice vs. string at dictionary level first; in scripts set and compare reference fields with sys_id values (or getDisplayValue()/dot-walking for the label), and verify by checking the field value in a list with the display value turned off.

Assuming that extending a table copies the parent's fields and data into the child, and expecting a query on the child table to return only child records, or expecting a query on the parent to exclude children.

The table hierarchy behaves like inheritance, not duplication: the child inherits dictionary entries and a GlideRecord on the base table also returns records from tables that extend it, which contradicts the intuitive 'separate table' picture.

What to do instead

Model the hierarchy deliberately (base task-style table plus extensions), remember the child stores sys_class_name to identify its class, and always test a hierarchy query to see what it actually returns before answering questions about record counts or filters.

Enforcing mandatory fields, read-only fields or input validation with UI policies or client scripts and calling it done.

UI policy is the fastest way to get a form to look correct during testing, so it feels like the natural enforcement tool; candidates forget it runs in the browser only and can be bypassed by list edit, imports, REST, or a user with browser tools.

What to do instead

Split the requirement: presentation and dynamic form behaviour on the client (UI policy/client script), and enforcement on the server (dictionary mandatory/read-only, data policy for import/list edit, business rule or ACL for true security).

Expecting an onChange client script to run when the form loads, or calling g_form.getValue() on a reference field and treating the result as the display name.

The onChange handler naturally looks like it covers 'the value whenever it changes', and the form shows a friendly name so the returned sys_id looks like a bug rather than the documented behaviour.

What to do instead

Use onLoad for initial state and call the same logic explicitly (or check isLoading) instead of relying on onChange; use getReference()/getDisplayValue() to read the label from a reference field and getValue() only when the sys_id is genuinely what you need.

Writing g_form or other GlideForm calls inside a business rule or Script Include that runs on the server, or trying to use GlideRecord directly inside a client script.

Candidates memorise one API surface and apply it everywhere, and both environments 'look like JavaScript', so the environment boundary is not top of mind during a timed question.

What to do instead

Anchor each answer to where it executes: server = GlideRecord/current/GlideSystem, client = g_form/g_user/g_scratchpad, and the bridge is GlideAjax calling a client-callable Script Include. State the environment out loud before choosing an API.

Believing server-side changes persist unconditionally: calling current.update() inside a before business rule, or setting current.field in an after business rule and expecting the record to be saved.

The 'before' and 'after' timing distinction is easy to read but easy to forget under pressure, and update() inside a before rule looks harmless while actually causing duplicate saves or recursion.

What to do instead

Use before rules for validation and for changes to current (they persist automatically without update()); use after rules when you need a separate GlideRecord query plus setValue()/update() for related records, and add recursion guards (workflow flag, query condition) whenever a rule updates its own table.

Treating a role listed on an ACL as sufficient access, or assuming ACLs on the table grant field-level access, without checking the most-specific-match evaluation and the security_admin elevate requirement.

Roles and ACLs are usually studied as two separate lists rather than as a resolution order, so candidates answer what 'should' be allowed instead of tracing table.field > table.* > . and the deny-by-default behaviour.

What to do instead

Learn the ACL resolution order and practise it: create a field-level ACL that conflicts with the table ACL, impersonate a user with only the lower role, and use session debug / the ACL debug tools to see which ACL actually decided the outcome; remember security_admin must be elevated to edit ACLs.

Moving records between instances with update sets while the wrong application scope is selected, or deploying a scoped app without its application files, so the target instance has broken references or missing scripts.

Update sets silently capture whatever scope is active, and scoped applications have their own deployment path (application repository/publish), so a candidate who treats 'update set' as a universal transport misses that scoped app metadata travels differently.

What to do instead

Check the application picker before every edit, verify the update set contains the expected records, use the scoped app's own publish/install path for whole applications, and plan deployment order (dictionary/tables before data, roles before ACLs).

Assuming integration is symmetric: trying to build an inbound endpoint as an outbound REST/SOAP Message record, or forgetting that inbound calls run as a user and are subject to ACLs and web-service access.

Both directions use the word 'integration' and the outbound REST Message module is the one candidates find first; the inbound permission model (authenticated user, ACLs, scripted REST API resources) is easy to skip when focusing on the payload.

What to do instead

Separate the two patterns explicitly: outbound = REST Message + REST step/method; inbound = Scripted REST API (or Import Set + transform map for bulk data). For inbound, define the authentication, the user the call runs as, and verify the ACLs that user needs.

Exam requirements can change. Confirm current details with the exam provider.

ServiceNow CAD practice

196 questions. Each one lists the choices, the correct answer, and an explanation. With JavaScript, this list opens one question at a time. The checker at the top of this page saves progress in this browser when it is available.

  1. Question 1Platform Overview and Application Design

    Which table stores the individual user records of a ServiceNow instance?

    1. sys_glide_object
    2. sys_user Correct answer.
    3. sys_user_group
    4. sys_user_role

    Explanation

    User records live in the sys_user table. Groups are stored in sys_user_group, and the roles that can be granted to users or groups are stored in sys_user_role.

  2. Question 2Platform Overview and Application Design

    In the ServiceNow data model, what is a record?

    1. A bundle of related tables shipped as an application
    2. A column that holds one value for every row
    3. A script that executes when a form is submitted
    4. A single row in a table, composed of fields Correct answer.

    Explanation

    A table is made up of rows and columns; each row is a record and each column is a field. Records hold the actual data, while field definitions live in the dictionary.

  3. Question 3Platform Overview and Application Design

    Which field type stores a link to a single record on another table?

    1. String
    2. Journal
    3. Reference Correct answer.
    4. Integer

    Explanation

    A reference field holds the sys_id of a record on another (or the same) table and renders it as a clickable link. String and integer fields store plain values, and journal fields store work notes and comments.

  4. Question 4Platform Overview and Application Design

    Custom tables created in the global scope are named with which prefix by default?

    1. u_ Correct answer.
    2. x_
    3. sys_
    4. sn_

    Explanation

    Tables created manually in the global scope receive the u_ prefix. The sys_ prefix is reserved for base-system tables, and x_ identifies tables owned by a scoped application.

  5. Question 5Platform Overview and Application Design

    Table B extends table A. Which statement describes the result?

    1. Table B inherits A's fields and may add fields of its own Correct answer.
    2. Table B receives a snapshot copy of A's existing records
    3. Table B cannot be extended by any further table
    4. Table A is removed once table B is created

    Explanation

    Extension creates an inheritance relationship: the child table stores its own records but exposes the parent's fields plus any fields defined on the child. The parent table and its records are unaffected.

  6. Question 6Platform Overview and Application Design

    Which table is the parent that Incident, Problem, and Change Request all extend?

    1. Request
    2. Task Correct answer.
    3. cmdb_ci
    4. sys_audit

    Explanation

    Task is the base table for work items and supplies common fields such as number, assignment, state, and SLA support. Incident, Problem, and Change Request all extend Task.

  7. Question 7Platform Overview and Application Design

    What is an application menu?

    1. A rule that restricts access to a table
    2. A scheduled job that runs inside an application
    3. A list of users who may open an application
    4. The top-level heading in the navigator that groups modules Correct answer.

    Explanation

    An application menu is the top level of the navigation hierarchy and contains modules. Each module opens a specific page such as a list or a form.

  8. Question 8Platform Overview and Application Design

    Which mechanism records configuration changes so they can be moved from one instance to another?

    1. Scheduled jobs
    2. Access control lists
    3. Import sets
    4. Update sets Correct answer.

    Explanation

    Update sets capture configuration changes made in one instance so the same customizations can be applied to another instance. Import sets move data, not configuration.

  9. Question 9Platform Overview and Application Design

    Which statement about a scoped application is correct?

    1. It can modify any global table without extra configuration
    2. It must extend the Task table in order to store data
    3. Artifacts are isolated, and global artifacts must be marked accessible Correct answer.
    4. It cannot contain custom tables of its own

    Explanation

    A scope is a namespace that isolates its artifacts from other scopes. Crossing a scope boundary requires explicit configuration, such as marking the target artifact accessible from the requesting scope.

  10. Question 10Platform Overview and Application Design

    Which table stores the definition of every field in the instance, including its type and default value?

    1. sys_dictionary Correct answer.
    2. sys_db_object
    3. sys_ui_element
    4. sys_choice

    Explanation

    The dictionary (sys_dictionary) holds one entry per field, describing its type, length, default, and other attributes. sys_db_object stores table-level metadata instead.

  11. Question 11Platform Overview and Application Design

    Without writing script, a designer wants a field to become mandatory and read-only when Priority is 1. Which feature should be used?

    1. Access control list
    2. Scheduled job
    3. UI policy Correct answer.
    4. Business rule

    Explanation

    UI policies apply client-side form behavior declaratively and can make fields mandatory, read-only, or visible based on conditions. They are the no-code counterpart to an onChange client script.

  12. Question 12Platform Overview and Application Design

    How is a many-to-many relationship between two tables implemented?

    1. By creating a third table with reference fields to both tables Correct answer.
    2. By adding two reference fields to the same table
    3. By making both tables extend a common parent
    4. By using a choice field that lists both tables

    Explanation

    A many-to-many relationship needs a mapping (intersection) table whose records each point to one record in each of the two related tables. A single reference field can express only a one-to-many relationship.

  13. Question 13Platform Overview and Application Design

    An administrator displays incident.caller_id.email on a form. What is this technique called?

    1. Dot-walking Correct answer.
    2. Delegation
    3. Coalescing
    4. Glide aggregation

    Explanation

    Dot-walking traverses a reference field to read a value from the related record, chaining table.field.field. It works in scripts, conditions, and field references on forms.

  14. Question 14Platform Overview and Application Design

    Which record represents a single navigable link that opens a list, a form, or another page?

    1. UI action
    2. Application menu
    3. Record producer
    4. Module Correct answer.

    Explanation

    Modules sit inside application menus and define the destination page, such as a table list or a specific form. The menu is only the container for those modules.

  15. Question 15Platform Overview and Application Design

    Where are the selectable options of a choice field stored?

    1. sys_dictionary
    2. sys_db_object
    3. sys_ui_list
    4. sys_choice Correct answer.

    Explanation

    Each option of a choice field is a record in sys_choice, keyed by the table and element it belongs to. The dictionary defines the field itself, but not its option values.

  16. Question 16Platform Overview and Application Design

    Which configuration runs on the server and therefore applies equally to form saves, imports, and REST API calls?

    1. UI action
    2. Client script
    3. UI policy
    4. Business rule Correct answer.

    Explanation

    Business rules execute on the server for every insert, update, delete, or query, regardless of the channel that triggered it. Client-side features only run in the browser.

  17. Question 17Platform Overview and Application Design

    A designer wants a button on the Incident form that runs script when clicked. Which record type should be created?

    1. UI policy
    2. Business rule
    3. UI action Correct answer.
    4. Client script

    Explanation

    UI actions define buttons, links, and context-menu items on forms and lists, and they can run client-side or server-side script. They are the standard way to add a clickable control.

  18. Question 18Platform Overview and Application Design

    Which mechanism decides whether a specific user may read or write a particular field or record?

    1. Access control list (ACL) Correct answer.
    2. UI policy
    3. Dictionary override
    4. Data policy

    Explanation

    ACLs secure tables, records, and fields by evaluating rules against the user's roles and conditions. They are the authoritative security layer on both client and server.

  19. Question 19Platform Overview and Application Design

    An administrator adds a new field to the Task table. Which tables gain that field?

    1. Only the Task table
    2. Only custom tables that extend Task
    3. Task and Incident, but no other table
    4. Task and all tables that extend it Correct answer.

    Explanation

    Fields added to a parent table become available to every child table through inheritance. Because Incident, Problem, and Change Request all extend Task, they all expose the new field.

  20. Question 20Platform Overview and Application Design

    Which of the following is captured in an update set?

    1. Configuration records such as business rules and form layouts Correct answer.
    2. The rows of data in a custom table
    3. Audit records generated by field changes
    4. User records created during testing

    Explanation

    Update sets record configuration artifacts, not transactional data. Records in business tables, user records, and audit entries are not part of an update set.

  21. Question 21Platform Overview and Application Design

    A developer makes a field mandatory with an onChange client script. A record is later created through the REST API without that field. What happens?

    1. The record is rejected, because UI policies also apply to API calls
    2. The record is rejected, because client scripts run on the server for all transactions
    3. The record is saved, but only after the client script re-runs
    4. The record is saved, because client scripts run only in the browser Correct answer.

    Explanation

    Client scripts execute in the user's browser and never run for REST, import, or other non-form transactions. To enforce a rule in every channel, the logic must be server-side, such as a business rule or a data policy.

  22. Question 22Platform Overview and Application Design

    A scoped application must read records from a global table. What is required?

    1. The scoped application must first be converted to global scope
    2. Nothing, since scoped applications reach all global tables
    3. An ACL must be created for the Everyone role
    4. The table must be made accessible from the application's scope Correct answer.

    Explanation

    Scope isolation blocks access to artifacts in other scopes unless access is explicitly granted, for example by designating the target table as accessible from the requesting scope. Only then can the scoped application query it.

  23. Question 23Platform Overview and Application Design

    A field inherited from a parent table needs a different default value and label on one child table only. What should be used?

    1. A UI policy
    2. A dictionary override Correct answer.
    3. A choice list
    4. A transform map

    Explanation

    A dictionary override changes attributes such as default value, label, or choice of an inherited field on a specific child table while leaving the parent definition untouched.

  24. Question 24Platform Overview and Application Design

    Why would a designer build a custom table that extends Task instead of a standalone table?

    1. Extending Task prevents other tables from referencing it
    2. Extending Task removes the need for access controls
    3. The table inherits task fields and behaviors such as assignment and SLA support Correct answer.
    4. Extending Task automatically generates a database view

    Explanation

    Extending Task gives the new table the common work-item fields and behaviors, so it integrates with assignment, approvals, SLAs, and task-based reporting without rebuilding them.

  25. Question 25Platform Overview and Application Design

    Where is the set of columns shown in a table's list view configured?

    1. In the form layout
    2. In the field's dictionary entry
    3. In the application menu
    4. In the list layout Correct answer.

    Explanation

    The list layout determines which columns appear and in what order for a list of records. The form layout governs the record form instead, and the dictionary stores field attributes.

  26. Question 26Platform Overview and Application Design

    In the ServiceNow platform, what is an instance?

    1. A logical grouping of users who share the same set of roles
    2. A reusable application that can be installed from the ServiceNow Store
    3. A dedicated deployment of the platform with its own database and settings Correct answer.
    4. A single record that stores one configuration setting for the platform

    Explanation

    An instance is a complete, isolated deployment of the ServiceNow platform, including its own database, configurations, and data. Customers typically run separate instances for development, testing, and production so changes can be promoted between them.

  27. Question 27Platform Overview and Application Design

    Which statement describes the sys_id field that exists on every table?

    1. It holds a unique 32-character identifier generated for each record Correct answer.
    2. It holds the value of the table's display field for the current record
    3. It records which user last updated the record and at what time
    4. It stores the human-readable number shown to end users for each record

    Explanation

    Every record is assigned a system-generated, unique 32-character GUID stored in sys_id. This value identifies the record independently of its number or display value and is used in references, URLs, and integrations.

  28. Question 28Platform Overview and Application Design

    What is a database view in ServiceNow?

    1. A read-only rendering of a form that prevents any edits
    2. A read-only virtual table that joins columns from two or more tables Correct answer.
    3. A temporary table built in memory each time a list loads
    4. A saved filter on one table that limits which records a user can see

    Explanation

    A database view combines columns from multiple tables into a single read-only table-like structure that can be queried and reported on. It does not duplicate data; it presents joined data at query time and cannot be written to directly.

  29. Question 29Platform Overview and Application Design

    Most ServiceNow tables contain an Active field. What is the intended effect of clearing it on a record?

    1. The record is copied into an archive table and locked against further edits
    2. The record is hidden only from users who lack the admin role
    3. The record is permanently removed from the table at the next cleanup job
    4. The record remains in the database but is excluded from most list queries Correct answer.

    Explanation

    The Active flag provides a soft-delete pattern: the row stays in the table and can still be referenced, but default queries and list filters typically exclude inactive records. Reactivating the record restores it to normal visibility without any data loss.

  30. Question 30Platform Overview and Application Design

    A company has two business units that must not see each other's records even though both use the same Incident table and the same roles. Which capability is designed to handle this without custom scripting on each table?

    1. Domain separation, which partitions data and configuration by domain Correct answer.
    2. A read-only ACL applied to the Incident table for the smaller unit
    3. Access Control Lists conditioned on the caller's department
    4. A separate scoped application built for each business unit

    Explanation

    Domain separation lets one instance host multiple tenants by tagging data and configuration with a domain and restricting visibility to the user's domain. It applies consistently across tables and is the platform feature built for multi-tenant isolation.

  31. Question 31Data Model and Database Design

    Which table stores the metadata definitions for tables, such as a table's name, label, and parent table?

    1. sys_dictionary
    2. sys_choice
    3. sys_glide_object
    4. sys_db_object Correct answer.

    Explanation

    Table metadata, including a table's label, name, and parent, is stored in sys_db_object. Field-level metadata lives in sys_dictionary, not in the table definition record.

  32. Question 32Data Model and Database Design

    Which field is the unique 32-character identifier that exists on every table?

    1. number
    2. name
    3. sys_class_name
    4. sys_id Correct answer.

    Explanation

    Every table includes a sys_id field, a 32-character GUID that uniquely identifies the record. It is generated by the platform and is not the same as the human-readable number field.

  33. Question 33Data Model and Database Design

    Which field type stores the sys_id of a record on another table?

    1. Choice
    2. Glide List
    3. String
    4. Reference Correct answer.

    Explanation

    A reference field stores the sys_id of a record on another table. It does not store the full referenced record or its display value.

  34. Question 34Data Model and Database Design

    Which table is the parent table for Incident, Problem, and Change Request?

    1. sys_user
    2. task Correct answer.
    3. cmdb_ci
    4. sys_db_object

    Explanation

    Incident, Problem, and Change Request all extend the task table, inheriting fields such as number, assignment, and state.

  35. Question 35Data Model and Database Design

    What is the primary purpose of extending a table?

    1. It copies existing records from the parent table into the child table.
    2. It creates a many-to-many relationship with the parent table.
    3. It inherits the parent table's fields and can add its own fields. Correct answer.
    4. It prevents the child table from using the parent's business rules.

    Explanation

    Extending a table creates a child table that inherits the parent's fields and behavior, and the child can add its own fields. It does not copy records.

  36. Question 36Data Model and Database Design

    On an extended table such as task, which field records the name of the table that actually stores a given record?

    1. number
    2. sys_class_name Correct answer.
    3. table_name
    4. sys_id

    Explanation

    For tables in a hierarchy, sys_class_name stores the name of the table that actually holds the record. This lets a query on task identify whether a row is an incident, problem, or another child class.

  37. Question 37Data Model and Database Design

    A reference field named caller_id on the Incident table points to sys_user. What does caller_id.email do?

    1. It copies the email value into the incident record.
    2. It creates a reference from email to user.
    3. It returns all users with the same email.
    4. It reads the email field from the referenced user record. Correct answer.

    Explanation

    Dot-walking follows a reference field to read a field on the referenced record. caller_id.email returns the email of the user referenced by caller_id.

  38. Question 38Data Model and Database Design

    A choice field stores the value 1 when a user selects the label High. What is saved in the database?

    1. High
    2. Both the label and the value
    3. The sys_id of the selected choice record
    4. 1, the stored choice value Correct answer.

    Explanation

    A choice field stores the choice value, not the label. The label is for display and can be changed without altering stored data.

  39. Question 39Data Model and Database Design

    A field inherited from a parent table must be mandatory only on one child table. What should you create?

    1. A choice list on the child table
    2. A dictionary override on the child table for that field Correct answer.
    3. A new field on the child table with the same name
    4. A UI policy that applies to the child form

    Explanation

    A dictionary override on the child table changes attributes such as mandatory or default for an inherited field without affecting the parent or sibling tables.

  40. Question 40Data Model and Database Design

    A GlideRecord query on the task table returns records from incident and problem. Why?

    1. Child tables in a table hierarchy are included when querying the parent. Correct answer.
    2. GlideRecord automatically unions unrelated tables.
    3. Child tables are always empty.
    4. The task table stores a copy of every child record.

    Explanation

    In a table hierarchy, querying the parent table includes records stored in its child tables. sys_class_name identifies the actual child table for each returned record.

  41. Question 41Data Model and Database Design

    Which table stores the membership relationship between users and groups?

    1. sys_user_group
    2. sys_user
    3. sys_user_grmember Correct answer.
    4. sys_user_role

    Explanation

    sys_user_grmember is the intersection table that links users to groups, with reference fields for user and group.

  42. Question 42Data Model and Database Design

    In a scoped application with the vendor prefix acme, which name follows the platform convention for a custom table?

    1. sys_acme_asset
    2. x_acme_asset Correct answer.
    3. u_acme_asset
    4. acme_asset

    Explanation

    Custom tables in a scoped application use the x_<scope>_<name> convention. A global-scope custom table uses the u_ prefix.

  43. Question 43Data Model and Database Design

    When a reference field displays a record, which field on the referenced table supplies the text shown?

    1. The first string field on the table
    2. The number field on the table
    3. The field marked as the display field for that table Correct answer.
    4. The sys_id field

    Explanation

    A reference field displays the value of the referenced table's display field. The display field is a dictionary attribute, not necessarily the first string field.

  44. Question 44Data Model and Database Design

    Where are choice list options for a field stored?

    1. sys_glide_object
    2. sys_dictionary
    3. sys_db_object
    4. sys_choice Correct answer.

    Explanation

    Choice options are stored as records in sys_choice, keyed by table and element. The field's dictionary record references the choice list but does not hold each option.

  45. Question 45Data Model and Database Design

    Which design represents a one-to-many relationship from Department to User?

    1. A Glide List on Department containing user sys_ids
    2. A many-to-many table linking Department and User
    3. A reference field on Department pointing to User
    4. A reference field on User pointing to Department Correct answer.

    Explanation

    A one-to-many relationship places a reference field on the many side, so each user points to one department. The department does not store a list of users.

  46. Question 46Data Model and Database Design

    Which table contains one record for each field on each table?

    1. sys_db_object
    2. sys_choice
    3. sys_documentation
    4. sys_dictionary Correct answer.

    Explanation

    sys_dictionary holds one record per field per table, including the field name, type, and label. It is the core metadata table for field definitions.

  47. Question 47Data Model and Database Design

    Which pair of fields is automatically maintained by the platform on every table to record creation and update timestamps?

    1. sys_mod_count and sys_id
    2. sys_created_on and sys_updated_on Correct answer.
    3. sys_created_by and sys_updated_by
    4. sys_class_name and sys_id

    Explanation

    The platform maintains sys_created_on and sys_updated_on automatically to record when a record was created and last updated. These are system fields present on tables.

  48. Question 48Data Model and Database Design

    Which setting can a dictionary override change on an inherited field?

    1. The sys_id of the parent record
    2. The field type of the inherited field
    3. The default value of the inherited field Correct answer.
    4. The column name of the inherited field

    Explanation

    A dictionary override can change attributes such as default value, mandatory, and read-only for an inherited field on a child table. It cannot change the field's type or column name.

  49. Question 49Data Model and Database Design

    In CMDB, how are CI classes such as cmdb_ci_server and cmdb_ci_database related?

    1. They are linked by a many-to-many table only.
    2. They are unrelated tables with no shared fields.
    3. They extend the cmdb_ci base class. Correct answer.
    4. They both extend the task table.

    Explanation

    CMDB CI classes form a hierarchy rooted at cmdb_ci, and specific classes such as server and database extend that base. This lets queries on cmdb_ci include all CI types.

  50. Question 50Data Model and Database Design

    What is the effect of creating a unique index on a field?

    1. The field becomes mandatory on all forms.
    2. The field automatically becomes a reference.
    3. The field is converted to a choice list.
    4. The database rejects duplicate values for that field. Correct answer.

    Explanation

    A unique index enforces uniqueness at the database level, so duplicate values for the indexed field are rejected. It does not control form behavior such as mandatory.

  51. Question 51Data Model and Database Design

    Which field type stores a running history of comments and work notes as separate entries?

    1. String
    2. Glide List
    3. Journal Correct answer.
    4. HTML

    Explanation

    A journal field stores an audit trail of entries, commonly used for comments and work notes, with each entry saved separately. It is not a simple string field.

  52. Question 52Data Model and Database Design

    What does a reference qualifier on a reference field do?

    1. It creates a many-to-many relationship.
    2. It defines the text displayed for the referenced record.
    3. It limits the records available for selection in the field. Correct answer.
    4. It encrypts the referenced record's sys_id.

    Explanation

    A reference qualifier filters the records that appear for selection in a reference field. It does not change the display field or create relationships.

  53. Question 53Data Model and Database Design

    When a record is inserted into a child table that extends a parent table, where is the record stored?

    1. It is stored in the child table only. Correct answer.
    2. It is stored in the parent table with a pointer to the child.
    3. It is duplicated in both the parent and child tables.
    4. It is stored in sys_db_object as metadata.

    Explanation

    In table extension, each record is stored in the table where it was created. Querying the parent includes child records through the hierarchy, but storage remains in the child table.

  54. Question 54Data Model and Database Design

    Which table defines the available field types such as String, Reference, and Choice?

    1. sys_choice
    2. sys_db_object
    3. sys_glide_object Correct answer.
    4. sys_dictionary

    Explanation

    sys_glide_object defines the field types available in the dictionary, such as String, Reference, and Choice. It is not where individual fields are defined.

  55. Question 55Data Model and Database Design

    Which table contains one record for each table in the instance, including its label and parent table?

    1. sys_choice_set
    2. sys_db_object Correct answer.
    3. sys_glide_object
    4. sys_dictionary

    Explanation

    sys_db_object stores table-level metadata such as the table name, label, and super_class. sys_dictionary stores the field-level metadata that sits underneath each of those tables.

  56. Question 56Data Model and Database Design

    A field of type Reference stores the record a user selected. What value is written to the database column?

    1. The display value of the selected record
    2. The name of the referenced table
    3. The record number of the selected record
    4. The sys_id of the selected record Correct answer.

    Explanation

    A reference column stores only the sys_id of the target record. The text shown to users is resolved from the referenced table's display field when the record is read.

  57. Question 57Data Model and Database Design

    Which table stores the assignment of roles to individual users?

    1. sys_user_role
    2. sys_user_group
    3. sys_user_has_role Correct answer.
    4. sys_group_has_role

    Explanation

    sys_user_has_role is the many-to-many table that records which roles have been granted to which users. The role definitions themselves live in sys_user_role.

  58. Question 58Data Model and Database Design

    A field must be able to point to a record in any table and must retain both the table name and the sys_id. Which field type fits?

    1. List
    2. String
    3. Reference
    4. Document ID Correct answer.

    Explanation

    The Document ID field type stores a table name together with a sys_id, so it can target a record in any table without listing candidates on the field. A Reference field must declare the tables it can point to.

  59. Question 59Data Model and Database Design

    Which field type stores multiple sys_ids from one table inside a single column?

    1. String
    2. List Correct answer.
    3. Reference
    4. Document ID

    Explanation

    A List field (glide_list) keeps a comma-separated set of sys_ids that all belong to one specified table. It is commonly used for fields such as watch lists.

  60. Question 60Data Model and Database Design

    A choice field named subcategory should offer only the options that fit the value selected in the category field. What is the standard configuration?

    1. Set Dependent on subcategory to category and give each choice a dependent value. Correct answer.
    2. Create a many-to-many table that links each category to its permitted subcategory values.
    3. Add a reference qualifier on subcategory that filters values by category.
    4. Convert subcategory to a List field so several values can be selected per record.

    Explanation

    Choice filtering is driven by the Dependent setting on the child field's dictionary record plus a dependent value stored on each choice. At run time the platform shows only choices whose dependent value matches the parent field's current value.

  61. Question 61Data Model and Database Design

    An administrator deletes a field from a table by removing its dictionary record. What happens to the data that was stored in that column?

    1. The field is removed from all forms but stays in the dictionary marked as inactive.
    2. The field becomes read-only, and its values are cleared by a scheduled cleanup job.
    3. The dictionary record and the database column are both removed immediately, including the stored data.
    4. The dictionary record is deleted, but the column and its data remain in the database table. Correct answer.

    Explanation

    Deleting a dictionary record removes the field from the application data model but does not drop the physical column. The stored values stay in the table until a column drop is explicitly performed.

  62. Question 62Data Model and Database Design

    A team needs a new record type whose records must appear in any query that lists tasks and must share the standard task fields. Which design meets the requirement?

    1. Create a new table that extends task. Correct answer.
    2. Create a database view that combines incident with the new records.
    3. Add the needed fields directly to the incident table.
    4. Create a standalone table with a reference field to task.

    Explanation

    Extending task gives the new table all task fields through inheritance, and its records are stored in their own table while still being returned by queries on task. A reference relationship provides neither field inheritance nor that query behavior.

  63. Question 63Data Model and Database Design

    What is the effect of adding a non-unique database index to a field that is frequently used in query filters?

    1. It encrypts the stored values so they can only be read through that field on a form.
    2. It prevents duplicate values from being saved in that field by any user.
    3. It speeds up queries that filter on the field at a small cost to write operations. Correct answer.
    4. It forces the platform to validate every value against the field's choice list.

    Explanation

    A non-unique index gives the database a faster path to rows matching a filter, at the cost of extra work on inserts and updates. It places no restriction on duplicate values.

  64. Question 64Data Model and Database Design

    A choice field stores the value 2 for the label High. The designer renames that label to Critical and leaves the value as 2. What do existing records that store 2 display?

    1. They are rewritten by a background job to store the new label text.
    2. They display the new label Critical because only the label changed. Correct answer.
    3. They keep showing High because the label is copied into the record at insert time.
    4. They display blank until each record is opened and saved again.

    Explanation

    Choices persist the numeric value, while the label is looked up from the choice list whenever the record is displayed. Editing a label therefore changes how all records holding that value appear.

  65. Question 65Data Model and Database Design

    A field is added to a parent table after several child tables already exist. What is the result for those child tables?

    1. Each child table keeps its own copy of the field, which must be created manually per child.
    2. The field is added only to the parent table and is never visible to child records.
    3. The child tables reject the change until each one is recompiled by an administrator.
    4. The field is immediately available on every child table as an inherited field. Correct answer.

    Explanation

    Table inheritance is applied dynamically: a field defined on the parent is exposed on every child table without any manual step. The child tables therefore gain the field and its storage automatically.

  66. Question 66Data Model and Database Design

    A reference field on a child table uses the Cascade Rule Restrict. A user tries to delete a parent record that two child records still reference. What is the outcome?

    1. The delete is blocked while any child record still references the parent. Correct answer.
    2. The parent record is deleted, and each referencing field keeps the stale sys_id value.
    3. The parent record is deleted and the two child records are deleted as well.
    4. The parent record is deleted and the referencing fields are cleared.

    Explanation

    Restrict prevents deletion of a record while references to it still exist, protecting the relationship. The user must first remove or repoint the referencing records.

  67. Question 67Data Model and Database Design

    How does the platform maintain referential integrity between a reference field and the table it points to?

    1. By locking the referenced record while any other record points to it.
    2. Through a periodic job that removes references to deleted records.
    3. Through a foreign key constraint created in the database when the field is defined.
    4. At the application layer, because no database foreign key constraints are created. Correct answer.

    Explanation

    ServiceNow does not define database-level foreign keys; relationships are managed by the platform's own logic and cascade rules. As a result, a reference can hold a sys_id whose record no longer exists.

  68. Question 68Application User Interface (Forms, Lists, UI Policies)

    On a ServiceNow form, which element is used to group related fields together visually?

    1. A related list
    2. A list control
    3. A field annotation
    4. A form section Correct answer.

    Explanation

    A form section is a container on the form that holds fields and other elements, and administrators split a form into several sections to organize fields logically. Related lists show child records, list controls govern list behavior, and annotations are display-only text.

  69. Question 69Application User Interface (Forms, Lists, UI Policies)

    An administrator needs the Assignment group field to become mandatory on the Incident form whenever Category is Hardware. Which UI policy action accomplishes this?

    1. Set field visible
    2. Add field to section
    3. Set field value
    4. Make field mandatory Correct answer.

    Explanation

    The mandatory action in a UI policy changes whether a field must be filled in when the policy condition evaluates as configured. Actions operate on existing form fields; adding fields or moving them is a form layout task, not a policy action.

  70. Question 70Application User Interface (Forms, Lists, UI Policies)

    Which form element displays records from a child table that reference the record currently open?

    1. The filter breadcrumb
    2. A related list Correct answer.
    3. The form header
    4. The activity stream

    Explanation

    A related list appears at the bottom of a form and shows records on another table that are linked to the current record through a reference field or many-to-many relationship. It is configured per table and can be added or removed in the form layout.

  71. Question 71Application User Interface (Forms, Lists, UI Policies)

    What is the purpose of an annotation on a form?

    1. Shows static text for user guidance Correct answer.
    2. Restricts the form to a single view
    3. Makes a field mandatory on insert
    4. Records each change made to a field

    Explanation

    An annotation is a non-data element placed in a form section that displays fixed text, such as instructions or a policy reminder. It stores no record data and does not change the behavior of any field.

  72. Question 72Application User Interface (Forms, Lists, UI Policies)

    Several active UI policies apply to the same table. What determines the order in which they are evaluated?

    1. The alphabetical order of the policy names
    2. The order in which the fields appear on the form
    3. The Order value, lowest first Correct answer.
    4. The sequence the policies were created in

    Explanation

    Each UI policy record carries an Order value, and policies are processed in ascending order of that value. Administrators raise or lower the Order value to control which policy takes effect last when two policies touch the same field.

  73. Question 73Application User Interface (Forms, Lists, UI Policies)

    What is the primary purpose of a form template?

    1. It pre-fills field values on new records Correct answer.
    2. It controls which users may open the form
    3. It defines the sections shown on the form
    4. It enforces required fields on the server

    Explanation

    A form template stores a set of field values that are applied automatically when a user creates a new record from that form, saving repetitive data entry. Templates do not alter the layout, security, or server-side validation of the form.

  74. Question 74Application User Interface (Forms, Lists, UI Policies)

    A UI policy makes a field mandatory when its condition is true. The Reverse if false option is selected. What happens when the condition later becomes false?

    1. An error message is shown and the record cannot be saved
    2. The field reverts to its dictionary-defined mandatory state Correct answer.
    3. The field stays mandatory until the form is reloaded
    4. The policy is disabled for the rest of the session

    Explanation

    Reverse if false applies the opposite of each configured action when the condition stops being true, so the field returns to the state defined by the dictionary rather than staying in the policy-controlled state. Without this option the applied state simply persists for the rest of the session.

  75. Question 75Application User Interface (Forms, Lists, UI Policies)

    Which combination must be true for a UI policy's actions to be applied on a form?

    1. The table must have at least one client script
    2. The form must be opened in the Service Portal
    3. The policy must be active and its condition must be met Correct answer.
    4. The user must hold the admin role

    Explanation

    UI policies are client-side rules that run only while the record is active and only when the configured condition evaluates to the required result. If the policy is inactive, or the condition is not satisfied and Reverse if false is not selected, no actions are applied.

  76. Question 76Application User Interface (Forms, Lists, UI Policies)

    A UI policy has the Run scripts option selected and contains a script. When does that script execute?

    1. Instead of the policy's field actions
    2. On the server before the record is written
    3. Together with the policy's actions, whenever the policy runs Correct answer.
    4. Only when the record is submitted

    Explanation

    Selecting Run scripts adds a client-side script that is executed whenever the policy itself runs, alongside the configured field actions. The script can perform additional changes, such as setting values or showing messages, that the standard actions cannot express.

  77. Question 77Application User Interface (Forms, Lists, UI Policies)

    Which tool is used to move a field from one section to another on a form?

    1. System Dictionary
    2. UI Policy
    3. Form Design (form layout) Correct answer.
    4. List Layout

    Explanation

    Form Design, the form layout editor, lets an administrator add, remove, reorder, and move fields between sections and control which sections appear. The dictionary only defines a field's properties, not its placement on the form.

  78. Question 78Application User Interface (Forms, Lists, UI Policies)

    Which UI policy action stops a user from saving the form until a value is entered?

    1. Mandatory Correct answer.
    2. Read only
    3. Visible
    4. Set field value

    Explanation

    The mandatory action marks a field as required so the record cannot be submitted while the field is empty. Visible controls display, read only prevents editing, and set field value populates data.

  79. Question 79Application User Interface (Forms, Lists, UI Policies)

    A user wants to change which columns appear in a list for themselves, without affecting other users. What should they do?

    1. Personalize the list columns Correct answer.
    2. Edit the dictionary record
    3. Create a new view
    4. Change the module definition

    Explanation

    List personalization stores column choices, order, and width per user, so only that user's list display changes. Administrators change the shared list layout through list controls or the module instead.

  80. Question 80Application User Interface (Forms, Lists, UI Policies)

    Columns of a related list must be changed for all users. Where is this configured?

    1. In the parent table's dictionary entry
    2. In the related list configuration Correct answer.
    3. In each user's list personalization
    4. In the system properties for lists

    Explanation

    The related list configuration for a table defines which columns that related list shows to everyone, and it is maintained through the form's related list settings rather than by individual users. Personal list settings only affect the person who sets them.

  81. Question 81Application User Interface (Forms, Lists, UI Policies)

    Which object is available inside a UI policy script to manipulate fields on the current form?

    1. g_user
    2. g_form Correct answer.
    3. g_modal
    4. g_list

    Explanation

    UI policy scripts run on the client and use g_form to read and change field values, visibility, mandatory state, and read-only state on the form that is open. The other objects serve different purposes: list manipulation, user information, and dialogs.

  82. Question 82Application User Interface (Forms, Lists, UI Policies)

    A UI policy has both On load and Reverse if false selected, and its condition is false when the form loads. What is the result?

    1. The policy waits for a field change before running
    2. Nothing is applied because the condition is false
    3. The policy's actions are applied on load
    4. The reverse of the configured actions is applied Correct answer.

    Explanation

    With On load selected, the policy is evaluated as soon as the form is displayed. Because the condition is false and Reverse if false is selected, the inverse of each configured action is applied immediately at load.

  83. Question 83Application User Interface (Forms, Lists, UI Policies)

    A user wants to narrow a list so that it shows only records where Priority is 1 - Critical. Which list feature is used?

    1. The column header sort
    2. The form's activity stream
    3. The list title menu
    4. The filter condition builder Correct answer.

    Explanation

    The condition builder attached to the list creates a query that limits which records are returned, and it can be saved as a personal or shared view. Sorting changes only the order of records, not which records appear.

  84. Question 84Application User Interface (Forms, Lists, UI Policies)

    A field must remain uneditable even if a user bypasses client-side restrictions with browser tools. Which configuration enforces this?

    1. A form annotation explaining the rule
    2. A write access control (ACL) on the field Correct answer.
    3. A UI policy read-only action
    4. A client script that blocks editing

    Explanation

    ACLs are evaluated on the server for every read and write, so they enforce restrictions even when client-side controls are manipulated. UI policy actions and client scripts only affect what the browser displays and can be circumvented.

  85. Question 85Application User Interface (Forms, Lists, UI Policies)

    Once a form has loaded, when is a UI policy's condition re-evaluated?

    1. Each time a field referenced in the condition changes Correct answer.
    2. Only when the form is submitted
    3. Only once, at form load
    4. Every 30 seconds by a timer

    Explanation

    UI policies watch the fields used in their conditions and re-run automatically whenever one of those values changes on the form. This is what allows fields to appear, hide, or become required in response to user input.

  86. Question 86Application User Interface (Forms, Lists, UI Policies)

    Which list feature allows a user to edit field values directly in the list rows?

    1. Inline (list) editing Correct answer.
    2. Export
    3. Group by
    4. Filter

    Explanation

    Inline editing lets a user double-click a cell in a list and change the value without opening the record. Grouping, filtering, and exporting change how the list is displayed or delivered, not how values are modified.

  87. Question 87Application User Interface (Forms, Lists, UI Policies)

    A UI policy must apply to forms on many different tables. What must be configured?

    1. A UI policy on the sys_user table
    2. One UI policy per table, linked by name
    3. A UI policy on the Task table only
    4. A global UI policy with no table specified Correct answer.

    Explanation

    A global UI policy has no table assignment and is therefore evaluated on forms across all tables, provided its condition references fields that exist on the form. Table-specific policies are limited to the table they name.

  88. Question 88Application User Interface (Forms, Lists, UI Policies)

    A field must always be populated, including on records created by imports and API calls. Which configuration guarantees this?

    1. A UI policy that makes the field mandatory
    2. A UI policy with Reverse if false selected
    3. A dictionary mandatory attribute on the field Correct answer.
    4. A client script that checks the field on submit

    Explanation

    A mandatory attribute on the dictionary is enforced whenever the record is written, so imports, integrations, and API clients are held to the same rule as form users. UI policies and client scripts act in the browser and never run for direct data loads.

  89. Question 89Application User Interface (Forms, Lists, UI Policies)

    A UI policy hides a field that already contains a value. What happens to that value when the record is saved?

    1. It is cleared because hidden fields are ignored
    2. It is copied to the activity stream
    3. It is retained and saved with the record Correct answer.
    4. It is stored only if the field is mandatory

    Explanation

    Hiding a field changes only its visibility in the browser; the underlying value stays on the record and is written back when the form is saved. To actually remove the value, a set field value action or a script must clear it explicitly.

  90. Question 90Application User Interface (Forms, Lists, UI Policies)

    Which form element shows the record's work notes and comments history?

    1. The related list filter
    2. The activity stream Correct answer.
    3. The field annotation
    4. The form header

    Explanation

    The activity stream displays comments, work notes, and field change history for the current record and allows users to add new entries. It is a form element distinct from fields, related lists, and annotations.

  91. Question 91Application User Interface (Forms, Lists, UI Policies)

    Different groups of users must see different form layouts for the same table. Which feature supports this?

    1. Views and view rules Correct answer.
    2. UI policy actions
    3. List personalization
    4. Dictionary overrides

    Explanation

    A view defines a specific arrangement of fields and related lists, and view rules determine which view a given user sees based on conditions such as role or group. UI policies change field behavior but not which layout is presented.

  92. Question 92Application User Interface (Forms, Lists, UI Policies)

    Which form element attaches a short explanatory note to a single field and displays it only when a user hovers over a small icon next to that field?

    1. Form template
    2. Section caption
    3. Field label override
    4. Annotation Correct answer.

    Explanation

    An annotation attaches a short text note to one specific field on a form and renders as a small icon whose text appears on hover. It stores no record data and does not change the field's behavior, it only surfaces guidance in the form context.

  93. Question 93Application User Interface (Forms, Lists, UI Policies)

    A developer needs client-side logic to run each time a user changes the value of the Priority field on a form, before the record is submitted. Which client script type is configured for that behavior?

    1. onSubmit
    2. onChange Correct answer.
    3. onLoad
    4. onCellEdit

    Explanation

    An onChange client script is created against one specific field and fires whenever that field's value changes on the form. It is the standard hook for reacting to user edits before the record is saved.

  94. Question 94Application User Interface (Forms, Lists, UI Policies)

    An Incident list must show the name of each caller's manager as a column, without storing any new data on the Incident table. What is the appropriate approach?

    1. Copy the manager name into a text field on Incident with a business rule.
    2. Dot-walk to Manager.Name through the Caller column. Correct answer.
    3. Build a database view that joins the Incident and User tables.
    4. Add a manager reference field to the Incident table.

    Explanation

    Dot-walking follows a reference field to a field on the referenced record, so Caller.Manager.Name can be displayed as a list column. The value is resolved at display time from data that already exists, so no schema change or stored copy is needed.

  95. Question 95Application User Interface (Forms, Lists, UI Policies)

    A client script must display a neutral status message in the banner area at the top of a form. Which g_form method accomplishes this?

    1. g_form.addErrorMessage()
    2. g_form.showFieldMsg()
    3. g_form.addOption()
    4. g_form.addInfoMessage() Correct answer.

    Explanation

    g_form.addInfoMessage() places an informational message in the form's message area at the top of the form. It takes only the message text and does not require a field name, unlike field-level messaging methods.

  96. Question 96Application User Interface (Forms, Lists, UI Policies)

    Users must be able to type a value directly into a cell of a list row, and a script must run each time such an inline edit is made. Which configuration provides this behavior?

    1. An onCellEdit client script on the list's table Correct answer.
    2. A UI policy with Run scripts selected on the table
    3. A before query business rule on the table
    4. An onLoad client script on the list's table

    Explanation

    An onCellEdit client script is defined on the table with a target field and runs when a user changes that field inline in a list. Form-oriented mechanisms such as onLoad scripts and UI policies do not fire for edits made directly in list rows.

  97. Question 97Business Logic and Scripting (Client and Server Side)

    Which client script type executes when a user opens a form?

    1. onSubmit
    2. onChange
    3. onLoad Correct answer.
    4. onCellEdit

    Explanation

    Each client script type is bound to a specific browser event. onLoad fires when the form is rendered, whereas onChange fires when a field value changes, onSubmit when the form is saved, and onCellEdit when a list cell is edited.

  98. Question 98Business Logic and Scripting (Client and Server Side)

    Inside a client script, which call retrieves the value a user has entered in the 'short_description' field?

    1. gs.getValue('short_description')
    2. g_form.getValue('short_description') Correct answer.
    3. g_record.getValue('short_description')
    4. current.getValue('short_description')

    Explanation

    Client scripts use the g_form object to read and write values on the form currently displayed in the browser. The gs and current objects exist only in server-side scripts, and g_record is not a ServiceNow client-side object.

  99. Question 99Business Logic and Scripting (Client and Server Side)

    Which GlideSystem method writes an entry to the system log at the info severity level?

    1. gs.debug('message')
    2. gs.error('message')
    3. gs.warn('message')
    4. gs.info('message') Correct answer.

    Explanation

    GlideSystem offers severity-specific logging methods, and gs.info writes at the info level. gs.warn, gs.error, and gs.debug write at their own corresponding severities.

  100. Question 100Business Logic and Scripting (Client and Server Side)

    In a business rule that runs on update, which object contains the field values as they were before the change?

    1. previous Correct answer.
    2. g_scratchpad
    3. current
    4. gs

    Explanation

    During an update, current holds the incoming values that are about to be written, while previous holds the values already stored in the database before this operation. Comparing the two is how change detection is normally done.

  101. Question 101Business Logic and Scripting (Client and Server Side)

    A GlideRecord has been built with several addQuery() calls. Which method executes the query so the results can be iterated?

    1. update()
    2. next()
    3. get()
    4. query() Correct answer.

    Explanation

    addQuery() only adds conditions to the GlideRecord. The query() method sends those conditions to the database and positions the record set so that next() can walk through the results.

  102. Question 102Business Logic and Scripting (Client and Server Side)

    Which configuration feature can make a field mandatory or read-only based on another field's value without writing script?

    1. Business rule
    2. Script include
    3. Client script
    4. UI policy Correct answer.

    Explanation

    UI policies are declarative rules that change field mandatory, read-only, and visible states in the form. They are evaluated in the browser without requiring custom code, unlike client scripts.

  103. Question 103Business Logic and Scripting (Client and Server Side)

    Where does a client script execute?

    1. In the user's browser Correct answer.
    2. In a scheduled job
    3. Inside the database engine
    4. On the application server

    Explanation

    Client scripts are downloaded with the form and run in the browser's JavaScript engine. Server-side logic such as business rules, script includes, and scheduled jobs runs on the application node instead.

  104. Question 104Business Logic and Scripting (Client and Server Side)

    Which client-side call displays an informational message at the top of a form?

    1. current.addInfoMessage('Saved')
    2. gs.addInfoMessage('Saved')
    3. g_form.addInfoMessage('Saved') Correct answer.
    4. g_record.addInfoMessage('Saved')

    Explanation

    The g_form object controls form-level presentation, including addInfoMessage and addErrorMessage. The gs and current objects are server-side only, and g_record does not exist.

  105. Question 105Business Logic and Scripting (Client and Server Side)

    What does the GlideRecord get() method return when it is called with a sys_id?

    1. The sys_id of the first match
    2. The number of matching records
    3. The display value of the record
    4. true if the record was found Correct answer.

    Explanation

    get() loads at most one record identified by its sys_id and returns a Boolean indicating whether that record was found. The field values are then read from the same GlideRecord object.

  106. Question 106Business Logic and Scripting (Client and Server Side)

    A business rule must set a field on the record and have that value saved without an additional update call. Which timing should be used?

    1. after
    2. async
    3. before Correct answer.
    4. display

    Explanation

    Before business rules run while the record is still being written, so any change made to current is stored by the same database operation. After rules run once the write has already happened and require an explicit update to persist changes.

  107. Question 107Business Logic and Scripting (Client and Server Side)

    Which setting must be enabled on a script include so that a client script can invoke it through GlideAjax?

    1. Protected
    2. Accessible from all scopes
    3. Mandatory
    4. Client callable Correct answer.

    Explanation

    The Client callable flag exposes a script include to GlideAjax requests originating in the browser. Without it, the server will not process client-initiated calls to that script include.

  108. Question 108Business Logic and Scripting (Client and Server Side)

    Which client-side class is used to call a client-callable script include from a client script?

    1. GlideDateTime
    2. GlideRecord
    3. GlideAjax Correct answer.
    4. g_form

    Explanation

    GlideAjax packages a request to a client-callable script include and returns the server response to a callback function in the browser. GlideRecord, g_form, and GlideDateTime serve other purposes and cannot invoke server-side script includes.

  109. Question 109Business Logic and Scripting (Client and Server Side)

    An onCellEdit client script runs in which situation?

    1. A record is deleted by a server-side business rule
    2. A form is loaded for the first time
    3. A user edits a value in an editable list cell Correct answer.
    4. A scheduled job runs in the background queue

    Explanation

    onCellEdit is triggered when a value is changed directly inside an editable list and the cell loses focus. Form-level events are handled instead by onLoad, onChange, and onSubmit.

  110. Question 110Business Logic and Scripting (Client and Server Side)

    Which statement describes how an asynchronous business rule runs?

    1. It runs before the record is written and can change field values
    2. It runs in the browser as part of the form submit
    3. It runs only when records are deleted
    4. It runs in the background after the transaction completes Correct answer.

    Explanation

    Asynchronous business rules are placed on the event queue and processed after the current transaction commits. Because they run later, they cannot modify the record that triggered them.

  111. Question 111Business Logic and Scripting (Client and Server Side)

    Which class computes aggregate values such as COUNT and SUM without loading each matching record?

    1. GlideFilter
    2. GlideAggregate Correct answer.
    3. GlideRecord
    4. GlideRecordSecure

    Explanation

    GlideAggregate issues GROUP BY, COUNT, SUM, AVG, MIN, and MAX operations in the database and returns only the aggregate result. It avoids the overhead of iterating every matching record with GlideRecord.

  112. Question 112Business Logic and Scripting (Client and Server Side)

    An after business rule updates related records through GlideRecord. Which call prevents business rules from firing for that update?

    1. autoSysFields(false)
    2. setNoTrigger(true)
    3. setForceUpdate(true)
    4. setWorkflow(false) Correct answer.

    Explanation

    setWorkflow(false) suppresses business rules, workflows, and related engine events for subsequent operations on that GlideRecord. It is the standard way to avoid unintended cascading logic.

  113. Question 113Business Logic and Scripting (Client and Server Side)

    An onSubmit client script returns false. What is the result?

    1. The form reloads with default field values
    2. The script is re-run once before the save
    3. The form does not submit and stays open Correct answer.
    4. The record is saved and the form closes

    Explanation

    The return value of an onSubmit script controls whether the save proceeds. Returning false cancels the submission so the user remains on the form, typically after an error message has been shown.

  114. Question 114Business Logic and Scripting (Client and Server Side)

    Which server-side call checks whether the current user has the 'itil' role?

    1. gs.isMemberOf('itil')
    2. gs.getRole('itil')
    3. gs.userHasRole('itil')
    4. gs.hasRole('itil') Correct answer.

    Explanation

    GlideSystem exposes hasRole() to test the roles of the current session, for example inside a business rule or script include. The other method names do not exist on the gs object.

  115. Question 115Business Logic and Scripting (Client and Server Side)

    Which business rule 'when' setting runs on the server as a form is displayed, before the user sees it?

    1. before
    2. async
    3. after
    4. display Correct answer.

    Explanation

    A display business rule fires on the server when a form loads, which makes it the right place to populate g_scratchpad for client scripts. It cannot modify the record being displayed.

  116. Question 116Business Logic and Scripting (Client and Server Side)

    Which class behaves like GlideRecord but also enforces record-level ACLs for the current user?

    1. GlideRecordSecure Correct answer.
    2. GlideFilter
    3. GlideAggregate
    4. GlideRecordEncoded

    Explanation

    GlideRecordSecure applies access control checks to every record it reads or writes on behalf of the current user. Plain GlideRecord does not enforce those record-level ACLs by default in server-side script.

  117. Question 117Business Logic and Scripting (Client and Server Side)

    For a single record update, in what order do the business rule timings execute?

    1. before, then after, then async Correct answer.
    2. before, then async, then after
    3. after, then before, then async
    4. async, then before, then after

    Explanation

    Before rules run first, inside the transaction and before the database write. After rules then run once the record is written, and asynchronous rules are queued to run after the transaction commits.

  118. Question 118Business Logic and Scripting (Client and Server Side)

    A client-callable script include extends AbstractAjaxProcessor and the client sends the parameter 'sysparm_id'. How does the server-side method read that value?

    1. this.getParameter('sysparm_id') Correct answer.
    2. g_form.getValue('sysparm_id')
    3. this.request.getParameter('sysparm_id')
    4. gs.getParameter('sysparm_id')

    Explanation

    AbstractAjaxProcessor provides a getParameter() method that reads parameters added on the client with addParam(). Parameters prefixed with sysparm_ are the conventional way to pass values such as record identifiers.

  119. Question 119Business Logic and Scripting (Client and Server Side)

    What is the purpose of a before query business rule?

    1. To populate reference fields on a form
    2. To validate field values before a record is inserted
    3. To limit which records a query returns for a user Correct answer.
    4. To modify the record after it is written

    Explanation

    A before query business rule appends conditions to queries executed against its table, so restricted records are never returned to the user. It runs at query time rather than during a record write.

  120. Question 120Business Logic and Scripting (Client and Server Side)

    A client script calls GlideAjax and reads the returned value on the very next line, but gets nothing. Why?

    1. The response is asynchronous and arrives in the callback Correct answer.
    2. The script include was not marked as client callable
    3. GlideAjax can only be called from a server-side business rule
    4. GlideAjax always returns a Boolean instead of a string value

    Explanation

    GlideAjax sends the request to the server asynchronously, so execution continues on the next line before any response exists. The returned value must be processed inside the callback function supplied to getXMLAnswer() or getXML().

  121. Question 121Business Logic and Scripting (Client and Server Side)

    What does GlideRecord.addEncodedQuery() accept?

    1. An encoded query string with operators like ^ and = Correct answer.
    2. A JSON object of field names and values
    3. A SQL WHERE clause that the database translates directly
    4. A single field name and value pair only

    Explanation

    addEncodedQuery() takes a complete encoded query string such as 'active=true^priority=1' and applies it to the GlideRecord. Building the same conditions with addQuery() calls produces an equivalent result.

  122. Question 122Business Logic and Scripting (Client and Server Side)

    During iteration of a GlideRecord query result, which method moves to the next record and returns false once no records remain?

    1. query()
    2. get()
    3. hasNext()
    4. next() Correct answer.

    Explanation

    GlideRecord.next() advances the cursor to the next row and returns false when the result set is exhausted, which is why it is commonly used as while (gr.next()). hasNext() only tests for another row, and query() executes the query.

  123. Question 123Business Logic and Scripting (Client and Server Side)

    Which statement describes the use of GlideRecord inside a client script?

    1. It works only for the record currently displayed.
    2. It is available only in UI actions.
    3. It is not available on the client, so server data is retrieved through GlideAjax. Correct answer.
    4. It can query any table directly from the browser.

    Explanation

    GlideRecord is a server-side class and is not available in browser client scripts. Client scripts must request server data through GlideAjax or another server endpoint.

  124. Question 124Business Logic and Scripting (Client and Server Side)

    Which client-side call sets the value of the field named 'priority' to '1'?

    1. g_form.setValue('priority', '1') Correct answer.
    2. g_form.set('priority', '1')
    3. g_form.setFieldValue('priority', '1')
    4. g_form.update('priority', '1')

    Explanation

    g_form.setValue(fieldName, value) assigns a value to a form field on the client. It takes the field name as the first argument and the new value as the second.

  125. Question 125Business Logic and Scripting (Client and Server Side)

    Which GlideRecord method deletes the record to which the GlideRecord currently points?

    1. destroy()
    2. delete()
    3. remove()
    4. deleteRecord() Correct answer.

    Explanation

    deleteRecord() removes the row that the GlideRecord currently points to. It is typically called after query() and next() have positioned the GlideRecord on a valid row.

  126. Question 126Business Logic and Scripting (Client and Server Side)

    On the server, which call returns the login name of the current user?

    1. g_form.getUserName()
    2. gs.getUserID()
    3. g_user.getUserName()
    4. gs.getUserName() Correct answer.

    Explanation

    gs is the server-side GlideSystem object; gs.getUserName() returns the current user's login name. gs.getUserID() returns the user's sys_id instead.

  127. Question 127Business Logic and Scripting (Client and Server Side)

    Which GlideRecord method returns the name of the table associated with the GlideRecord?

    1. getRecordTable()
    2. getTable()
    3. getTableName() Correct answer.
    4. tableName()

    Explanation

    getTableName() returns the table name of the GlideRecord's current table. This is useful when a script works with inherited tables and needs the actual table.

  128. Question 128Business Logic and Scripting (Client and Server Side)

    Which client-side method returns the current value of a form field as a string?

    1. g_form.valueOf('field')
    2. g_form.getValue('field') Correct answer.
    3. g_form.field('field')
    4. g_form.get('field')

    Explanation

    g_form.getValue(fieldName) returns the field's current value as a string on the client. For reference fields it returns the referenced record's sys_id.

  129. Question 129Business Logic and Scripting (Client and Server Side)

    Which client-side object provides information about the current user, such as roles, without a server round trip?

    1. gs
    2. g_user Correct answer.
    3. GlideRecord
    4. g_form

    Explanation

    g_user is the client-side object that exposes current-user information such as roles and user ID. It avoids a server round trip for these common checks.

  130. Question 130Business Logic and Scripting (Client and Server Side)

    A server-side script calls `var newId = gr.insert();` after populating a new GlideRecord. What does `newId` contain?

    1. The number of records inserted
    2. The sys_id of the inserted record Correct answer.
    3. A Boolean indicating success
    4. The GlideRecord object that was inserted

    Explanation

    GlideRecord.insert() returns the sys_id of the newly inserted record, or an empty value if the insert fails. It does not return a Boolean or the record object.

  131. Question 131Business Logic and Scripting (Client and Server Side)

    In a before update business rule, which expression returns the value that was stored in the database before the update?

    1. gr.field_name
    2. current.field_name
    3. oldValue(field_name)
    4. previous.field_name Correct answer.

    Explanation

    In a before update rule, previous contains the values read from the database before the change, and current contains the new values. previous.field_name therefore returns the old value.

  132. Question 132Business Logic and Scripting (Client and Server Side)

    A GlideAjax callback receives the response object. Which method returns the server's answer as a string without manually parsing XML?

    1. response.getParameter()
    2. response.getXMLAnswer() Correct answer.
    3. response.getAnswerText()
    4. response.responseXML

    Explanation

    GlideAjax responses expose getXMLAnswer(), which returns the answer portion as a string. This avoids manually walking the XML response.

  133. Question 133Business Logic and Scripting (Client and Server Side)

    Two before update business rules apply to the same table. Rule A has order 100, Rule B has order 200. Which rule runs first?

    1. Rule B
    2. The rule created first
    3. The rule with the lexicographically smaller name
    4. Rule A Correct answer.

    Explanation

    Business rule order controls execution sequence; lower order numbers run first. When both rules run on the same table and event, Rule A with order 100 runs before Rule B with order 200.

  134. Question 134Business Logic and Scripting (Client and Server Side)

    A GlideRecord query returns 50 records. The script calls `gr.setValue('active', false)` and then `gr.updateMultiple()`. What is the result?

    1. An error occurs because updateMultiple() requires a sys_id.
    2. Only the current record is updated.
    3. All 50 records are updated in one database operation. Correct answer.
    4. The query is re-executed and only the first record is updated.

    Explanation

    updateMultiple() applies the current field values to every record in the query result in one operation. It does not update only the current row.

  135. Question 135Business Logic and Scripting (Client and Server Side)

    Which server-side API adds an informational message to the top of the form for the user?

    1. gs.addInfoMessage() Correct answer.
    2. g_form.addInfoMessage()
    3. gs.info()
    4. current.addInfoMessage()

    Explanation

    gs.addInfoMessage() is a server-side call that places an informational message at the top of the form. gs.info() writes to the system log rather than the form.

  136. Question 136Business Logic and Scripting (Client and Server Side)

    Which client-side call adds a new choice to the 'state' field at runtime?

    1. g_form.addOption('state', '4', 'Closed') Correct answer.
    2. g_form.appendOption('state', '4', 'Closed')
    3. g_form.setOption('state', '4', 'Closed')
    4. g_form.addChoice('state', '4', 'Closed')

    Explanation

    g_form.addOption(fieldName, value, label) adds a choice option to a choice field at runtime. The value is what is stored and the label is what the user sees.

  137. Question 137Business Logic and Scripting (Client and Server Side)

    Which class should a server-side script use to compare two date/time values with methods such as before() and after()?

    1. GlideTime
    2. GlideDuration
    3. GlideDateTime Correct answer.
    4. GlideDate

    Explanation

    GlideDateTime provides date/time comparison and manipulation methods, including before() and after(). GlideDuration represents a length of time rather than a point in time.

  138. Question 138Business Logic and Scripting (Client and Server Side)

    A client script must check whether the current user has exactly the role 'admin', without matching roles inherited through a hierarchy. Which call is appropriate?

    1. g_user.hasRoles('admin')
    2. gs.hasRole('admin')
    3. g_user.hasRole('admin')
    4. g_user.hasRoleExactly('admin') Correct answer.

    Explanation

    g_user.hasRoleExactly('admin') checks for the exact role without expanding inherited roles. g_user.hasRole() considers inherited roles, and gs is server-side.

  139. Question 139Business Logic and Scripting (Client and Server Side)

    A script include is written as `var MyUtil = Class.create(); MyUtil.prototype = {...};`. What does this pattern provide?

    1. A global variable that cannot be reused
    2. A reusable class whose methods are called on instances Correct answer.
    3. Automatic client-callable access through GlideAjax
    4. A business rule that runs on insert

    Explanation

    Class.create() with a prototype defines a reusable JavaScript class in a script include. Other scripts instantiate it and call its methods on the instance.

  140. Question 140Business Logic and Scripting (Client and Server Side)

    A server-side script catches an exception and calls `gs.error('Processing failed: ' + e);`. Where does the message appear?

    1. In the system log Correct answer.
    2. In the browser developer console
    3. As an email to the record's caller
    4. As an info message on the form

    Explanation

    gs.error() writes an error-level entry to the system log. It does not display a form message or write to the browser console.

  141. Question 141Business Logic and Scripting (Client and Server Side)

    A GlideRecord query may match thousands of records, but the script needs only the first 10. Which call limits the number of records returned?

    1. gr.query(10)
    2. gr.setLimit(10) Correct answer.
    3. gr.setMax(10)
    4. gr.limit(10)

    Explanation

    setLimit(n) restricts the query to at most n records. It should be called before query() executes.

  142. Question 142Business Logic and Scripting (Client and Server Side)

    On a form, a reference field stores a sys_id. Which client-side call returns the display value shown to the user?

    1. g_form.getDisplayValue('field') Correct answer.
    2. g_form.getValue('field')
    3. g_form.getLabel('field')
    4. g_form.getReferenceValue('field')

    Explanation

    g_form.getDisplayValue(fieldName) returns the display label for a reference or choice field. g_form.getValue() would return the underlying stored value such as a sys_id.

  143. Question 143Business Logic and Scripting (Client and Server Side)

    On the server, which GlideRecord method returns the display value of a reference field for the current record?

    1. getValue('field')
    2. getLabel('field')
    3. getReference('field')
    4. getDisplayValue('field') Correct answer.

    Explanation

    GlideRecord.getDisplayValue(fieldName) returns the display value for a field on the current record. getValue() returns the stored value, such as the sys_id for a reference field.

  144. Question 144Business Logic and Scripting (Client and Server Side)

    A client script calls `g_form.getReference('caller_id', callback);`. Which statement about the callback is correct?

    1. It runs only if the field is read-only.
    2. It runs immediately and receives a string value.
    3. It runs after an asynchronous server request and receives a GlideRecord. Correct answer.
    4. It runs only when the reference field is empty.

    Explanation

    getReference() performs an asynchronous server lookup and invokes the callback with a GlideRecord when the data returns. Code after the call cannot assume the callback has already run.

  145. Question 145Business Logic and Scripting (Client and Server Side)

    An after update business rule calls `current.setValue('state', '4')` but never calls `current.update()`. What happens to the state change?

    1. It is saved automatically because current is writable.
    2. It is saved only if the rule is asynchronous.
    3. It is not saved because after rules run after the database write. Correct answer.
    4. It triggers the same rule again until the state changes.

    Explanation

    After business rules execute after the database write, and changes made to current are not automatically persisted. A separate update call is required for the change to be saved.

  146. Question 146Business Logic and Scripting (Client and Server Side)

    During a before update event, Rule A (order 100) changes `current.assigned_to`. Rule B (order 200) then reads `current.assigned_to`. What value does Rule B see?

    1. A null value until the update completes.
    2. The value only if Rule A called current.update().
    3. The value set by Rule A, because they share the same current object. Correct answer.
    4. The original database value, because before rules are isolated.

    Explanation

    Before business rules for the same event share the same current object, so changes made by an earlier rule are visible to a later rule. Order determines which rule sees the modified value.

  147. Question 147Application Security (Roles, ACLs, Scoped Application Security)

    A developer opens an ACL record and finds the fields read-only. Which role must be elevated to edit the ACL?

    1. sn_acl_admin
    2. security_admin Correct answer.
    3. security_analyst
    4. admin

    Explanation

    Security configuration records such as ACLs are protected independently of normal administrative rights. A user must hold the security_admin role and explicitly elevate it with Elevate Roles before the ACL form becomes editable.

  148. Question 148Application Security (Roles, ACLs, Scoped Application Security)

    What is the effect of selecting the Admin overrides check box on an ACL?

    1. Admins must still satisfy the ACL's condition and script.
    2. Users with the admin role bypass that ACL. Correct answer.
    3. The ACL applies only to users with the admin role.
    4. The ACL is skipped for all users regardless of role.

    Explanation

    Admin overrides makes the ACL non-binding for users holding the admin role, so they are granted the access without meeting the condition or script. Clearing the check box forces admins through the normal evaluation.

  149. Question 149Application Security (Roles, ACLs, Scoped Application Security)

    An ACL's Roles field lists itil and sn_incident_write. A user holds only itil. What is the result of the role check?

    1. The role check passes. Correct answer.
    2. The user must also belong to a group containing both roles.
    3. The role check is skipped and only the script decides.
    4. The role check fails because both roles are required.

    Explanation

    Multiple roles on one ACL are combined with OR logic: holding any one of the listed roles satisfies the requirement. Group membership matters only as a way of inheriting roles, not as an additional condition.

  150. Question 150Application Security (Roles, ACLs, Scoped Application Security)

    A user is not assigned the itil role directly but belongs to a group that has itil. How is the user's access evaluated?

    1. Group roles apply only to records owned by that group.
    2. The user lacks itil until the role is assigned directly.
    3. The user is treated as having itil. Correct answer.
    4. The group's roles apply only after the user elevates roles.

    Explanation

    Roles are granted to a user directly or inherited through group membership, and inherited roles behave identically in ACL evaluation. No direct assignment is needed.

  151. Question 151Application Security (Roles, ACLs, Scoped Application Security)

    Which ACL operation is evaluated when a user updates an existing record?

    1. read
    2. write Correct answer.
    3. delete
    4. create

    Explanation

    The write operation governs changes to existing records, while create governs inserts, read governs viewing, and delete governs removal. A user must pass the write ACL to save an update.

  152. Question 152Application Security (Roles, ACLs, Scoped Application Security)

    An ACL contains a script. What must the script return for the ACL to grant access?

    1. true Correct answer.
    2. the record's sys_id
    3. an empty string
    4. 1 as a string

    Explanation

    An ACL script is evaluated as a boolean expression: returning true grants access and returning false denies it. Any other returned value does not grant access.

  153. Question 153Application Security (Roles, ACLs, Scoped Application Security)

    A table has a read ACL, and one field on that table has its own read ACL. What must a user satisfy to see that field's value?

    1. Either ACL, since matching one is sufficient.
    2. Only the field ACL, because field ACLs replace table ACLs.
    3. Both the table ACL and the field ACL. Correct answer.
    4. Only the table ACL, because field ACLs apply to writes only.

    Explanation

    Field-level ACLs add a further restriction rather than replacing the table-level rule, so both must pass for the field value to be visible. Field ACLs apply to reads as well as writes.

  154. Question 154Application Security (Roles, ACLs, Scoped Application Security)

    An ACL has no roles, no condition, and no script, and Requires authentication is selected. Who passes the ACL?

    1. No user, because no roles are listed.
    2. Only users with the admin role.
    3. Any authenticated user is granted access. Correct answer.
    4. Only users in the ACL's application scope.

    Explanation

    With no role, condition, or script requirements, the ACL imposes no restriction beyond the authentication check. Any logged-in user therefore passes it.

  155. Question 155Application Security (Roles, ACLs, Scoped Application Security)

    An administrator clears the Active check box on an ACL. How is that ACL treated during evaluation?

    1. The ACL is ignored during evaluation. Correct answer.
    2. It is replaced by the table's default ACL.
    3. It denies access to all users.
    4. It applies only to unauthenticated users.

    Explanation

    Inactive ACLs are skipped entirely, so any restriction they provided disappears and other applicable ACLs or platform defaults decide the outcome. This is a common cause of unintended access after a security change.

  156. Question 156Application Security (Roles, ACLs, Scoped Application Security)

    What does the Condition field of an ACL contain?

    1. A JavaScript expression that returns true or false.
    2. A comma-separated list of role names that apply.
    3. The name of the field being secured.
    4. An encoded query the record must match. Correct answer.

    Explanation

    The Condition field holds a filter, expressed as an encoded query, that is evaluated against the record being accessed. JavaScript logic belongs in the Script field instead.

  157. Question 157Application Security (Roles, ACLs, Scoped Application Security)

    A user can see a record in a list, but the Description field always appears blank. Which ACL most likely denies access?

    1. The table's delete ACL, because the record is hidden.
    2. The table's create ACL, because the record is new.
    3. The read ACL on the Description field. Correct answer.
    4. The table's write ACL, because updates are blocked.

    Explanation

    When a record is visible but an individual field shows no value, the field-level read ACL is normally blocking that value while the table-level read ACL still allows the record. Write, create, and delete ACLs do not affect display of stored values.

  158. Question 158Application Security (Roles, ACLs, Scoped Application Security)

    Role A contains Role B, and a user is assigned only Role A. Which privileges does the user receive?

    1. Only privileges granted to Role B.
    2. Neither, until Role B is assigned directly.
    3. Privileges of both Role A and Role B. Correct answer.
    4. Only privileges granted to Role A.

    Explanation

    Role containment is hierarchical: assigning a containing role conveys the privileges of the roles it contains. Direct assignment of the contained role is unnecessary.

  159. Question 159Application Security (Roles, ACLs, Scoped Application Security)

    A role named approver is created inside the scoped application with scope identifier x_acme_ops. How is the role listed when assigned to a user?

    1. acme_ops.approver
    2. approver.x_acme_ops
    3. approver (global)
    4. x_acme_ops.approver Correct answer.

    Explanation

    Roles created in a scoped application are namespaced with the application's scope identifier followed by the role name. This prevents collisions with identically named roles in other scopes.

  160. Question 160Application Security (Roles, ACLs, Scoped Application Security)

    A scoped application needs to read a table owned by another scope. How is that access granted?

    1. Cross-scope reads are permitted by default between scoped applications.
    2. The requesting scope marks the table as public in its own application record.
    3. An administrator assigns the admin role to all users of the requesting scope.
    4. The owning scope grants a cross-scope privilege to the requester. Correct answer.

    Explanation

    Cross-scope privileges are controlled by the application that owns the resource; it adds an Application Access record naming the requesting scope, resource, and operation. The requesting scope cannot grant itself access.

  161. Question 161Application Security (Roles, ACLs, Scoped Application Security)

    An application's scope record has Accessible from set to 'This application scope only'. What does this mean for other scoped applications?

    1. Cross-scope access is granted automatically to the global scope.
    2. Users without roles cannot log in to the instance.
    3. Other scopes need a privilege to use its resources. Correct answer.
    4. The application can no longer be edited in Studio.

    Explanation

    That setting makes the scope private, so resources such as tables, script includes, and roles are unavailable to other scoped applications unless a cross-scope privilege is granted. It has no effect on user login or on editing rights within the owning scope.

  162. Question 162Application Security (Roles, ACLs, Scoped Application Security)

    A Script Include in scoped app A queries a table owned by scoped app B and fails at runtime. Both scopes are private. What is the most likely reason?

    1. App A's scope has no roles defined for the table.
    2. App B's ACLs have Admin overrides selected.
    3. App B has not granted app A access to the table. Correct answer.
    4. The Script Include is missing the client-callable option.

    Explanation

    A private scope blocks other applications from using its resources until the owning scope records a cross-scope privilege for the requesting scope and table. Server-side code fails with an access error rather than returning data.

  163. Question 163Application Security (Roles, ACLs, Scoped Application Security)

    Which tool shows, during your own session, why a specific ACL granted or denied access?

    1. System Log > All messages
    2. The application scope picker
    3. Session debug > Security Correct answer.
    4. The ACL's Active field

    Explanation

    Enabling the Security option in Session Debug writes ACL evaluation detail to the session log, showing which ACLs were checked and whether each passed. It is the standard way to trace unexpected grants or denials for the current user.

  164. Question 164Application Security (Roles, ACLs, Scoped Application Security)

    A developer working in scoped app A needs to secure a table owned by scoped app B with a new ACL. What should the developer do?

    1. Rely on any scoped app being able to create ACLs on any table.
    2. Create a global ACL and set its application scope to app A.
    3. Create the ACL in app A and mark it as a cross-scope record.
    4. Create the ACL in app B's scope, which owns the table. Correct answer.

    Explanation

    ACLs are scoped records that belong to the application owning the table they protect, so the security rule must be created and maintained in that scope. A foreign scope cannot impose an ACL on another application's table.

  165. Question 165Application Security (Roles, ACLs, Scoped Application Security)

    An ACL on a table lists the itil role and a condition of Active is true. A user with itil opens an inactive record. What happens?

    1. Access is granted because the ACL has no script.
    2. Access is denied because the ACL condition fails. Correct answer.
    3. Access is denied because two roles are required.
    4. Access is granted because the user holds the itil role.

    Explanation

    Every requirement configured on an ACL must be met: the condition is evaluated against the record and, when it is false, the ACL denies access regardless of role. A script is only needed when logic cannot be expressed as a filter.

  166. Question 166Application Security (Roles, ACLs, Scoped Application Security)

    Which value in an ACL's Name field secures a single field on the Incident table?

    1. short_description.incident
    2. incident.short_description Correct answer.
    3. incident/short_description
    4. incident::short_description

    Explanation

    A field-level ACL is named with the table followed by a dot and the field name, for example incident.short_description. A Name containing only a table name creates a table-level ACL.

  167. Question 167Application Deployment, Integration, and Maintenance

    What is the primary purpose of an update set in ServiceNow?

    1. To archive the transaction logs that record deleted database rows
    2. To package configuration changes so they can be moved between instances Correct answer.
    3. To schedule the nightly cloning of a production instance
    4. To store the compiled source of all client-side scripts

    Explanation

    Update sets record changes made to customizable records in an instance and package them as XML that can be exported, retrieved, and committed on another instance. They are the standard mechanism for moving configuration between development, test, and production. They do not store logs, clones, or compiled code.

  168. Question 168Application Deployment, Integration, and Maintenance

    When a developer creates a custom application, what does the application scope provide?

    1. A unique namespace that isolates the application's artifacts Correct answer.
    2. A role that grants the application's users access to its modules
    3. A table that stores every record created by the application
    4. A scheduled job that synchronizes the application across instances

    Explanation

    Every application created in the platform is assigned a unique scope identifier, typically in the form x_vendor_name, which namespaces and isolates its scripts, tables, and other artifacts. Access to artifacts from outside that scope must be granted explicitly. Scope is not a role, a scheduled job, or a single table.

  169. Question 169Application Deployment, Integration, and Maintenance

    What is the role of a transform map in an import?

    1. It defines how often a scheduled import runs
    2. It encrypts sensitive values before they are written to the target
    3. It maps source columns to target fields for each imported row Correct answer.
    4. It stores the raw rows that were loaded from the source file

    Explanation

    A transform map links a staging table to a target table and defines, field by field, how source values are written to target fields, including scripts and coalesce behavior. Running the transform map converts staged rows into target records. Scheduling, row storage, and encryption are separate concerns.

  170. Question 170Application Deployment, Integration, and Maintenance

    Which ServiceNow feature runs automated, repeatable tests against forms, UI pages, and server-side scripts?

    1. Automated Test Framework Correct answer.
    2. Scheduled Jobs
    3. Update Set Preview
    4. Import Sets

    Explanation

    The Automated Test Framework lets developers build test suites made of steps that exercise forms, UI pages, and server-side logic, then run them on demand or as part of a pipeline. It reports pass/fail results so regressions are caught before deployment. The other features handle data loading, time-based execution, and deployment validation.

  171. Question 171Application Deployment, Integration, and Maintenance

    When is a MID Server required for an integration?

    1. When the integration must run while the instance is in maintenance
    2. When the external system is reachable only from the private network Correct answer.
    3. When the payload of the request is larger than one megabyte
    4. When the external system exposes a REST API instead of a SOAP API

    Explanation

    A MID Server is an agent that runs inside a customer's network and relays traffic between the instance and systems that are not publicly reachable, such as on-premise databases and internal APIs. It is not related to payload size, maintenance windows, or the choice of REST versus SOAP.

  172. Question 172Application Deployment, Integration, and Maintenance

    Which role is required to activate a plugin on a ServiceNow instance?

    1. import_admin
    2. admin Correct answer.
    3. itil
    4. sn_app_client

    Explanation

    Plugin activation changes the instance's schema and installed applications, so it is restricted to users holding the admin role. Other roles grant access to specific functional areas but not to plugin management.

  173. Question 173Application Deployment, Integration, and Maintenance

    Which update set state indicates that the developer has finished the work and the set can be exported or retrieved?

    1. Previewed
    2. Ignore
    3. Complete Correct answer.
    4. In Progress

    Explanation

    A local update set is marked Complete when the developer is done adding records, which makes it eligible for export or retrieval by another instance. In Progress means it is still accepting changes, and Ignore excludes it from being applied. Previewed refers to a retrieved set that has already been checked for collisions on the target.

  174. Question 174Application Deployment, Integration, and Maintenance

    Where are the rows of an import set stored immediately after a data source is loaded?

    1. In the sys_transform_map table
    2. In the target table, with a status of Pending
    3. In the sys_import_set_run table
    4. In the staging table for that import set Correct answer.

    Explanation

    Loading a data source creates an import set and writes the raw rows into a staging table, where they remain until a transform map converts them into target records. The target table is not touched until the transform runs. Transform maps and run logs are configuration and audit records, not row storage.

  175. Question 175Application Deployment, Integration, and Maintenance

    A developer edits a business rule while working in an application. Where is the change recorded?

    1. In the application's source control repository, bypassing update sets
    2. In a new update set named after the table of the edited record
    3. In the update set currently selected in the developer's session Correct answer.
    4. In the Default update set of the instance's system administrator

    Explanation

    When a customizable record is saved, the platform writes a customer update record into the update set that is current for that user's session. Each developer therefore controls which set receives their work by selecting it before making changes. Update sets are not created automatically per table, and source control is a separate, optional mechanism.

  176. Question 176Application Deployment, Integration, and Maintenance

    What is the main purpose of previewing a retrieved update set before committing it?

    1. To detect conflicts with records already present on the target Correct answer.
    2. To run the update set against production before the test instance
    3. To compress the update set XML so it transfers faster
    4. To convert the update set into a scoped application

    Explanation

    Previewing compares each record in the retrieved set with the version already on the target instance and flags collisions so the administrator can decide how to handle them. Only after reviewing the preview should the set be committed. Preview does not change packaging, environment order, or application type.

  177. Question 177Application Deployment, Integration, and Maintenance

    A global business rule must call a script include that belongs to the scope x_acme_orders. What must be configured?

    1. The script include must be copied into the global scope before use
    2. A cross-scope privilege granting the global scope access to it Correct answer.
    3. The application must be changed to the global scope before deployment
    4. Nothing; global scripts can call any scoped script include directly

    Explanation

    Scoped applications are isolated by default, so code outside the scope needs an explicit cross-scope privilege record before it can use the scoped artifact. The privilege names the target artifact and the scope allowed to reach it. Copying the script or moving the whole application would break the application's packaging.

  178. Question 178Application Deployment, Integration, and Maintenance

    What does delegated development allow an administrator to do?

    1. Assign developers to work in a specific application scope Correct answer.
    2. Publish an application to the Application Repository
    3. Let developers edit records in any scope without review
    4. Restrict developers to read-only access on production

    Explanation

    Delegated development grants named users or groups the ability to create and modify artifacts inside one application scope without giving them the full admin role. This limits the blast radius of development work while still allowing teams to build their own applications. It does not grant instance-wide editing rights or publishing rights.

  179. Question 179Application Deployment, Integration, and Maintenance

    In a scripted REST API, which element defines a URL path and the HTTP method that clients can call?

    1. A UI action on the API's table
    2. A REST message record with an HTTP method
    3. A transform map attached to the API
    4. A resource record that belongs to the API Correct answer.

    Explanation

    A scripted REST API contains one or more resources, and each resource specifies its relative path, the HTTP method it accepts, and the server-side script that handles the request. Clients reach the resource through the API's namespace, API ID, and version plus the resource path. REST messages are for outbound calls, and transform maps and UI actions play no role here.

  180. Question 180Application Deployment, Integration, and Maintenance

    What is the recommended way for an outbound REST integration to authenticate to a third-party system?

    1. Add the remote user's password to the query string of every request
    2. Enable the REST API plugin on the third-party server
    3. Trust the instance's IP address on the third-party firewall
    4. Use a credential record referenced by the REST message Correct answer.

    Explanation

    Credentials should be stored in a credential record, connection alias, or authentication profile and referenced by the REST message's HTTP method, so secrets are encrypted and never appear in code or logs. Query strings and scripts are visible to anyone who can read the configuration. Firewall trust and plugins on the remote system do not authenticate the caller.

  181. Question 181Application Deployment, Integration, and Maintenance

    In IntegrationHub, what is a spoke?

    1. A packaged set of actions for one third-party system Correct answer.
    2. A table that stores inbound payloads from external systems
    3. A MID Server cluster dedicated to one integration
    4. A scheduled job that polls an external system for changes

    Explanation

    A spoke is a store-installable package that supplies prebuilt actions, subflows, and connection configuration for a specific third-party product. Flow designers reuse those actions instead of writing custom scripts for each call. Spokes are not scheduled jobs, network infrastructure, or storage tables.

  182. Question 182Application Deployment, Integration, and Maintenance

    Which field mapping setting causes an existing target record to be updated instead of a new one inserted?

    1. Choice action
    2. Source script
    3. Reference qualifier
    4. Coalesce Correct answer.

    Explanation

    Marking a field map as coalesce tells the transform to search the target table for a record matching the incoming value; if one is found, that record is updated rather than a duplicate being inserted. Multiple coalesce fields combine to form the match key. Choice actions, source scripts, and reference qualifiers control values, not record matching.

  183. Question 183Application Deployment, Integration, and Maintenance

    Which statement correctly distinguishes retrieving an update set from committing it?

    1. Retrieving applies the changes; committing copies the set to production
    2. Retrieving backs out the changes; committing restores them
    3. Retrieving validates the records; committing exports them to XML
    4. Retrieving copies the set into the instance; committing applies its changes Correct answer.

    Explanation

    Retrieval pulls the update set XML from another instance into the target instance's Retrieved Update Sets list, where it can be previewed. Committing is the step that actually writes the records into the target instance. Export creates the XML, and back out reverses a previously committed set.

  184. Question 184Application Deployment, Integration, and Maintenance

    A change was captured in the wrong update set and no other changes exist in that set. What is the recommended fix?

    1. Move the record to the correct update set with the Move to Update Set link Correct answer.
    2. Clone the incorrect update set and commit both sets together
    3. Export the incorrect set and import it into the correct one
    4. Delete the record and repeat the change while the correct set is current

    Explanation

    The platform records each captured change as a customer update record, and that record can be reassigned to a different update set using the Move to Update Set related link. This preserves the change without rework and keeps the deployment package clean. Repeating the edit or shuffling the whole package risks duplicate or unintended records.

  185. Question 185Application Deployment, Integration, and Maintenance

    Which configuration determines how an email received by the instance becomes or updates a record?

    1. An outbound REST message with a POST method
    2. An inbound email action with a condition and a script Correct answer.
    3. A scheduled flow that reads the POP3 mailbox
    4. A notification record with a mail script

    Explanation

    Inbound email actions evaluate the received message against their conditions and then run the associated script to create or update the appropriate target record. Notifications handle outbound messages, so they play no part in processing incoming mail. Outbound REST messages and mailbox polling flows are different mechanisms entirely.

  186. Question 186Application Deployment, Integration, and Maintenance

    What does the ServiceNow Application Repository let a developer do?

    1. Publish a custom scoped application for others to install Correct answer.
    2. Automatically upgrade store applications on a schedule
    3. Run automated tests on a scoped application before release
    4. Merge two instances' update sets into one deployment

    Explanation

    The Application Repository is the distribution point where a developed scoped application is published so that other instances or customers can install and later upgrade it. Installation and upgrades are performed from the store, not by merging update sets. Testing is handled by the Automated Test Framework.

  187. Question 187Application Deployment, Integration, and Maintenance

    During commit, an update set record collides with a record that was modified on the target instance after the update set was exported. What does the platform do by default?

    1. Cancels the commit and rolls back all previously applied records
    2. Writes the update set's version of the record over the target record Correct answer.
    3. Merges both versions field by field and keeps the newest value
    4. Skips the record and leaves the target record unchanged

    Explanation

    The preview flags the record as a collision, but the commit itself applies the version carried in the update set, overwriting whatever is on the target. That is why a careful preview and an explicit decision to skip individual records matter before committing. There is no field-level merge and no automatic rollback of the whole set.

  188. Question 188Application Deployment, Integration, and Maintenance

    A team wants to add its own fields to a table that belongs to another scoped application. What is the supported approach?

    1. Create a database view that adds virtual columns to the table
    2. Extend the target table with a new table in their own scope Correct answer.
    3. Add the fields and save the record while impersonating an admin
    4. Unlock the table's scope and add the fields directly to the table

    Explanation

    Adding fields to another application's table would modify that application's records and be lost or blocked on upgrade. The supported pattern is to create a table in your own scope that extends the target table, so the new fields live in your application while inheriting the parent's structure and records. Database views are read-only, and impersonation does not change scope rules.

  189. Question 189Application Deployment, Integration, and Maintenance

    What is the purpose of an update set batch?

    1. To split one large update set into several smaller sets automatically
    2. To run unit tests against all update sets in an instance
    3. To archive completed update sets after they are committed
    4. To group related update sets so they can be moved together Correct answer.

    Explanation

    An update set batch collects multiple related update sets so they can be exported, retrieved, and committed as one unit, which keeps dependent changes together. Sets in a batch retain their individual identities but travel as a package. Batching does not split, test, or archive update sets.

  190. Question 190Application Deployment, Integration, and Maintenance

    On a domain-separated instance, which records can a user in the domain Acme see?

    1. Records in Acme and in every sibling domain at the same level
    2. Only records whose domain exactly matches Acme
    3. Records in any domain, because domain separation only filters reports
    4. Records in Acme and in any child domains beneath Acme Correct answer.

    Explanation

    Domain separation filters data along a domain hierarchy: a user can see records in their own domain and in all domains that descend from it. Sibling domains and parents are outside that visibility. The filtering applies to record access generally, not only to reports.

  191. Question 191Application Deployment, Integration, and Maintenance

    A scripted REST API has namespace x_acme, API ID orders, version v1, and a resource path /items. What URL path reaches that resource?

    1. /x_acme/api/orders/items/v1
    2. /api/orders/x_acme/v1/items
    3. /api/v1/x_acme/items/orders
    4. /api/x_acme/orders/v1/items Correct answer.

    Explanation

    Scripted REST API URLs follow the pattern /api/<namespace>/<api_id>/<version>/<resource_path>, so the namespace comes first after /api, followed by the API ID, the version, and the resource path. Mixing the order of the API ID and namespace, or placing the version elsewhere, produces an endpoint that does not resolve.

  192. Question 192Application Deployment, Integration, and Maintenance

    An administrator needs to create a development instance that contains the same configuration and data as the production instance. Which feature is designed for this task?

    1. System Clone Correct answer.
    2. Update Set retrieval
    3. Instance Scan
    4. Import Set transform

    Explanation

    System Clone copies the database of a source instance into a target instance, carrying over both configuration records and business data. It is the standard mechanism for refreshing sub-production instances from production, and clone profiles control what is preserved or excluded. Update sets and import sets move only selected records, not a full copy of the instance.

  193. Question 193Application Deployment, Integration, and Maintenance

    What is the primary purpose of Instance Scan?

    1. It runs a set of checks against the instance configuration and reports findings such as best-practice deviations. Correct answer.
    2. It compiles and executes Automated Test Framework suites automatically after every deployment.
    3. It exports application files so that they can be imported into a different instance.
    4. It compares record counts between two instances to validate a completed clone.

    Explanation

    Instance Scan executes scan checks, grouped into suites, against an instance to surface issues such as misconfigurations, inactive records, and deviations from best practice. Results guide remediation and are commonly reviewed before an upgrade or after a clone. It does not move data between instances or execute functional test cases.

  194. Question 194Application Deployment, Integration, and Maintenance

    An outbound REST integration must call an API hosted on a server inside a private network that is not reachable from the internet. What must the administrator configure?

    1. Register the private host in the instance's outbound IP allow list.
    2. Configure a VPN tunnel directly on the REST message record before sending.
    3. Attach a MID Server with the required capabilities and select it on the REST message. Correct answer.
    4. Create an ACL that grants the integration user access to the private subnet.

    Explanation

    When a target endpoint is only reachable from inside the corporate network, the request must be proxied by a MID Server deployed there. The REST message supports this by enabling MID Server use and specifying the MID Server or MID selection and required capabilities. Allowing an IP address or changing ACLs does not give the cloud instance network reachability to a private host.

  195. Question 195Application Deployment, Integration, and Maintenance

    A development team wants to group related Automated Test Framework tests so they can be executed together and reported as a single unit. Which construct provides this?

    1. A single assertion record that stores the expected result for all tests.
    2. A CI/CD pipeline stage definition inside the application record.
    3. A test suite that contains the test cases to be run in order. Correct answer.
    4. A client test runner script that records the team's browser interactions.

    Explanation

    A test suite is a container that references multiple test cases, allowing them to be executed in sequence as one run with combined results. Test cases hold the individual steps and assertions, while suites provide the grouping and reporting unit. This lets a team validate a whole feature area with a single execution.

  196. Question 196Application Deployment, Integration, and Maintenance

    An administrator creates an update source record on a sub-production instance. What does this configuration enable?

    1. The instance can retrieve update sets automatically from a designated parent instance. Correct answer.
    2. The instance can authenticate to an external Git repository for source control.
    3. The instance can schedule recurring clones from the production instance.
    4. The instance can push its own update sets to a designated child instance.

    Explanation

    An update source record stores the connection details, such as the instance URL and credentials, of another instance that holds update sets to be pulled down. Once configured, update sets can be retrieved on demand or on a schedule, which is typical in a parent-to-child deployment model. It is a pull mechanism for inbound update sets, not a push or clone mechanism.

ServiceNow CAD flashcards

33 cards. Read the term and the definition here. The deck at the top of this page is optional.

Scoped application namespace
A scoped app's artifacts carry a unique prefix such as x_acme_orders; the scope isolates its tables, scripts, roles, and properties from all other applications in the instance.
Update set
A container recording configuration changes made in the global scope; changes are stored as XML records in sys_update_xml and moved between instances by export and retrieve.
sys_db_object
The system table storing one row per table in the database, holding the table name, label, and parent (extends) reference used by the data dictionary.
Instance hierarchy
Development, test, and production instances; sub-production instances are typically created by cloning production so that configuration and data mirror the live system.
Role
A record in sys_user_role that bundles permissions; roles are assigned to users directly through sys_user_has_role or inherited through group membership.
Table extension
When a table extends another it inherits all parent fields; each row is stored in the child table, while a query on the parent returns parent and child rows.
Reference field
A field type storing the sys_id of a record on another table, creating a one-to-many relationship and enabling dot-walking into that record's fields.
sys_dictionary
The dictionary table holding one row per field, defining its type, maximum length, default value, reference table, and choice list for each column.
Choice field
A drop-down field whose stored value differs from its display label; the value and label pairs come from the dictionary or from sys_choice records.
Many-to-many table
A table with two reference fields linking two other tables, such as sys_user_grmember linking users and groups; each row represents one association.
sys_id
A 32-character globally unique identifier automatically assigned as the primary key of every record on every table across the entire platform.
Database index
A structure on one or more columns that speeds query conditions on those columns; created in sys_index and used when the field appears in a filter.
UI policy
A client-side rule that conditionally makes form fields mandatory, visible, or read-only; Run scripts enables script actions and Reverse if false restores state.
Data policy
A server-side rule enforcing mandatory or read-only fields across every entry channel, including forms, imports, and web services, independent of the browser.
onCellEdit client script
A client script that fires when a cell is edited directly in a list, using g_form to validate or change values before the row is saved.
g_form.setMandatory
A client-side API method that makes a form field mandatory or optional at runtime; it affects only the current form and is not enforced by the server.
Dictionary override
A record that changes a field's dictionary behavior, such as mandatory or default value, for one child table without affecting the parent table.
Form view
A named layout stored in sys_ui_view that presents a different arrangement of sections and fields for the same table to different audiences.
Before business rule
A server-side rule running before the database write, so changes made to current.field are saved with the record without calling update().
After business rule
Runs after the database write; changes to current require an explicit current.update(), which can trigger recursion and should be guarded with setWorkflow(false).
GlideAjax
A client-side class that asynchronously calls a client-callable script include on the server and returns values to a client script without reloading the page.
GlideAggregate
A server-side class performing count, sum, average, min, max, and groupBy queries in the database, avoiding the cost of looping through individual GlideRecord rows.
Async business rule
A business rule that runs in a separate background job after the originating transaction, used for slow or non-critical work that must not block the user.
Script include
A reusable server-side JavaScript class stored on the platform; on-demand functions run only when called, and client-callable ones extend AbstractAjaxProcessor.
ACL
An access control list record in sys_security_acl that grants or denies an operation on a table, field, or endpoint for specified roles and conditions.
Field ACL
An ACL protecting a single field for read or write; access is granted only when the field ACL and any matching table ACL both pass.
Cross-scope privilege
A record granting a scoped application access to another scope's tables or scripts, required because scoped applications are isolated from each other by default.
security_admin role
An elevated role a user must activate to create or modify ACLs; it is granted to admins but enabled per session through the Elevate Roles dialog.
Role containment
A relationship in sys_user_role_contains where one role automatically includes all permissions of another role it contains, simplifying role administration.
Coalesce
A transform map setting naming fields whose values must match an existing target record; a match updates that record, and no match inserts a new one.
Update set commit
The step that applies a retrieved update set's XML records to the target instance after preview; collisions and errors must be resolved first.
Application repository
A versioned store for scoped applications; publishing an app pushes a version that another instance can install or upgrade, unlike update sets.
MID Server
A Java agent installed on a customer network that lets the instance reach internal systems for discovery, orchestration, and REST or SOAP integrations.

ServiceNow CAD study guide

Platform Overview and Application Design

What to know

Every ServiceNow instance is a single-tenant environment built on a shared table model: all data lives in tables, all configuration is itself stored in tables, and everything a user sees is generated from those records. As a designer you must understand application scope. A scoped application has its own sys_app record, its own prefix, and its own artifacts; a global application shares one namespace with the base system.

Know the artifacts an application owns: application menu and modules, tables and columns, forms and views, business rules and script includes, UI policies, roles, ACLs, properties, and scheduled jobs. Know that scope is chosen when the application is created and is painful to change later, so decide early.

Traps

  • Assuming a scoped application can freely read and write global tables, or that global code can freely call scoped script includes. Cross-scope access must be granted; private script includes are not callable from other scopes unless their access is set to public.
  • Confusing update sets with source control, or assuming an update set carries data records. Update sets carry configuration metadata.
  • Designing for a single instance instead of designing portable artifacts that can be published and installed elsewhere.
  • Forgetting that new custom tables need a prefix, a display value, and access controls before they are usable.

Worked example / rule of thumb

Before opening Form Designer, answer four questions: What scope, what table, who may read or write, and how will this ship? If the answer to the last question is 'it must be reusable or sold', build it in a scoped application with a unique prefix and its own menu.

Rule of thumb: configuration over customization - prefer tables, forms, flows, and properties to scripts, and keep custom code inside the application that owns it.

Data Model and Database Design

What to know

ServiceNow models data as tables containing records containing fields. A table is defined in sys_db_object; its columns are defined in sys_dictionary. Every record has a unique 32-character sys_id, a number (from a number sequence) if enabled, and standard audit fields such as sys_created_on and sys_updated_by.

Understand column types and choose deliberately: string, integer, choice, reference, glide_list, date/time, and journal. Choices live in sys_choice and store a value plus a label; reference fields store the sys_id of a record on another table. A dependent field (for example Subcategory on Category) requires its controlling field to supply matching choice values.

Understand table extension vs reference. Extension creates an is-a relationship: Incident extends Task, inheriting every Task column and business rule, and adding an inherited-only view. You cannot delete an inherited column from the child. Reference creates a has-a relationship where the target records exist independently.

Many-to-many relationships use an intermediate m2m table (for example sys_user_grmember). Add database indexes on columns used in frequent query filters, and use coalesce fields on transform maps to prevent duplicate inserts.

Traps

  • Deleting a column deletes its data permanently, and deleting a column inherited from a parent is not allowed.
  • Confusing choice values with labels; filters and scripts compare against the value.
  • Assuming a reference field displays the sys_id rather than the target table's display value.
  • Extending a table to reuse one field, then inheriting an entire rule set you did not expect.

Worked example

Need to store a customer contact on a case? Use a reference to sys_user, not a free-text name. Need a new record type that shares state, assignment, and work notes with Task? Extend Task.

Rule of thumb: is-a means extend; has-a means reference.

Application User Interface (Forms, Lists, UI Policies)

What to know

A form is a composition of views, sections, and fields, saved in sys_ui_form / sys_ui_element style metadata and edited best through Form Designer. Lists are configured with list layout, list controls, and filters; related lists show child records on a form. Know the difference between a form view (role-specific layouts such as Default or Mobile) and a list view.

UI policies are client-side rules that change a field's mandatory, visible, or read-only state when a condition is met. Key attributes: the short description, the conditions, the order, the 'on load' checkbox, and Reverse if false - when checked, actions are undone if the condition later becomes false; when unchecked, the applied state sticks. UI policy actions target a field and a state.

Data policies look similar but are enforced server-side: mandatory and read-only are enforced for API, import, and form submissions. They also have 'reverse if false' semantics and an error message.

Client scripts (onLoad, onChange, onSubmit, onCellEdit) run after UI policies on form load, which is why a UI policy may appear to be overridden by an onLoad script that changes the same field. Server-side ACLs are evaluated before the form renders; UI policies cannot grant access, only presentation.

Traps

  • Believing a UI policy protects data. It does not; a savvy user or integration can still write the field.
  • Forgetting Reverse if false, then wondering why a hidden field stays hidden after the condition changes.
  • Expecting a data policy to change the visual appearance of a form.
  • Using an onChange client script for something a one-line UI policy already handles.

Worked example

Show and require 'Justification' when Priority is 1: create a UI policy with condition [Priority][is][1], an action setting Justification to Visible, another setting it Mandatory, and check Reverse if false and On load.

Rule of thumb: presentation in UI policies, enforcement in data policies and ACLs.

Business Logic and Scripting (Client and Server Side)

What to know

Server-side logic lives in business rules (sys_script). Know the four timings: before (runs before the record is written; use current.setValue() to change the record without a second update), after (record already written; use for side effects such as creating child records or notifications), async (queued, runs after the transaction, no user session), and display (runs only when a form loads and cannot persist changes). Before-query rules inject conditions into list queries; know their performance risk.

Reusable server code belongs in script includes, typically ES5-style prototypes or classes, called with new MyHelper(). GlideRecord is the data API: addQuery, addEncodedQuery, get, next, setValue, insert, update, setLimit, and getValue. Use GlideAggregate for counts and sums instead of looping, and previous in after rules to compare values.

Client-side logic lives in client scripts and UI policies: g_form, g_user, g_scratchpad, and GlideAjax calling a script include that extends AbstractAjaxProcessor. Client scripts cannot query the database directly - that is the classic exam scenario for GlideAjax.

Also know Flow Designer for orchestration and scheduled jobs for recurring work.

Traps

  • Calling current.update() inside a business rule on the current record, causing recursion and duplicate side effects.
  • Trying to use GlideRecord in a client script.
  • Assuming display business rules persist values; they do not.
  • Forgetting setWorkflow(false) when you do not want notifications or flows triggered.
  • Assuming an async rule can read the user's session or g_scratchpad.

Worked example

Auto-assign a group on insert: before-insert business rule with condition Assignment group is empty, script current.setValue('assignment_group', <sys_id>);. The write happens as part of the same insert - no extra update.

Rule of thumb: change the record before, react to the record after.

Application Security (Roles, ACLs, Scoped Application Security)

What to know

Access is layered. Roles (sys_user_role) grant permissions and are assigned directly to users or inherited through groups. Roles may contain other roles. Users, groups, and roles are combined in ACLs; group membership is the preferred way to grant a role at scale.

ACLs (sys_security_acl) are the enforcement point. Each ACL names a table or field, an operation (read, write, create, delete, or a UI/process operation), and a rule. The name follows table.field for fields, table.* for every field on a table, and *.field for a field on every table. An ACL can require one or more roles, a condition (declarative), or a script that returns true or false. When a condition is defined it is evaluated and the script is not used. Deny unless permitted.

Evaluation is most-specific-first: a field ACL overrides a table-level ACL; if the field ACL passes, the table read check is still applied for record access. Read ACLs also filter list queries, which is why a restricted user sees fewer rows rather than error messages. Admins bypass ACLs unless the High Security plugin is enabled, which forces admins through evaluation.

Scoped application security adds another layer: cross-scope access must be allowed, script includes are private by default, and tables carry an application access setting. Use the debug security tools to see which ACL allowed or denied an operation.

Traps

  • Assuming admin always bypasses ACLs (not with High Security enabled).
  • Granting a role to a user directly when a group would scale better.
  • Thinking a condition and a script are both evaluated in one ACL.
  • Assuming an ACL with no roles and no condition grants access; it does not.
  • Overlooking that field-level write ACLs also require table-level write access.

Worked example

Restrict salary on the user record: create a read ACL on sys_user.salary requiring role payroll_reader. Only that role sees the value; other users see the field masked, and the record itself remains readable.

Rule of thumb: least privilege, granted through groups, enforced with ACLs named table.field.

Application Deployment, Integration, and Maintenance

What to know

Update sets (sys_update_set) capture configuration changes as customer update records. Know the lifecycle: work in a named update set, complete it, export or retrieve it in the target instance, preview to see conflicts, then commit. Batches group update sets. Skipped records appear during preview or commit when an artifact is missing or a newer version exists, and must be investigated rather than ignored. Update sets do not carry transactional data, and some system properties are not captured.

Application deployment for scoped apps uses the application repository or app publishing: publish a version, install it in the target instance. Source control integration and CI/CD pipelines move applications between instances. Cloning copies production configuration and data over a sub-production instance and is a maintenance routine, not a deployment mechanism.

Integration: import sets use a data source, a transform map, and coalesce fields; transform scripts (onBefore, onAfter) enrich records. REST and SOAP support both directions: outbound REST messages, inbound scripted REST APIs, and the REST API Explorer. A MID Server is required when the endpoint sits behind a firewall on-premises. IntegrationHub and Flow Designer provide no-code actions.

Maintenance: upgrade skipped records must be reviewed after every family upgrade; instance scan and health check catch configuration drift.

Traps

  • Assuming update sets move data rows or user records.
  • Committing without previewing, then overwriting newer work.
  • Forgetting coalesce on a transform map, producing duplicates on every import run.
  • Trying to hit an internal endpoint from the instance without a MID Server.
  • Treating a clone as a way to deploy a new application.

Worked example

Moving a custom form change from dev to test: confirm the change is in the correct update set, complete it, export the XML, import in test, preview and read every skipped record, then commit.

Rule of thumb: preview before commit, coalesce before import, MID Server before on-prem.

ServiceNow CAD cheat sheet

Quick reference

Platform Overview and Application Design

  • A scoped application stores its artifacts under a unique namespace prefix (for example x_acme_orders); its tables, scripts, roles, and properties are isolated from other scopes.

  • The application scope is chosen when the application is created and cannot be changed afterward, so scope selection is a one-time design decision.

  • Custom tables created in the global scope use the u_ prefix; the sys_ prefix is reserved for base-system tables delivered by the platform.

  • Update sets store configuration changes as XML records in sys_update_xml, grouped by a parent record in sys_update_set.

  • Typical instance landscape: development, then test/staging, then production; sub-production instances are usually created by cloning production.

  • A role (sys_user_role) grants permissions; roles reach users directly through sys_user_has_role or indirectly through group membership.

  • Recommended design sequence: personas and process, then data model, then forms and lists, then logic, then security, then deployment.

  • Flow Designer automates processes with triggers, actions, and flows, and is the platform's current tool for new process automation.

  • Every table has a parent chain rooted at sys_db_object, and every record carries a 32-character sys_id as its primary key.

Quick reference

Data Model and Database Design

  • Table extension: a child table inherits all parent fields, each row is stored once in the child table, and a query on the parent returns rows from parent and children.

  • Table metadata lives in sys_db_object; field metadata (type, length, reference, default) lives in sys_dictionary.

  • A reference field stores the sys_id of a record on another table and forms a one-to-many relationship; dot-walking (current.assigned_to.email) reads fields through it.

  • A choice field stores the value while displaying the label; the pairs are defined on the dictionary or as records in sys_choice.

  • One-to-many uses a reference field on the many side; many-to-many uses an m2m table with two reference fields, such as sys_user_grmember linking users and groups.

  • incident, problem, change_request, and sc_task all extend the task table, so task-level fields and business rules apply to each of them.

  • sys_user_has_role stores role grants to users and groups; sys_user_grmember links user records to group records.

  • Create a database index (sys_index) on columns that appear frequently in query conditions to reduce full table scans.

  • Number maintenance (sys_number) defines the prefix and counter that produce identifiers such as INC0010001.

Quick reference

Application User Interface (Forms, Lists, UI Policies)

  • UI policies run on the client and set fields mandatory, visible, or read-only; the Run scripts option enables script actions and Reverse if false restores the original state when the condition stops matching.

  • Data policies enforce mandatory and read-only on the server, so the rule applies to imports, web services, and mobile clients as well as forms.

  • Client script types are onLoad, onChange, onSubmit, and onCellEdit; all of them use the g_form API rather than direct DOM access.

  • g_form methods include setValue, getValue, setVisible, setMandatory, setReadOnly, addOption, clearValue, showFieldMsg, and save.

  • onCellEdit fires when a cell is edited directly in a list; onSubmit can block a save by returning false.

  • Form views (sys_ui_view) present different layouts of the same table to different audiences; the default view is used when no view is specified.

  • A dictionary override changes a field's behavior (for example mandatory or default value) for one child table without affecting the parent.

  • Related lists on a form are defined in sys_ui_related_list, and list columns are defined in sys_ui_list.

  • The Order field on a UI policy determines execution sequence when several UI policies target the same form.

Quick reference

Business Logic and Scripting (Client and Server Side)

  • Business rule types: before (modifies current in memory, no extra write), after (needs current.update() to persist changes), async (runs in a background job after the transaction), display (runs when a record is loaded for display).

  • A before business rule can assign current.field values directly and they save with the transaction; calling update() in an after rule risks recursion and should be guarded with setWorkflow(false).

  • GlideRecord pattern: addQuery or addEncodedQuery, then query(), then while (next()) with getValue and setValue, then update(), insert(), or deleteRecord().

  • GlideAggregate performs count, sum, average, min, max, and groupBy in the database and is preferred over looping GlideRecord rows.

  • GlideAjax calls a client-callable script include (extending AbstractAjaxProcessor) so a client script can run server-side logic.

  • Client scripts cannot use GlideRecord; available objects are g_form, g_user, g_list, and GlideAjax.

  • On-demand script includes run only when explicitly called; client-callable script includes must have the Client callable flag set.

  • gs utility methods include gs.info, gs.log, gs.getUserID, gs.hasRole, gs.addInfoMessage, and gs.nowDateTime.

  • Scheduled jobs and Flow Designer actions run server-side on a schedule or a record trigger, independent of any user session.

Quick reference

Application Security (Roles, ACLs, Scoped Application Security)

  • ACL types are record, field, client_callable_script_include, rest_endpoint, ui_page, and processor; operations are read, write, create, delete, and execute.

  • If no ACL matches a table or field, access is allowed by default; ACLs restrict, they do not grant by default.

  • Admins bypass ACL checks by default; clearing the Admin overrides option on an ACL makes that rule apply to admins as well.

  • An ACL script sets answer to true or false and can call gs.hasRole(), gs.getUserID(), and inspect the current record.

  • For a field read or write to succeed, any field ACL and the matching table ACL must both allow the operation.

  • Roles are defined in sys_user_role, can contain other roles through sys_user_role_contains, and can be granted to groups through sys_group_has_role.

  • A scoped application needs a cross-scope privilege (sys_scope_privilege) to read or call artifacts that belong to another scope.

  • A client-callable script include requires a client_callable_script_include ACL before a browser script can invoke it.

  • Creating or editing ACLs requires elevating to the security_admin role for the current session.

Quick reference

Application Deployment, Integration, and Maintenance

  • Update sets capture global-scope configuration; lifecycle is create, make changes, complete, export or retrieve, preview, commit, with back-out available to revert.

  • Preview reports collisions and errors before commit; updates whose parent records are missing are skipped and must be resolved manually.

  • Scoped applications deploy as versions through the Application Repository rather than through update sets.

  • Cloning copies production to a sub-production instance; clone profiles control excluded tables, preserved data, and anonymization.

  • Import set flow: data source, staging table (sys_import_set_row), transform map, target table; coalesce fields decide update versus insert.

  • A transform map can define field maps, source scripts, and onBefore and onAfter scripts; coalesce fields should uniquely identify the target record.

  • Outbound integrations use REST or SOAP messages; inbound integrations use Scripted REST APIs or import sets; a MID Server reaches systems on a customer network.

  • After a platform upgrade, skipped records appear in the upgrade history and must be reviewed and resolved manually.

  • IntegrationHub spokes and actions extend Flow Designer to third-party systems without custom scripted integration code.

ServiceNow CAD key terms

Scoped Application

A custom application built inside its own private namespace, so its tables, scripts, and logic stay isolated from other applications and from the global scope unless access is explicitly granted.

Related: Application Scope, Global Application, Cross-Scope Privilege
Application Scope

The unique namespace identifier assigned to a scoped application, for example x_acme_orders, which prefixes its tables and determines which artifacts the application owns and may call.

Related: Scoped Application, Cross-Scope Privilege
Global Application

The default scope whose artifacts any application may call or extend; changes made there are shared across the whole instance rather than isolated to one application.

Related: Scoped Application, Application Scope
Application Menu

The top-level navigation menu that groups an application's modules so users can reach its lists, forms, and dashboards from the instance banner.

Related: Module, Application Access
Module

A navigable link inside an application menu that opens a specific page, list, or record, sometimes filtered by a predefined query.

Related: Application Menu, List Control
Delegated Development

A setting that lets a non-administrator user create and edit artifacts within one specific scoped application without being given full administrative rights on the instance.

Related: Scoped Application, Role
Table

A named collection of records that share the same set of fields, stored as rows in the database; a table may extend another table or stand alone.

Related: Dictionary Entry, Table Inheritance, sys_id
Dictionary Entry

The record in the system dictionary that defines a table column, including its type, maximum length, default value, reference target, and other attributes.

Related: Table, Reference Field, Dictionary Override
sys_id

A 32-character globally unique identifier automatically assigned to every record and used as the key for lookups, reference values, and record URLs.

Related: Reference Field, GlideRecord
Reference Field

A field type that stores the sys_id of a record on another table, creating a link that renders as a clickable value and supports dot-walking to the related record.

Related: sys_id, Related List, Many-to-Many Relationship
Choice List

A field whose permitted values come from a defined set of options stored in the choice table and presented to users as a dropdown, radio buttons, or similar control.

Related: Dictionary Entry
Table Inheritance

A relationship in which a child table extends a parent table and automatically gains all of the parent's fields and behavior, as the incident table does from task.

Related: Table, Dictionary Override
Many-to-Many Relationship

A data design where two tables are joined through a third mapping table holding a reference field to each side, so many records can relate to many records.

Related: Reference Field, Table
Form Designer

The drag-and-drop interface used to arrange fields, sections, and related lists on a form for a chosen table and view, without editing layout records by hand.

Related: Related List, List Control
List Control

Configuration that determines which columns appear on a table's list, the order of those columns, and whether users may personalize the list themselves.

Related: Module, Form Designer
Related List

A list embedded on a form that shows records from another table connected to the current record, typically through a reference field pointing back to it.

Related: Reference Field, Form Designer
UI Policy

A condition-based rule evaluated in the browser that makes fields visible, mandatory, or read-only, letting developers change form behavior without writing client scripts.

Related: UI Policy Action, Client Script
UI Policy Action

A single field-level instruction attached to a UI policy, such as setting a field mandatory, hiding it, making it read-only, or clearing its value.

Related: UI Policy, Dictionary Override
Dictionary Override

A record that lets a child table change a field's label, mandatory state, read-only state, or default value without altering the parent table's dictionary entry.

Related: Dictionary Entry, UI Policy
Client Script

JavaScript that runs in the user's browser on form or list events such as load, field change, submit, or cell edit, providing immediate interactive behavior.

Related: UI Policy, GlideAjax, UI Action
Business Rule

Server-side script that runs when records are queried, inserted, updated, or deleted, executing before, after, or asynchronously from the database operation.

Related: Script Include, GlideRecord, Scheduled Job
Script Include

A reusable server-side JavaScript class that other server scripts can call and that, when marked client callable, the browser can invoke through GlideAjax.

Related: GlideAjax, Business Rule
GlideAjax

A client-side class that sends an asynchronous request to a server-side Script Include and returns the result to the browser without reloading the form.

Related: Script Include, Client Script
GlideRecord

The primary server-side API class for querying, inserting, updating, and deleting records; it runs queries, iterates result sets, and reads or writes field values.

Related: Business Rule, sys_id
GlideSystem (gs)

A server-side utility object that provides session and instance information, logging, date and number helpers, property lookups, and user role checks.

Related: Business Rule, Role
UI Action

A button, link, or context menu item on a form or list that runs client-side script, server-side script, or both when the user activates it.

Related: Client Script, Business Rule
Flow Designer

A low-code tool for building automations as flows composed of triggers, actions, and approvals, often replacing traditional workflow and simple business rule use cases.

Related: Business Rule, Scheduled Job
Scheduled Job

A record that runs a server-side script automatically at defined times or intervals, commonly used for recurring cleanup, maintenance, or data updates.

Related: Business Rule, Flow Designer
ACL

An access control rule that grants or denies read, write, create, or delete access to a table, record, or field, evaluated by a condition or a script.

Related: Role, Cross-Scope Privilege
Role

A named set of permissions assigned to users or groups; roles gate menu items, ACL evaluation, and script-level checks such as checking whether a user has the role.

Related: ACL, GlideSystem (gs)
Cross-Scope Privilege

A record that permits one scoped application to read or use a specific artifact, such as a table or script include, that belongs to a different scope.

Related: Scoped Application, ACL
Application Access

A related list on an application record that lists the roles whose users are allowed to open the application's menu and its modules.

Related: Role, Application Menu
Update Set

A container that records configuration changes made in an instance so the changes can be exported and replayed on another instance.

Related: Update Set Preview and Commit, Application Repository
Update Set Preview and Commit

The two-step deployment process in which preview compares the update set's records with the target instance and reports conflicts, and commit then applies the changes.

Related: Update Set, Application Repository
Application Repository

A central store of published applications and plugins from which instances install or upgrade apps, including custom scoped applications shared between instances.

Related: Update Set, Scoped Application
Import Set and Transform Map

A staging area that receives raw imported data plus the mapping that converts each staged row into a record on a target table, optionally coalescing onto existing records.

Related: Table, Reference Field
MID Server

An agent installed inside a customer network that lets the instance communicate with internal systems for integrations, discovery, and orchestration tasks.

Related: REST Message
REST Message

A record defining an outbound REST integration, including the endpoint URL, HTTP method, headers, query parameters, and any response processing.

Related: MID Server, Script Include
Automated Test Framework (ATF)

A platform tool for building and running automated tests of forms, UI actions, and server-side logic to confirm that changes did not break existing behavior.

Related: Update Set Preview and Commit, Flow Designer

ServiceNow CAD study plan

8 weeks · About 6 hours per week

Week 1

Business Logic and Scripting (Client and Server Side)

  • Map each scripting type (client script, UI policy script, business rule, script include, scheduled job) to its execution context, timing, and whether GlideRecord is available.

  • Distinguish before/after/async/display business rules and predict execution order for a record insert with three overlapping rules.

  • Write and debug five server-side business rules covering current/previous value comparisons, setValueBefore/setAbortAction behaviors, and gs.addInfoMessage versus gs.addErrorMessage.

  • Explain when to prefer a business rule over a client script and document three failure modes (server-only APIs on client, recursion, infinite loops).

Your checkpoint

A one-page execution-context cheat sheet plus a log of 10 hand-solved business rule ordering/behavior scenarios scored at 8/10 or better.

Week 2

Business Logic and Scripting (Client and Server Side)

  • Construct GlideRecord queries with addQuery, addEncodedQuery, addJoinQuery, OR conditions, and ordering, and translate each into the equivalent encoded query string.

  • Build a Script Include with a reusable class and call it from the client through GlideAjax, verifying the returned value on the form.

  • Implement error handling and performance hygiene: null checks on get(), setLimit on large queries, avoiding queries inside loops, and using GlideAggregate for counts.

  • Compare client-side GlideRecord, GlideAjax, and REST for a given requirement and justify the choice in writing.

Your checkpoint

A working scoped app where a form button triggers GlideAjax into a Script Include that returns a record count, recorded with a short test log and a 15-question self-quiz at 80% or higher.

Week 3

Data Model and Database Design

  • Select appropriate field types (reference, choice, glide_list, string, integer, currency, date/time) for ten stated business requirements and defend each choice.

  • Model one-to-many and many-to-many relationships, including when to use a reference field versus a task-relationship or custom mapping table.

  • Configure choice lists, dependent fields, and dictionary overrides, then verify the resulting values render correctly on forms and lists.

  • Identify the core OOB tables (task, incident, cmdb_ci, sys_user, sys_user_group, sys_user_grmember) and their inheritance paths.

Your checkpoint

A data model diagram for a custom app with at least five tables, two reference fields, one many-to-many mapping table, and a written justification of every field type.

Week 4

Data Model and Database Design

  • Apply naming conventions for tables, fields, and sys_ids, and evaluate when to extend task versus build a standalone table.

  • Configure dictionary attributes and indexes, and reason about which queries benefit from an index on a large table.

  • Demonstrate dot-walking across two reference hops in a list view and a report filter.

  • Load sample data and validate the model by running three aggregate reports that expose relationship gaps.

Your checkpoint

A built-out data model in a personal developer instance with 20+ seeded records, dot-walked list views, and a 25-question timed mixed Domain 2 and 4 quiz passed at 75% or higher.

Week 5

Application User Interface (Forms, Lists, UI Policies)

  • Configure form layout, form sections, views, and related lists for a multi-role form, and annotate which artifact controls each element.

  • Write UI policies with conditions, reverse-if-false, and scripts, then contrast them against client scripts for the same requirement.

  • Implement client scripts using onLoad, onChange, onSubmit, and onCellEdit, including g_form calls, addChoice/clearValue, and onSubmit return false validation.

  • Build list controls, filters, and a saved list view, and explain the difference between a list filter and a list collector on a form.

Your checkpoint

A configured app form with four UI policies and three client scripts, plus a 10-scenario test matrix where every scenario passes and the UI-policy-versus-client-script choice is justified.

Week 6

Application Deployment, Integration, and Maintenance

  • Assemble an update set, preview and commit it into a clean instance, and reconcile a deliberately created collision.

  • Compare update sets against source control and application publishing for promoting scoped apps, and list the artifacts each method does and does not carry.

  • Configure an inbound REST integration using a scripted REST API or REST message, and an Import Set transform for CSV data.

  • Write a deployment checklist covering scope, dependencies, demo data exclusion, and rollback.

Your checkpoint

A complete update set exported and successfully committed to a second instance with a reconciliation note, plus a one-page deployment checklist.

Week 7

Application Security (Roles, ACLs, Scoped Application Security) & Platform Overview and Application Design

  • Distinguish ACL types (record, field, table, processor, REST) and evaluate how the four ACL operations and condition/script fields interact to grant or deny access.

  • Assign roles through groups versus directly on users, and trace effective permissions for a test user with overlapping roles.

  • Configure scoped application security: application scope, cross-scope access, application roles, and the impact of the Private flag.

  • Describe the platform's core architecture components (instance, application scope, CMDB, workflow/flow, integration hub) at a level sufficient to answer design questions.

Your checkpoint

An ACL matrix covering three records across three test users, with actual test results filled in and every mismatch corrected and re-tested.

Week 8

Business Logic and Scripting (Client and Server Side) & Data Model and Database Design & Application Deployment, Integration, and Maintenance

  • Re-drill the two heaviest domains by re-attempting every previously missed question and writing the correct rationale for each.

  • Take two full-length timed practice exams and log every miss by domain and by error type (knowledge gap, misread, time pressure).

  • Close the weakest domain identified in the logs with two targeted study blocks and a re-quiz.

  • Finalize a one-page personal reference sheet limited to facts you can state without looking them up.

Your checkpoint

Two timed full-length practice exams scored 85% or higher, with an error log showing every remaining weak item either resolved or flagged for final review.

Milestones

Week 2: Can write a business rule, a client script, and a GlideAjax Script Include from scratch without notes, and correctly state where each executes.

Week 4: Data model complete and validated in a personal instance; timed 25-question Domain 2 and 4 quiz at 75% or higher.

Week 6: Update set committed cleanly into a second instance, and the UI configuration test matrix passed 10/10.

Week 8: Two full-length timed practice exams at 85% or higher with an error log showing no unresolved high-frequency misses.

ServiceNow CAD exam day

Your checklist

Government-issued photo ID

Bring the exact name-matching ID the provider requires (typically a passport or driver's license). The name on your registration must match the ID exactly - if it doesn't, fix the registration record before test day. Confirm the accepted ID list with the provider.

Second form of ID or appointment confirmation

Some delivery setups ask for a second ID or your appointment/confirmation number. Carry the confirmation email as a screenshot on your phone and in printed form. needs_review: confirm with the provider which documents are mandatory.

Test login credentials and portal URL

Know your testing-account username and password, and test that they work at least 48 hours ahead. Do not rely on a password-reset flow on exam morning.

Verified system check completed in advance

Run the provider's system/pre-check (browser or secure-browser install, webcam, microphone, bandwidth). Do this on the same machine and network you will use on exam day, not a different laptop.

Stable wired-or-strong Wi-Fi connection plus a backup

Have a fallback: mobile hotspot or a second network. Note that switching networks mid-exam may be restricted - ask the proctor before doing it.

Quiet, private, well-lit room

Clear desk, no papers, no second monitor, no phone within reach unless the proctor says otherwise. Sit with a plain wall behind you and even lighting on your face.

Charger and a fully charged device

Plug in the laptop and charge your phone (even if it stays out of reach). A battery warning mid-exam is pure distraction.

Close every other application and disable notifications

Quit chat apps, email, sync clients, and anything that pops a toast. Some secure browsers will flag or block these anyway.

Water and a light snack for after the exam

Keep them off the desk during the exam unless the proctor permits it. Hydrate beforehand rather than during.

Confirm what materials are allowed

Assume no notes, no second screen, no scratch paper, no reference tabs. needs_review: confirm with the provider whether any scratch paper or on-screen reference is permitted, and whether breaks are allowed.

Know your scoring and delivery format before you sit down

Question count, time limit, question types, and pass mark are set by the provider and can change. Read the current exam description on the certification page rather than relying on forum posts. needs_review: verify current numbers with the provider.

Plan your arrival and check-in buffer

Be logged in and ready well before your slot so identity verification and room scan do not eat into exam time. Confirm how early check-in opens with the provider.

Plan the day

72 hours before

Do a full dress rehearsal on the real machine and network: run the system check, launch the secure browser if one is required, and log in to the testing portal. Fix anything broken today, not tomorrow.

72 hours before

Re-read the official exam blueprint/domain weighting and spend your remaining study time on your two weakest domains only. No new topics this late - consolidate what you already know.

72 hours before

Resolve any registration-name mismatch, accommodation request, or scheduling change. Provider support queues are slow; three days is the realistic buffer.

72 hours before

Confirm the exact start time in your local time zone, including any daylight-saving difference from the provider's stated zone. Write it down in one place.

24 hours before

Stop studying new material. Do a light review of your own summary notes and a handful of practice items, then close the laptop.

24 hours before

Prepare and stage everything: ID out, charger packed, desk cleared, room tidied, notifications muted on all devices. Remove anything from the desk the proctor could object to.

24 hours before

Sleep a normal night. Do not cram past midnight - recall on scenario questions degrades faster than you think.

Morning of

Eat normally, avoid heavy caffeine if you are already anxious, and re-run a quick connectivity check. Confirm your phone is charged but silenced.

Morning of

Log in early, complete identity verification and the room/desk scan calmly, and have your ID face-up beside the keyboard before check-in begins.

During the test

Do a first pass answering everything you know quickly and flagging long scenario items. Never leave a question blank if the format has no penalty for guessing.

During the test

Read scenario stems for the constraint words - scope, role, 'best practice', 'first step'. Many items hinge on which of two technically valid options is the platform-recommended one.

During the test

Watch the clock at roughly the one-third and two-thirds marks and adjust pace. If you fall behind, stop reading explanations of options you have already eliminated.

During the test

Use flagged-question review time at the end, but only change an answer if you find a concrete reason. First-instinct changes under time pressure cost more than they save.

After the test

Note whatever you found hard while it is fresh - useful if you retake, and useful for your own practice. Do not discuss specific exam content with others; that is prohibited.

Rules to check

  • Bring the ID the provider specifies, with a name that matches your registration exactly. If the names differ, contact the provider before exam day; a proctor cannot waive this at the door.

  • Assume the room must be private and the desk clear. No notes, sticky notes, second monitor, phone in reach, or other people present unless the provider's rules explicitly allow it. Confirm with the provider what is permitted on the desk.

  • Do not write down, screenshot, photograph, record, or reproduce exam questions in any form. Sharing recalled content is a violation of the certification agreement and can void your result.

  • Follow the proctor's instructions immediately, including showing your workspace and ID on camera. If a proctor asks you to do something, comply first; raise a dispute with the provider afterward, not mid-exam.

  • Breaks and restroom policies vary by delivery format and are often limited or unavailable in a timed exam. Confirm with the provider in advance whether breaks are allowed and whether the clock keeps running.

  • Scoring, question count, time limit, and the passing threshold are set by the provider and change over time. Confirm current values on the official certification page; do not rely on third-party estimates.

  • If your session drops, follow the provider's reconnect procedure and contact support immediately. Do not start a second attempt or a new registration on your own - duplicate attempts can be flagged.

  • Keep the certification code of conduct in mind: no assistance, no unauthorized tools, no talking through questions. A conduct finding can result in a score cancellation rather than just a failure.

ServiceNow CAD FAQ

How many ServiceNow CAD practice questions are available?

The practice set has 196 ServiceNow CAD questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many ServiceNow CAD flashcards are available?

The flashcard set has 33 ServiceNow CAD cards. Each card shows the term and its definition.

Which topics does the ServiceNow CAD study material cover?

The ServiceNow CAD study material has 6 sections, including Platform Overview and Application Design, Data Model and Database Design, and Application User Interface (Forms, Lists, UI Policies).

What format facts does the catalog list for the ServiceNow CAD exam?

The catalog lists these item types: multiple choice for the ServiceNow CAD exam.