Which two capabilities are considerations when marking a field as required in Object Manager? Choose 2 answers

Question

Options

• AThe field is not required to save records via the API on that object.
• BThe field is universally required to save a record on that object.
• CThe field is added to every page layout on that object.
• DThe field is optional when saving records via web-to-lead and web-to-case

• A
  2% (1)
• B
  95% (42)
• D
  2% (1)

Explanation

When a field is marked as required at the field definition level in Object Manager (as opposed to only on a page layout), two important behaviors apply. B: The field becomes universally required across all interfaces - including the UI, API, and any integration - because the requirement is enforced at the database/object level, not just the layout level. C: Salesforce automatically adds that required field to every page layout on that object to ensure users always have access to fill it in; otherwise a layout without the field would make it impossible to save a record. A is false: unlike page-layout-only required fields (which API calls can bypass), fields required in Object Manager ARE enforced via the API. D is false: fields required in Object Manager are also required in Web-to-Lead and Web-to-Case submissions.

No community discussion yet for this question.