nerdexam
Salesforce

ADM-201 · Question #313

Northern Trail Outfitters uses a custom object Invoice to collect customer payment information from an external billing system. The Billing System field needs to be filled in on every Invoice…

The correct answer is A. Make the field universally required. To ensure the 'Billing System' field is always populated on every Invoice record, an administrator should make the field universally required.

Submitted by jaden.t· Apr 18, 2026Object Manager and Lightning App Builder

Question

Northern Trail Outfitters uses a custom object Invoice to collect customer payment information from an external billing system. The Billing System field needs to be filled in on every Invoice record. How should an administrator ensure this requirement?

Options

  • AMake the field universally required.
  • BDefine an approval process for the field.
  • CRequire the field on the record type.
  • DCreate a Process Builder to set the field.

How the community answered

(22 responses)
  • A
    86% (19)
  • C
    5% (1)
  • D
    9% (2)

Why each option

To ensure the 'Billing System' field is always populated on every Invoice record, an administrator should make the field universally required.

AMake the field universally required.Correct

Making a field universally required ensures that users must enter a value into that field whenever they create or edit a record, preventing records from being saved without the necessary information. This enforces data entry at the database level across all record types and page layouts.

BDefine an approval process for the field.

An approval process is used to manage how records are approved in Salesforce, not to enforce data entry for a specific field.

CRequire the field on the record type.

Requiring a field on a record type only makes it required on page layouts associated with that record type, and it can be bypassed if the field is not on the layout or if a record type is not used.

DCreate a Process Builder to set the field.

Process Builder can automate actions, but it's used to *set* field values or perform other actions, not to *enforce* user input as a requirement for saving the record.

Concept tested: Field Validation and Data Integrity

Source: https://help.salesforce.com/s/articleView?id=sf.fields_defining_required.htm&type=5

Topics

#Custom Fields#Required Fields#Data Integrity#Object Configuration

Community Discussion

No community discussion yet for this question.

Full ADM-201 Practice