PLAT-ADMN-201 · Question #27
PLAT-ADMN-201 Question #27: Real Exam Question with Answer & Explanation
The correct answer is D: Make the field universally required.. To ensure that a field is populated on every single record, regardless of how it is created (manually, via API, or through an integration), the best method is to make the field universally required at the field definition level. When a field is marked as "Required" in the Object
Question
Northern Trail Outfitters uses a custom Invoice object 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 a Platform Administrator ensure this requirement?
Options
- ACreate a flow to update the field.
- BRequire the field on the record type.
- CDefine an approval process for the field.
- DMake the field universally required.
Explanation
To ensure that a field is populated on every single record, regardless of how it is created (manually, via API, or through an integration), the best method is to make the field universally required at the field definition level. When a field is marked as "Required" in the Object Manager, the Salesforce database will reject any attempt to save a record if that field is empty. While requiring a field on a Page Layout or Record Type (Option B) provides a good user experience for manual entry, it does not prevent records from being created without that data via the API or background processes. Using a flow (Option A) to update the field is reactive rather than preventative. Universal requirement is the most robust way to maintain data integrity for critical fields like "Billing System" that are essential for reporting and external system alignment.
Topics
Community Discussion
No community discussion yet for this question.