Sign in
Home/ServiceNow/ServiceNow Certified Application Developer (CAD)/Free questions

ServiceNow Certified Application Developer (CAD) — Free Practice Questions

10 free sample questions from a bank of 234, with the correct answers and explanations. No signup required — start practising right now.

1Which of the following statements is true for the Form Designer? a) To add a field to the form layout, drag the field from the Fields tab to the desired destination on the form. b) To create a new field on a form's table, drag the appropriate data type from the Field Types tab to the form and then configure the new field. c) To remove a field from the form layout, hover over the field to enable the Action buttons, and select the Delete (X) button. d) To add a section to the form layout, drag it from the Field Types tab to the desired destination on the form.
  • a, b, c, and d
  • b, c, and d
  • a, b, and d
  • a, b, and c
Answer: D

The short version

D — a, b, and c are true and d is false. Form Designer uses the Fields tab for existing fields, the Field Types tab for brand-new fields, and the X control only removes layout placement while the section claim in d misstates the source tab.

Key concepts in this question

  • Fields tab: Shows existing dictionary fields for the form table so builders can drag a ready-made field onto the layout.
  • Field Types tab: Provides data-type widgets that create a genuinely new dictionary field on the underlying table after labeling.
  • Layout versus dictionary removal: The Delete X control in Form Designer removes the field instance from the form view only, while dictionary deletion is separate.
  • Sections and layout containers: Sections organize form content into collapsible groupings and are added via section controls, not data types.

Why D is correct

D selects statements a, b, and c together and leaves out d. Statement a holds because Fields dragging preserves definitions. Statement b holds because Field Types extends schema. Statement c holds because X clears placement, so a plus b plus c is option D.

Why the others are wrong

  • A. Includes all four statements, but d is incorrect because sections are not created from the Field Types tab, so all-of-the-above cannot hold.
  • B. Selects b, c, and d while omitting a, yet a is plainly correct since Fields tab dragging is the primary way to add existing fields to a layout.
  • C. Selects a, b, and d while omitting c, yet c is correct because the X control is the documented way to remove a field from the layout without deleting dictionary data.

CAD exam tip

Remember placement versus schema: Fields tab moves placement, Field Types tab creates schema, X clears placement, and sections never come from a data-type palette.

2Which of the following features are available to Global applications? (Choose two.)
  • Automated Test Framework
  • Source Control
  • Delegated Development
  • Flow Designer
Answer: A, D

The short version

AD — Automated Test Framework and Flow Designer are available in Global. Delegated Development and source model limits do not change that settled pair, and Global keeps platform-wide automation plus testing while staying distinct from true scoped-app tooling.

Key concepts in this question

  • Global application scope: the default platform scope that holds cross-cutting configuration, shared logic and out-of-box tables, with broader feature access but weaker isolation than a scoped app.
  • Automated Test Framework: platform test runner for repeatable functional tests of forms, lists and flows, useful in Global because tests often exercise core tables and navigation.
  • Flow Designer: declarative process automation with flows, subflows, actions and triggers, explicitly supported in Global so admins can automate core processes without a custom scope.
  • Delegated limits: delegated development is scoped-only and never applies to Global.

Why AD is correct

ATF runs in Global so core tables and UI can be tested where they live. Flow Designer is likewise available in Global for core tables such as Incident. The settled key stays A and D because Delegated Development is scoped-only.

Why the others are wrong

  • B. Source Control history is nuanced and Global support arrived later, so it is not part of the settled two-answer key for this exam version.
  • C. Delegated Development only works with true scoped apps, letting admins carve out file types and script access, so it can never be a Global feature.

CAD exam tip

Remember Global equals ATF plus Flow, scoped equals Delegated Development, and Source Control timing is the classic distractor on this question.

3What plugin enables the Guided Application Creator?
  • com.glide.sn-guided-app-creator
  • com.glide.service_creator
  • com.glide.snc.apps_creator
  • com.snc.apps_creator_template
Answer: A

The short version

A — com.glide.sn-guided-app-creator is the Guided Application Creator plugin. It is active by default and the activation record names that exact plugin ID, so the other service-creator style IDs are distractors.

