A custom field is made Read only from the Field level security and Required from Page layout. I can see the Field as Read Only for the User. Why it is happening? Is it because the Field level security override the Required option in Page layout?
Is there any real scenario that will come under this circumstance?
I know you said no validation rules in your question, but based on your comments it seems like it's more of the aesthetics that's keeping you away from them. From personal experience, as long as you have a good error explanation that doesn't leave users confused, they have no problem with validation rules. In case you decide to go this route, here's a rule that may work for you.
AND($Profile.Name = 'Read-Only Profile', ISCHANGED(Lead_Status))
Error Message: Lead Status is a read-only field for users with the profile 'Read-Only Profile'
Hope this helps if you decide to use this.
You can set the field as Read Only on page layout.
Best Answer
Hey @Robert thomas i understand the scenario it will consider the profile level First.I will briefly explain you with a scenario which will be asking recently in a mock test.
Universal Container wants to ensure that users complete the standard industry field when creating a new account record. To address the concern the administrator set the Industry field as required. However, some users are still able to create a new account record without completing the Industry Field.
For the above scenario answer will be like
Verify the field –level security for the Industry field is not set to “Read Only” on the user profiles.
(OR)
Verify that industry field is set as required on all page layout's assigned to the users
Hope this resolves your issue.