Custom Field Accessibility in Salesforce | Field Level Security and Page Layout

A.

If a custom field is made Read Only from the Field level security and Required from Page layout, the field will be Required for the user.

Here's why:

• Field level security controls the visibility and editability of fields based on profiles and permission sets. When a field is set to Read Only in the field level security, the user will not be able to edit the field.
• Page layout controls the layout and organization of fields on a record detail page. When a field is set to Required in the page layout, the user will have to fill out the field in order to save the record.
• In this case, the field is set to Read Only from the field level security, so the user will not be able to edit it. However, it is also set to Required from the page layout, which means that the user must fill it out in order to save the record. Since the user cannot edit the field, the only option is to fill it out with a value. Therefore, the field will be Required for the user.

Option A (Read Only for the user) is not correct because the field is set to Required in the page layout, which means the user must fill it out. Option C (Throws an error and doesn't allow making a Read only field Mandatory from page layout) is also not correct because there is no conflict between making a field Read Only from field level security and Required from page layout. Option D (User is given a choice in a pop-up window) is not correct because there is no option for the user to choose. The field is Read Only, and the user must fill it out in order to save the record, as it is Required in the page layout.