Valid ADM-201 Dumps shared by EduDump.com for Helping Passing ADM-201 Exam! EduDump.com now offer the newest ADM-201 exam dumps, the EduDump.com ADM-201 exam questions have been updated and answers have been corrected get the newest EduDump.com ADM-201 dumps with Test Engine here:
Which two capabilities are considerations when marking a field as required in Object Manager? Choose 2 answers
Correct Answer: A,B
When you mark a field as required in Object Manager, the field is universally required to save a record on that object in the user interface. However, the field is not required to save records via the API on that object, unless you also mark it as required on the page layout. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_required_fields.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_profile_picklists.htm&type=5
Recent Comments (The most recent comments are at the top.)
Sr - Jan 23, 2026
B & C
"A universally required field is a custom field. It must have a value whenever a record is saved within Salesforce, the Lightning Platform API, Connect Offline, Salesforce for Outlook, the Self-Service portal, or automated processes, such as Web-to-Lead and Web-to-Case. Making a field required on a page layout or through field-level security ensures that users must enter a value. Making a field required universally gives you a higher level of data quality beyond the presentation level of page layouts."
answers are B,C A. The field is not required to save records via the API on that object. ❌ → ❌ Incorrect — if a field is marked “Required” at the field-level (Object Manager), it is required everywhere, including the API, import wizard, Data Loader, Flows, and Apex.
Recent Comments (The most recent comments are at the top.)
B & C
"A universally required field is a custom field. It must have a value whenever a record is saved within
Salesforce, the Lightning Platform API, Connect Offline, Salesforce for Outlook, the Self-Service
portal, or automated processes, such as Web-to-Lead and Web-to-Case. Making a field required on
a page layout or through field-level security ensures that users must enter a value. Making a field
required universally gives you a higher level of data quality beyond the presentation level of page
layouts."
Source (page 24): https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/smb_sales_impl_guide_2.pdf
B & C are correct answers.
answers are B,D
Link: https://help.salesforce.com/s/articleView?id=platform.fields_universally_required_field_considerations.htm&type=5
answers are B,C
A. The field is not required to save records via the API on that object. ❌
→ ❌ Incorrect — if a field is marked “Required” at the field-level (Object Manager), it is required everywhere, including the API, import wizard, Data Loader, Flows, and Apex.