An organization uses Dynamics 365 Customer Engagement. The organization has accounting and customer service departments.

You must restrict users in customer service from being able to change the value of the balance field on the Contact records. The accounting team must be the only team able to edit this field.

You need to create the appropriate solution without any customizations.

What should you do?

A. Create an accounting form and role and make the balance field read-only.
B. Enable field security for the balance field and allow the customer service team to read and update it.
C. Create a customer service form and role and make the balance field read-only.

D. Enable field security for the balance field and allow the accounting team to read and update it.

Explanation:
Field-level security is available for the default fields on most out-of-box entities, custom fields, and custom fields on custom entities. Field-level security is managed by the security profiles. To implement field-level security, a system administrator performs the following tasks.
1. Enable field security on one or more fields for a given entity.
2. Associate one more existing security profiles, or create one or more new security profiles to grant the appropriate access to specific users or teams.

Note: Record-level permissions are granted at the entity level, but you may have certain fields associated with an entity that contain data that is more sensitive than the other fields. For these situations, you use field-level security to control access to specific fields.

Reference:
https://docs.microsoft.com/en-us/power-platform/admin/field-level-security