Key concepts in this question

  • Guided Application Creator: step-by-step wizard for scoped apps that creates tables, roles, modules and sample data from one guided flow.
  • Plugin identity: every platform capability is gated by a plugin ID, and the exam expects the literal ID rather than a paraphrase of its purpose.
  • com.glide.sn-guided-app-creator: the documented activation ID for Guided Application Creator, listed under Activation Information in product docs.
  • Look-alike IDs: nearby strings with service_creator or apps_creator fragments test whether you memorized the exact sn-guided-app-creator suffix.

Why A is correct

Product documentation places com.glide.sn-guided-app-creator under Activation Information for Guided Application Creator and states it is active by default in the Now Platform. The vendor prose quotes that same sentence from the Tokyo docs, leaving no room to prefer the shorter or template-flavored alternatives. Selecting the precise ID proves you know where the wizard comes from and how to verify activation on an instance.

Why the others are wrong

  • B. com.glide.service_creator is a plausible but incorrect fragment that does not match the documented Guided Application Creator activation record.
  • C. com.glide.snc.apps_creator adds an snc prefix seen in other artifacts but is not the published plugin ID for this wizard.
  • D. com.snc.apps_creator_template sounds like a template artifact rather than the enabling plugin, and docs never list it as the activator.

CAD exam tip

Memorize sn-guided-app-creator as one chunk, and recall that GAC is on by default so activation questions are pure ID recall.

4Which of the following can be an external data source for a ServiceNow application?
  • Microsoft Excel File
  • Data provided by a public web service using SOAP or REST
  • CSV file
  • All of the above
Answer: D

The short version

D — all listed sources can feed a ServiceNow application. Excel files, public SOAP or REST web services, and CSV files are each documented patterns for bringing outside data into scoped tables through imports or direct integration.

Key concepts in this question

  • External data source: Any system or file outside the instance that supplies records for import, synchronization, or on-demand lookup by the application logic.
  • File imports: File formats such as Excel and CSV load through import sets with field maps and coalesce matching.
  • Web service integration: SOAP and REST endpoints are consumed through messages, IntegrationHub, or scripted calls.
  • Application data strategy: Builders combine file loads for seed data with service calls for freshness.

Why D is correct

D states all of the above, which matches platform capability because each choice describes a supported ingestion path. Excel and CSV use the import engine with transforms and coalesce. SOAP and REST use endpoints with credentials. Since all paths are valid, the inclusive answer is complete.

Why the others are wrong

  • A. Excel alone is too narrow because the platform also ingests CSV and live web-service payloads, so a single-format answer misses supported paths.
  • B. SOAP or REST alone is too narrow because file-based seeding through Excel and CSV remains a core application technique alongside services.
  • C. CSV alone is too narrow because Excel workbooks and remote service calls use equally supported import and integration frameworks.

CAD exam tip

When you see Excel, CSV, and SOAP plus REST together, think all-of-the-above: files seed data, services keep it live.

5Which one of the following is true for the Application Picker and Application Scope?
  • Global is a reserved application which does not appear in the Application Picker
  • Selecting an application from the Application Picker does not set the Application Scope
  • Selecting an application from the Application Picker sets the Application Scope
  • Selecting Global in the Application Picker sets the Application Scope to Incident
Answer: C

The short version

C — Picking an app in the Application Picker sets the Application Scope. Scope context follows selection, so developers create and edit artifacts in the intended application rather than accidentally writing into Global.

Key concepts in this question

  • Application Picker: header control that shows the current application and lets developers switch between Global and scoped apps.
  • Application Scope: runtime and design-time boundary that determines which artifacts are edited and how cross-scope access is enforced.
  • Scope context: the session-level setting established by the picker, required before creating tables, scripts or modules.
  • Global behavior: Global is selectable and sets scope to Global, it is not hidden and it never maps to Incident when chosen.

Why C is correct

ServiceNow documentation states that application developers must select an application as their current scope context, and the picker task page shows selection as the mechanism. Choosing an app therefore both displays it and sets scope, which is why the platform warns builders to check scope before editing. That behavior prevents cross-contamination where a scoped fix lands in Global or vice versa. Options claiming no scope change or a hidden Global contradict the documented select-to-set workflow.

