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 on every Invoice record…

Question

Options

• AMake the field universally required.
• BCreate a Process Builder to set the field.
• CDefine an approval process for the child.
• DRequire the field on the record type.

• A
  3% (1)
• B
  9% (3)
• C
  72% (23)
• D
  16% (5)

Explanation

Note: The listed answer is C, but the correct answer is A. Making the field universally required (A) enforces that the Billing System field must be populated before any Invoice record can be saved, regardless of whether the record is created via the UI, API, or automation. This is the most reliable platform-level enforcement. Process Builder (B) could auto-populate a default value but would not prevent saving with a blank field. An Approval Process (C) routes records for human review and has no mechanism to require a field value - this answer is incorrect for this use case. Requiring the field on a record type (D) only enforces it through specific page layouts, not universally across all access methods including API.

No community discussion yet for this question.