Free ServiceNow CAD Exam Flashcards

A scoped app is a ServiceNow application with its own namespace and application files. Scope separates app artifacts from global changes and helps control cross-application access.

Use a declarative feature when the platform can meet the requirement through configuration, such as UI policies, flows, form settings, or ACLs. Script is for logic that configuration cannot express cleanly.

App Engine Studio is a guided workspace for building apps, tables, experiences, logic, and data models with low-code tools. It is useful for creating scoped apps without starting from raw platform lists.

Extend Task when the app needs task-like behavior such as assignment, state tracking, activity history, comments, or work notes. Extension reuses platform behavior instead of rebuilding it.

An application file is a record that belongs to an app, such as a table, form, business rule, script include, module, flow, or ACL. These files are what get moved, installed, or source-controlled.

Roles grant permissions and are commonly assigned through groups. They can control navigation visibility, form behavior, and access checks, but data access still depends on ACLs.

Group assignment is easier to maintain. Users inherit the role through group membership, so onboarding, offboarding, and access changes happen in one place.

A table ACL controls whether a user can perform an operation such as read, create, write, or delete on records in a table. It enforces access even if the user can see a menu or module.

A field ACL controls access to a specific field. A user may be able to read the record but still be blocked from seeing or updating sensitive fields.

Module roles control whether navigation appears. ACLs control whether the user can access the underlying records or fields. Hiding a module is not a security substitute.

Application access controls how other scopes can interact with an app's tables and artifacts. It helps limit cross-scope reads, writes, creates, deletes, and web service access.

Client scripts run in the browser, so users can inspect them. Sensitive logic, credentials, and privileged checks belong on the server behind ACLs or server-side APIs.

An application menu is the top-level navigation container for an app. It groups modules so users can find the app's records, pages, and tools.

A module is a navigation link under an application menu. It can open a list, form, URL, report, or other target, often filtered for a specific user workflow.

A view controls which fields and layout are shown for a form or list. Views tailor the interface for roles, tasks, or contexts without changing the underlying table.

Use a UI Policy for conditional form behavior such as making a field mandatory, read-only, or visible based on field values. It is declarative and avoids unnecessary script.

Use a Client Script for browser-side behavior that needs logic beyond a UI Policy, such as dynamic messages or calculations. It should not enforce security or trusted server logic.

A related list shows records connected to the current record, usually through a reference or relationship. It helps users review child records or associated activity without leaving the form.

A dictionary entry defines field-level metadata such as field type, label, max length, default value, reference target, and attributes. It shapes how data is stored and displayed.

A reference field stores a link to a record on another table. It supports relationships, dot-walking, display values, and lookups without duplicating the referenced data.

Dot-walking accesses fields on a referenced record, such as showing a caller's department from an incident. It is useful, but too much dot-walking can make queries and forms slower.

Use a choice field when the valid values are a controlled list, such as status or priority. It improves consistency and makes reporting easier.

A many-to-many table links records from two tables when either side can have multiple related records. It avoids forcing repeated data into one record.

A database view combines fields from multiple related tables for reporting or read-style access. It is not the same as a form or list view.

An import set is a staging table used to load external data before transforming it into target tables. It lets you validate and map data before changing production records.

A transform map maps fields from an import set to a target table and controls how incoming records are inserted, updated, or ignored.

Coalescing identifies whether an incoming row matches an existing target record. If a match is found, the record is updated; otherwise a new record can be inserted.

A Business Rule is server-side logic that runs when records are displayed, inserted, updated, deleted, or queried. It is used for trusted automation tied to database activity.

A before Business Rule runs before the database operation is committed. Use it to validate data or set field values before the record is saved.

An after Business Rule runs after the record is saved. Use it for logic that depends on the committed record, such as creating related records or starting follow-up work.

Use async logic for work that can happen after the user transaction, such as non-urgent integrations or heavy processing. It helps keep the form save responsive.

A display Business Rule runs before a form is sent to the browser and can add server-side data to the scratchpad for client scripts.

Flow Designer automates workflows with triggers, actions, approvals, and integrations. It is a low-code choice for process automation that should be readable by admins and builders.

An event records that something happened and can trigger notifications, scripts, or other processing. Events decouple the trigger from the work that responds to it.

A notification condition decides when a message should be sent. It keeps emails or alerts tied to the right record events, recipients, and business rules.

A Script Include stores reusable server-side JavaScript. Use it to centralize logic that multiple business rules, flows, or server scripts need.

GlideAjax lets client scripts call approved server-side Script Include methods. It is useful when the browser needs server data without exposing server logic.

Duplicated logic is hard to test and easy to change inconsistently. Shared behavior should move into a Script Include or reusable flow/action when appropriate.

An update set captures configuration changes so they can be moved between instances. It is commonly used for admin and configuration work, not for every type of data record.

Review captured changes, remove unrelated updates, test the behavior, and make sure dependencies are included. Clean update sets reduce deployment surprises.

Source control stores app files in a Git repository so teams can version, compare, branch, and recover application changes outside the instance.

The application repository is used to publish and install application versions between instances. It supports a managed app lifecycle beyond one development instance.

Versioning creates a clear installable release. It helps downstream instances know what changed and supports rollback, support, and dependency tracking.

It occurs when one application scope tries to use a resource from another scope without permission. Resolve it through deliberate application access and cross-scope privilege configuration.

Delegated development grants selected users development permissions for a scoped app without making them full administrators. It supports safer team-based app building.

Testing confirms that forms, ACLs, data logic, flows, and integrations work together in the target workflow. It catches scope, dependency, and permission problems before release.

Check when it runs, its condition, the target table, the current and previous values, and any script output. Many errors come from timing or conditions, not the script alone.

Direct production edits can bypass testing, capture unrelated changes, and make rollback difficult. CAD work should use a controlled lifecycle through development and test environments.

Configuration defines how the app works, such as tables, forms, rules, and flows. Data is the business content stored in those structures, such as user-created requests or records.

Use Flow Designer for readable process automation and common integrations. Use script when the requirement needs precise server-side logic that low-code actions cannot express well.