ServiceNow CAD study materials
ServiceNow CAD study resources

ServiceNow CAD study plan

ServiceNow CAD · Give each week a clear focus.

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.