Question 221 of 500

Quick Answer

The answer is to limit logs, use GlideAggregate, and leverage current/previous. These three factors directly address business rule performance best practices by reducing database I/O and script execution overhead. Excessive gs.log() statements in production degrade performance by writing to the system log, consuming I/O resources and filling the database, while GlideAggregate performs server-side aggregation without pulling unnecessary records, and using current/previous avoids costly database queries by working with the in-memory record. On the ServiceNow Certified Application Developer CAD exam, this question tests your understanding of efficient scripting in high-volume environments, often appearing as a select-three scenario where a common trap is choosing “use gs.log for debugging” instead of limiting it. A reliable memory tip is “Log less, aggregate on the server, and never query what you already hold.”

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.

Which THREE factors should be considered when designing a Business Rule for optimal performance? (Select THREE)

Question 1mediummulti select
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

Limit the use of gs.log() statements in production.

Option B is correct because excessive gs.log() statements in production can degrade performance by writing to the system log, which consumes I/O resources and can fill up the database. In ServiceNow, logging should be minimized or removed in production scripts to avoid unnecessary overhead, especially in high-volume Business Rules.

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.

  • Avoid using synchronous GlideAjax calls.

    Why it's wrong here

    GlideAjax is client-side, not in Business Rules.

  • Limit the use of gs.log() statements in production.

    Why this is correct

    Logging can impact performance.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use GlideAggregate instead of GlideRecord for calculations.

    Why this is correct

    More efficient for aggregate functions.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use 'current' and 'previous' instead of querying the database.

    Why this is correct

    Reduces database calls.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Set the Business Rule to run on 'before' if possible.

    Why it's wrong here

    Not a performance consideration.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may confuse client-side performance concerns (like synchronous GlideAjax) with server-side Business Rule optimization, or assume that running a rule 'before' always improves performance without considering the specific logic and context.

Detailed technical explanation

How to think about this question

Under the hood, gs.log() calls in ServiceNow write to the sys_log table, which can cause contention and slow down transaction processing, especially in high-throughput scenarios like update Business Rules on frequently modified tables. Using GlideAggregate instead of GlideRecord for calculations leverages database aggregation functions (e.g., SUM, COUNT) to process data server-side, reducing network and memory overhead. The 'current' and 'previous' objects are already loaded in memory during a Business Rule execution, so using them avoids additional GlideRecord queries that would hit the database again.

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: Limit the use of gs.log() statements in production. — Option B is correct because excessive gs.log() statements in production can degrade performance by writing to the system log, which consumes I/O resources and can fill up the database. In ServiceNow, logging should be minimized or removed in production scripts to avoid unnecessary overhead, especially in high-volume Business Rules.

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.