Question 245 of 500

Quick Answer

The answer is that the Business Rule runs after the database operation, which is why setAbortAction(true) fails to prevent the record save. This method works by setting an abort flag that cancels the pending database write, but it must execute before the database commit occurs. When a Business Rule runs in the 'after' order, the record has already been written to the database, so the abort flag is ignored and the save persists. On the ServiceNow Certified Application Developer CAD exam, this question tests your understanding of Business Rule execution order and the lifecycle of a database transaction. A common trap is assuming setAbortAction works in any phase, but it only functions in 'before' or 'before query' Business Rules. Remember the mnemonic: "Abort before the port" — the abort flag only stops the ship from leaving the dock, not after it has already sailed.

SNOW-CAD Practice Question: Automating application logic with business rules and scripts

This SNOW-CAD practice question tests your understanding of automating application logic with business rules and scripts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A Business Rule uses 'current.setAbortAction(true)' to stop a record from being saved. However, the record is still saved under certain conditions. Which scenario could cause this?

Question 1hardmultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

The Business Rule runs after the database operation.

Option A is correct because `current.setAbortAction(true)` must be called in a Business Rule that runs before the database operation (e.g., 'before' or 'before query' order). If the Business Rule runs 'after' the database operation, the record has already been committed to the database, so aborting the action has no effect on the save. The abort flag only prevents the pending database write; once the write is complete, the flag is irrelevant.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The Business Rule runs after the database operation.

    Why this is correct

    After rules cannot abort the operation.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The Business Rule is on a table that is extended from a table with a higher order Business Rule.

    Why it's wrong here

    Order does not affect abort ability.

  • Another Business Rule runs in the same order but sets abort to false.

    Why it's wrong here

    Once abort is set, it cannot be undone by another rule.

  • The Business Rule has a condition that is not met.

    Why it's wrong here

    If condition not met, abort not triggered, but this is expected behavior.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume `setAbortAction(true)` works regardless of when the Business Rule runs, but the platform only honors the abort flag in 'before' or 'before query' scripts, not in 'after' scripts.

Detailed technical explanation

How to think about this question

Under the hood, ServiceNow uses a GlideRecord transaction lifecycle: before-query, before, after, and async. `setAbortAction(true)` sets a flag on the GlideRecord object that is checked by the platform just before the database INSERT or UPDATE is issued. If the rule runs after the database operation (e.g., 'after' order), the database write has already occurred, and the abort flag is never evaluated. A real-world scenario is a Business Rule that validates a field and aborts if invalid—if mistakenly set to 'after', invalid records will be saved, causing data integrity issues.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the SNOW-CAD exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SNOW-CAD practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SNOW-CAD practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SNOW-CAD question test?

Automating application logic with business rules and scripts — This question tests Automating application logic with business rules and scripts — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The Business Rule runs after the database operation. — Option A is correct because `current.setAbortAction(true)` must be called in a Business Rule that runs before the database operation (e.g., 'before' or 'before query' order). If the Business Rule runs 'after' the database operation, the record has already been committed to the database, so aborting the action has no effect on the save. The abort flag only prevents the pending database write; once the write is complete, the flag is irrelevant.

What should I do if I get this SNOW-CAD question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 25, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This SNOW-CAD practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CAD exam.