Question 52 of 500
Application development using ServiceNow StudiohardMultiple ChoiceObjective-mapped

Quick Answer

The correct choice is to replace gs.yearsAgoStart(5) with gs.yearsAgo(5) because gs.yearsAgoStart() returns midnight on January 1st of the year five years ago, not the exact date five years ago from today. This means a purchase_date that is, for example, 5 years and 1 month old could still be greater than that January 1st date, causing the condition to fail. The gs.yearsAgo() method, by contrast, returns the precise date and time five years prior, ensuring any record with a purchase_date older than exactly five years triggers the status update. On the ServiceNow Certified Application Developer CAD exam, this distinction tests your understanding of GlideSystem date methods and their real-world impact on business rule conditions—a common trap is assuming both methods are interchangeable. Remember the memory tip: “Start” gives you the start of the year, while “Ago” gives you the exact ago.

SNOW-CAD Practice Question: Application development using ServiceNow Studio

This SNOW-CAD practice question tests your understanding of application development using servicenow studio. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 developer is building a custom application in ServiceNow Studio for IT asset management. The application includes a table 'Asset' with fields: asset_tag (string), serial_number (string), purchase_date (date), cost (currency), and status (choice: In Use, In Stock, Retired). The developer needs to create a business rule that automatically sets the status to 'Retired' when the cost is zero and the purchase_date is older than 5 years. The business rule should run before the record is saved to the database and should not prevent the save if conditions are not met. The developer writes the following business rule in Studio: Table: Asset, When: Before, Order: 100, Condition: current.cost == 0 && current.purchase_date < gs.yearsAgoStart(5). The script is: current.status = 'Retired'; However, the status is not being updated as expected. What is the most likely issue?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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

Replace gs.yearsAgoStart(5) with gs.yearsAgo(5) to get the exact date 5 years ago.

The issue is that `gs.yearsAgoStart(5)` returns the start of the year (January 1st) five years ago, not the exact date five years ago. This means a record with a purchase_date that is, for example, 5 years and 1 month old might still be after that start-of-year date and thus not match the condition. The correct method is `gs.yearsAgo(5)`, which returns the exact date and time five years ago, ensuring the comparison works as intended for any purchase_date older than 5 years.

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.

  • Replace gs.yearsAgoStart(5) with gs.yearsAgoEnd(5) to get the end of the year 5 years ago.

    Why it's wrong here

    gs.yearsAgoEnd(5) returns the last day of the year 5 years ago, which is not what is needed.

  • Change the table from 'Asset' to 'Asset [new]' as the business rule may be on the wrong table.

    Why it's wrong here

    The table name 'Asset' is correct; changing it would break the rule.

  • Increase the order of the business rule to 200 to ensure it runs after other rules.

    Why it's wrong here

    The order does not affect the logic; the condition is the issue.

  • Replace gs.yearsAgoStart(5) with gs.yearsAgo(5) to get the exact date 5 years ago.

    Why this is correct

    gs.yearsAgo(5) returns the date exactly 5 years before the current date, which correctly implements 'older than 5 years'.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse `gs.yearsAgoStart()` and `gs.yearsAgoEnd()` with `gs.yearsAgo()`, not realizing that the 'Start' and 'End' variants are for fiscal or calendar year boundaries, not for exact date arithmetic.

Detailed technical explanation

How to think about this question

Under the hood, `gs.yearsAgoStart(5)` uses GlideDateTime's `getYearStart()` method, which sets the time to 00:00:00 on January 1st of the specified year, while `gs.yearsAgo(5)` uses `addYears(-5)` to subtract exactly 5 years from the current date and time. In a real-world scenario, if today is 2025-06-15, `gs.yearsAgoStart(5)` returns 2020-01-01, so a purchase_date of 2020-06-14 would not be caught (it is after 2020-01-01), but it is actually older than 5 years. Only `gs.yearsAgo(5)` returns 2020-06-15, correctly matching any date before that.

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?

Application development using ServiceNow Studio — This question tests Application development using ServiceNow Studio — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Replace gs.yearsAgoStart(5) with gs.yearsAgo(5) to get the exact date 5 years ago. — The issue is that `gs.yearsAgoStart(5)` returns the start of the year (January 1st) five years ago, not the exact date five years ago. This means a record with a purchase_date that is, for example, 5 years and 1 month old might still be after that start-of-year date and thus not match the condition. The correct method is `gs.yearsAgo(5)`, which returns the exact date and time five years ago, ensuring the comparison works as intended for any purchase_date older than 5 years.

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.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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 11, 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.