Why the others are wrong

  • A. Global is a reserved scope but it does appear in the picker, so the hidden-application claim is false.
  • B. Selection does set scope, which is the entire purpose of the control, so the no-effect statement reverses the behavior.
  • D. Selecting Global sets scope to Global, not to Incident, and Incident is a table rather than a scope value.

CAD exam tip

Picker equals scope, if you pick it you are in it, and always glance at the header before creating any file.

6Which of the following is an available feature in Studio? (Choose two.)
  • Push to update set
  • Merge branches
  • Search code
  • Push to external source control
Answer: C, D

The short version

CD — Search code and Push to external source control are the Studio features. Merge branches and Push to update set belong to other workflows, so only C and D combine into the settled pair.

Key concepts in this question

  • Studio IDE: The scoped-app workspace consolidating files, tables, logic, and source control.
  • Search code: A Studio search across Script Includes, Client Scripts, and Business Rules for impact analysis.
  • External source control: Studio linkage pushing files to Git via URL plus credentials for collaboration.
  • Update sets versus git: Update sets move customization between instances, while source control versions externally; Studio favors the latter.

Why CD is correct

CD pairs Search code with Push to source control, both exposed in Studio. Search locates functions and strings. Push versions files in Git. Merge and update-set push live elsewhere, leaving C plus D.

Why the others are wrong

  • A. Push to update set sounds plausible but is not a Studio action, since update-set capture and promotion run through system update-set tables and instance migration.
  • B. Merge branches is a Git provider operation rather than a Studio button, so including it overstates what the embedded IDE performs itself.
  • C. Alone is incomplete because it omits source-control push, which is equally part of the Studio feature set alongside code search.
  • D. Alone is incomplete because it omits code search, which pairs with source control as the two testable Studio capabilities here.

CAD exam tip

Studio equals code plus git: remember Search code and Push to source control, never merge or update-set push.

7The Task table is an example of which of the following? (Choose two.)
  • Parent class
  • Legacy class
  • Child class
  • Base class
Answer: A, D

The short version

AD — Task is both a parent class and a base class. It sits above Incident, Problem and Change, extends no higher table, and passes fields and logic downward through table extension.

Key concepts in this question

  • Table extension: hierarchy where a child table extends a parent and inherits columns, business logic and access evaluation.
  • Parent class: a table that is extended by other tables, supplying shared fields such as number, state and assignment.
  • Base class: the top of an extension hierarchy that itself extends nothing, often used interchangeably with root parent in exam wording.
  • Child versus legacy: child means it extends another table, while legacy class is not a ServiceNow table-class term, making both wrong for Task.

Why AD is correct

Task is the classic ServiceNow example of a table that other task-derived tables extend, which makes it a parent class by the definition quoted in vendor prose. Because Task itself extends no higher table, it is also the base or root of that hierarchy, so base class applies as well. Docs define the extended table as the parent, and Task plays exactly that role for Incident, Problem, Change and other children. That dual position explains why the settled key needs two letters rather than one.

Why the others are wrong

  • B. Legacy class is not a documented table-extension category, so it is a nonsense distractor with no search support.
  • C. Child class requires extending another table, yet Task extends nothing and instead is extended by others.

CAD exam tip

Think Task at the top, children below, parent equals base here, and legacy is always the throwaway option.

8Which of the following is true about deleting fields from a table?
  • Table records are deleted when a field is deleted
  • User-defined non-inherited fields can be deleted
  • Any field on a table can be deleted
  • Inherited fields can be deleted
Answer: B

The short version

B — only user-defined non-inherited fields can be deleted. Deleting a field removes its column and stored values but leaves table rows intact, while inherited and system fields remain protected from removal.

Key concepts in this question

  • Dictionary field: A column definition storing type, label, and attributes, distinct from row data.
  • User-defined field: A custom column added to a specific table and owned by that table.
  • Inherited field: A column defined on a parent table and visible on extended child tables through table extension, where the definition lives with the parent.
  • Field deletion impact: Removing a column drops its values but keeps rows, unlike record deletion.

