Skip to content
Tutorials Center
My learning

Topics

Lesson 39 of 39 ยท Projects and Practice

Practice Exercises and Certification Preparation for ServiceNow

Practice ServiceNow skills with scripting and flow exercises, a study plan for the Certified System Administrator exam, and a checklist of topics to know.

Reading about a platform is not the same as using it. This final lesson gives you exercises that you can solve in a free developer instance, a way to check your reasoning with small JavaScript stand-ins, and a plan for preparing for the Certified System Administrator (CSA) exam, the most common first ServiceNow certification.

Exam outlines change between releases, and this lesson does not reproduce exam questions. Use the official exam blueprint on the ServiceNow training site as the authority, and use the Personal Developer Instance (PDI) from the developer site for real practice. A PDI may be reclaimed after inactivity, so keep your work exportable in update sets.

How to practice

  1. Request a PDI and keep it updated to a recent release.
  2. Learn on demo data: the PDI comes with users such as Abel Tuter and Beth Anglin and sample incidents.
  3. Do every exercise twice: first the click path, then in your own words why each step is needed.
  4. Keep a notebook of errors you caused and how you found them. Debugging is the real skill.

Exercises: configuration

  1. Add a choice Awaiting vendor to the incident On Hold reason. Where does the change live, and how do you move it to another instance?
  2. Create a UI policy that makes Close notes mandatory when State is Resolved, and hides Problem for callers without the itil role. Check it as another user.
  3. Build a list filter of "my open incidents, priority 1 or 2, older than a day", save it as a list view, and share it with a group.
  4. Create a notification that emails the caller when an incident is resolved, then use Email Logs to see the result.
  5. Make a catalog item with one reference variable filtered by a reference qualifier.

Exercises: flows and automation

  1. Write a flow that creates an incident task for each user in a group when a major incident is opened (use Look Up Records and For Each).
  2. Add an error handler that records the failure on the incident.
  3. Build a subflow Notify team with two inputs and call it from two flows.
  4. Add an SLA with a pause condition and test the Paused and Achieved stages.

Exercises: scripting

  1. In Scripts - Background, count active incidents per priority with GlideAggregate.
  2. Write a before business rule that blocks resolving an incident without close notes, and a client script that does the same on submit. Which one is the real guard?
  3. Write a Script Include with a method returning the number of open incidents for a group, call it from a rule, and test with a group that does not exist.
  4. Call the Table API for incident #1 from a REST client, then explain what a 403 means here.

Try the reasoning questions below in code. The first stand-in checks your understanding of how conditions combine in a filter; the second checks how change detection should behave.

JS Exercise helper: encoded query evaluator

Press Run (or Ctrl + Enter) to see the console output here.

No output.

JS Exercise helper: which rules fire on this save?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

CSA study plan (about six weeks)

Week Focus Practice in the PDI
1 Navigation, lists, forms, filters, favorites, platform basics Build and share list views; tour the Application Navigator
2 Tables, fields, dictionary, relationships, references, import sets Create a custom table, add fields, import a CSV with coalesce
3 Users, groups, roles, ACLs, impersonation Test with several users; read an ACL; debug security rules
4 Forms and UI: UI policies, client scripts, data policies, form layout, related lists Make a form dynamic without code
5 Process: incident, problem, change, catalog, SLA, notifications, knowledge Run an incident to Closed; order and fulfill a catalog item
6 Administration: update sets, reports, dashboards, instance health, upgrades, then mixed review Move a change between instances if you have two PDIs

Concentrate on the why: when to choose a UI policy over a client script, data policy over business rule, flow over business rule, ACL over hiding a button.

Checklist: can you explain these?

  • Tables, extension (Task and its children), dictionary entries and reference fields.
  • Roles, groups, containment and ACL evaluation.
  • UI policy vs data policy vs client script vs business rule.
  • Update set preview, collisions, and what is not captured.
  • Import set stages, coalesce and transform maps.
  • Notifications, events and email logs.
  • SLA conditions (start, pause, stop, reset) and schedules.
  • Catalog hierarchy (REQ, RITM, SCTASK), variables and record producers.
  • Flow Designer trigger, actions, data pills, subflows, error handling.
  • Reports, dashboards and Performance Analytics.
  • Instance clone, upgrade and sub-production testing.

After the CSA

Typical next steps: Certified Application Developer (CAD) for scripting and scoped applications, Certified Implementation Specialist tracks (ITSM, CSM, HRSD, Discovery and others) for processes, and ServiceNow Developer content for modern tooling such as App Engine Studio and UI Builder. Keep building small projects, read the release notes each cycle, and join community forums to learn from real cases.

Good habits that last

  1. Configure before you customize, and customize before you script.
  2. One change, one update set.
  3. Test as the user who will use it.
  4. Write it down: names, descriptions and short notes on every rule.
  5. Never assume the data is clean. Plan for empty fields and missing references.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the safest place to practice ServiceNow configuration?

    A PDI is free, isolated and made for learning, so mistakes harm nobody.
  2. 2. Which source defines what the CSA exam covers?

    The official blueprint is the authority and changes with releases.
  3. 3. A requirement says 'require close notes when resolving'. Which is the real enforcement?

    Server-side rules apply on every path, while client scripts only affect the browser form.
  4. 4. In the encoded query helper, what does ^OR do?

    ^OR joins a condition to the previous one as an alternative, while ^ alone means AND.

Summary

  • Practice in a PDI, do each exercise twice, and keep a log of mistakes.
  • The CSA study plan covers navigation, data, security, forms, processes and administration.
  • Know the reasons for choosing one tool over another, not only the steps.
  • Use the official blueprint, then continue with developer or implementation certifications.

Back to the ServiceNow track.