Creating and customizing tables and data →mediumMultiple ChoiceObjective-mapped

SNOW-CAD Creating and customizing tables and data Practice Question

A custom table 'u_incident' has a 'priority' field that should be set to 1 when the 'category' is 'Critical', otherwise 3. Which is the most efficient way to implement this default?

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

✓

Define a default value script in the dictionary for the priority field

The most efficient way is to define a default value script in the dictionary for the 'priority' field. This script runs server-side during record insertion and sets the priority based on the category without additional database operations. Option A (Business Rule) works but adds overhead compared to a dictionary default. Option B (Client Script) is client-side and can be bypassed or not execute. Option C (UI Policy) only affects client-side behavior and does not set field values on the server.

Answer analysis

Option-by-option breakdown

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

✗
Create a Business Rule on 'Before Insert' that sets the priority
Why it's wrong here
Works but less efficient than dictionary default script; adds separate rule.
✗
Create a Client Script that runs onLoad and sets priority
Why it's wrong here
Client-side only, can be bypassed, and does not guarantee server-side default.
✗
Use a UI Policy to set priority based on category
Why it's wrong here
UI Policies do not set field values; they only show/hide fields.
✓
Define a default value script in the dictionary for the priority field
Why this is correct
Executes at database level with no extra rule overhead.

Go deeper

SNOW-CAD Creating and customizing tables and data Practice Question

Why each option matters

Option-by-option breakdown

Related to this question