Core Application Development →easyMultiple ChoiceObjective-mapped

SNOW-CAD Core Application Development Practice Question

Exhibit

Refer to the exhibit.

Data Policy configuration on Incident table:

Name: DP - Require short description on category change
Table: Incident
Conditions: short_description IS NOT EMPTY OR category IS NOT EMPTY
Script:
if (current.operation() == 'update' && current.category.changes()) {
    current.short_description.setMandatory(true);
}

The data policy is intended to require short description when category changes during an update. However, the short description is never made mandatory. Which issue exists?

⚠ Common exam trap

ServiceNow often tests the distinction between server-side and client-side APIs, and the trap here is that candidates assume `setMandatory()` works everywhere because it is commonly used in UI policies, but it is not available in data policies.

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 script uses setMandatory which is not available in Data Policies

`setMandatory()` is a client-side method used in client scripts or UI policies, not in data policies. Data policies run server-side and use `mandatory=true` on a dictionary element or `gs.addErrorMessage()` to enforce field requirements. Since the script attempts to call `setMandatory()` within a data policy, it will fail to make the short description mandatory, leaving the requirement unmet.

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 table is Incident but the policy uses current.operation() incorrectly
Why it's wrong here
Incorrect; operation() is valid.
✗
The condition should use AND instead of OR
Why it's wrong here
Incorrect; the condition logic is not the cause of mandatory not being set.
✓
The script uses setMandatory which is not available in Data Policies
Why this is correct
Correct; Data Policies cannot change field properties via script; they can only enforce validation or abort saves.
✗
The policy should be of type 'Constraint'
Why it's wrong here
Incorrect; Data Policies are already constraints.

Go deeper

SNOW-CAD Core Application Development Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question