Which statement best describes reference fields in ServiceNow?

Which statement best describes reference fields in ServiceNow?

• A. Reference fields require the use of reference tables
• B. Reference fields can store any type of data
• C. Reference fields are deprecated
• D. Reference fields are only for user records

Answer: (A)

Reference fields in ServiceNow create a link to a record in another table. They aren’t generic data holders; they specifically point to a record in a defined reference table, and what’s stored behind the scenes is the sys_id of that referenced record while the UI shows its display value. This is why the statement that they require the use of a reference table is correct—the field must know which table it’s linking to so it can look up and display the related record. Understanding this helps: you can reference any table’s records (not just user records), and you typically see a lookup picker or autocomplete to choose the linked record. The other options are inaccurate because reference fields don’t store arbitrary data, aren’t deprecated, and aren’t limited to user records.

Reference fields in ServiceNow create a link to a record in another table. They aren’t generic data holders; they specifically point to a record in a defined reference table, and what’s stored behind the scenes is the sys_id of that referenced record while the UI shows its display value. This is why the statement that they require the use of a reference table is correct—the field must know which table it’s linking to so it can look up and display the related record.

Understanding this helps: you can reference any table’s records (not just user records), and you typically see a lookup picker or autocomplete to choose the linked record. The other options are inaccurate because reference fields don’t store arbitrary data, aren’t deprecated, and aren’t limited to user records.