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

When a field is marked as 'required' in Object Manager (field settings), Salesforce automatically enforces its presence on all page layouts for that object to ensure users can always fulfill the requirement, preventing inconsistencies.

Making a field universally required at the object level via Object Manager means it must always have a value when a record of that object type is created or updated, applying universally across the UI, API, web-to-lead/case, and other data entry methods.

If a field is universally required in Object Manager, it is mandatory even for records created via web-to-lead and web-to-case, not optional.

Marking a field as universally required in Object Manager means it is also required when saving records via the API; API calls will fail if the required field is not populated.