Why B is correct

B holds because only owned custom non-inherited fields carry a deletable dictionary entry. Cleanup removes obsolete columns without harming parents. Inherited definitions stay locked, and rows persist with remaining columns.

Why the others are wrong

  • A. Table records are not deleted when a field is deleted, since only values in that column are dropped while the rows and other columns remain queryable.
  • C. Not every field can be deleted because system, inherited, and protected platform columns are blocked to preserve upgrade integrity and shared behavior.
  • D. Inherited fields cannot be deleted from the child table because ownership sits with the parent, so removal must occur at the source or not at all.

CAD exam tip

Own it to remove it: deletable means custom plus non-inherited on that exact table.

9Why would you build a custom app? (Choose two.)
  • To avoid using a code repository like GitHub or GitLab
  • To replace ServiceNow base tables
  • To fulfill a specific use case on internal processes
  • To create a custom integration for a 3rd party system
Answer: C, D

The short version

CD — custom apps fulfill specific internal use cases and third-party integrations. They extend the platform to unmet process needs rather than evading repositories or replacing core tables.

Key concepts in this question

  • Custom scoped application: A purpose-built set of tables, logic, and permissions solving a departmental workflow.
  • Internal process fit: Approvals, intake, and tracking gaps that stock modules miss suit custom builds.
  • Third-party integration: Connecting records to vendor systems via REST, SOAP, or IntegrationHub needs helper tables in a custom app.
  • Platform citizenship: Good apps reuse base tables via extension and honor scoping plus source control.

Why CD is correct

CD combines internal use cases with custom integrations as additive value. Processes gain tailored tables and automation. Integrations gain homes for endpoints and credentials. Both preserve upgrades, so C plus D holds.

Why the others are wrong

  • A. Avoiding a code repository is never a legitimate motive, since professional apps should embrace Git or update sets for versioning and team review.
  • B. Replacing ServiceNow base tables breaks upgradeability and data integrity, so extension rather than replacement is the prescribed pattern.
  • C. Alone is incomplete because integration construction is an equally valid and frequently tested driver for scoped development.
  • D. Alone is incomplete because bespoke internal workflow coverage is likewise a core justification alongside integration work.

CAD exam tip

Build to add, not to dodge: bespoke process plus bespoke integration equals custom app.

10What are three ServiceNow table creation methods? (Choose three.)
  • Using legacy Workflows
  • Upload and turn a spreadsheet into a custom table
  • Using Flow Designer
  • Use the Now Experience Table Creator
  • Extend a table
  • Create a custom table
Answer: B, E, F

The short version

BEF — Upload a spreadsheet, extend a table, or create a custom table. Those three are the documented creation paths, while workflows, flows and the invented Now Experience creator do not create tables.

Key concepts in this question

  • Custom table creation: building a new dictionary-defined table from scratch when no spreadsheet or parent table fits.
  • Spreadsheet import: turning an uploaded sheet into a custom table with fields inferred from columns, ideal for migration starts.
  • Table extension: creating a child of an existing table to inherit columns and business logic, such as extending Task.
  • Non-methods: Flow Designer automates logic and legacy workflows route work, but neither defines schema, and Now Experience Table Creator has no doc existence.

Why BEF is correct

App Engine Studio and Guided Application Creator docs list the same three table origins, quoted in vendor prose as create-and-customize, create-from-scratch and extend paths. Upload covers data-led builds, extend covers hierarchy reuse, and custom covers greenfield design, together spanning every legitimate start. The exam deliberately contrasts those schema operations with automation tools that run after tables exist. That three-way coverage is why B, E and F form the settled triple.

Why the others are wrong

  • A. Legacy workflows execute approvals and tasks but do not define tables or fields.
  • C. Flow Designer builds flows and subflows against existing tables rather than creating table schema.
  • D. Now Experience Table Creator returns no documentation hits and is an invented name for this question.

CAD exam tip

Tables come from sheet, scratch or parent, flows and workflows never create schema, and unknown creator names are wrong.

Want the full bank of 234 questions for ServiceNow Certified Application Developer (CAD)? See all practice exams.