ServiceNow, Databricks, Snowflake & K8s: practice drill
10 realistic exam questions, graded as you go, with the exact rule or statute citation for every answer. Start free, no sign-up.
Timed mock exam
10 questions in 12 minutes, drawn from every topic. No answers shown until the end, then a full score breakdown, your weakest topics and a review of what you missed.
Prices are in US dollars, plus tax where it applies. Stripe, our payment processor, calculates tax at checkout.
All sales are final. If something is really wrong, such as a duplicate charge or a purchase that does not unlock what you bought, write to support@careerexampro.com and we will put it right.
One-time payment. Nothing renews.
You have an exam ticket for this practice test. Start the timed mock exam to use it.
Exact question counts, passing scores, and allowed reference materials vary by testing window and state/agency. Always confirm current rules with the official testing provider.
Sample questions
In ServiceNow, incident, problem, and change_request all extend the base task table. An administrator needs the inherited short_description field to have a custom default value and read-only behavior strictly on incident records without affecting problem or change_request. What is the recommended approach?
Edit the short_description Dictionary Entry directly on task, because child tables automatically isolate dictionary edits from siblings.
Create a duplicate custom column named u_short_description on incident and deactivate the inherited task.short_description field.
Configure a Dictionary Override on task.short_description scoped specifically to the incident table.
Modify the task table's extends attribute so incident becomes a standalone base table with independent column definitions.
Show the answer
C. Configure a Dictionary Override on task.short_description scoped specifically to the incident table.
A Dictionary Override lets an administrator customize inherited field attributes (such as default value, mandatory, read-only, or reference qualifier) for a specific child table (incident) without altering the parent task table or sibling tables like problem and change_request.
A ServiceNow team requires resolution_notes to be mandatory whenever an Incident's state is set to Resolved—whether updated via the browser form, a List Edit, an Import Set, or the Table REST API. Which configuration enforces this across every channel?
A UI Policy with Run scripts enabled, because ServiceNow automatically executes form UI Policies inside the REST API layer.
An onChange Client Script calling g_form.setMandatory('resolution_notes', true), because Client Scripts block server-side API writes.
A display Business Rule checking current.state == 6, because display rules validate incoming Import Set payloads before insert.
A Data Policy with Use as UI Policy on client enabled, enforcing the rule server-side on API/imports and client-side on forms.
Show the answer
D. A Data Policy with Use as UI Policy on client enabled, enforcing the rule server-side on API/imports and client-side on forms.
UI Policies and Client Scripts run only in the user's browser form and are bypassed by REST API calls, Import Sets, and standard list edits. A Data Policy enforces mandatory and read-only rules on the server across all entry points and can optionally mirror as a UI Policy on forms.
Reference: ServiceNow UI Policy vs. Client Script vs. Data Policy
A developer writes a before Business Rule on the incident table to set an escalation flag on the record being saved:
Why does ServiceNow code review flag current.update() here as a severe defect?
A before Business Rule cannot modify fields on current at all; field updates on current are only permitted inside an async Business Rule.
before rules save changes to current automatically; calling current.update() causes redundant or recursive execution.
current.update() only commits changes in display Business Rules and silently discards field assignments during before execution.
Calling current.update() bypasses all table ACLs and automatically deletes the previous GlideRecord object from memory.
Show the answer
B. before rules save changes to current automatically; calling current.update() causes redundant or recursive execution.
In a before Business Rule, modifying current.<field> automatically persists as part of the pending database write. Calling current.update() triggers an extra database write and re-fires Business Rules, risking infinite loops and severe performance degradation (after is for related tables; async is for deferred background work).
Reference: ServiceNow Business Rules: before, after, async & display Best Practices
Taking this exam soon?
Tell us which exam domains or calculation drills you want more practice on.