Question 1 of 30
In a Dynamics 365 environment, a company wants to implement field-level security to protect sensitive customer information. They have a custom entity called \"Customer Feedback\" with fields such as \"Feedback Comments,\" \"Customer Rating,\" and \"Follow-Up Date.\" The company has two roles: \"Customer Service Agent\" and \"Manager.\" The Customer Service Agent should only have read access to the \"Feedback Comments\" and \"Customer Rating\" fields, while the Manager should have full access to all fields. If the Customer Service Agent attempts to edit the \"Follow-Up Date\" field, which is set to have no access for this role, what will be the outcome when they try to save the record after making changes to this field?
The record will not save, and an error message will indicate insufficient permissions for the "Follow-Up Date" field.
The record will save, but the changes to the "Follow-Up Date" field will not be applied.
The record will save successfully, and the changes to the "Follow-Up Date" field will be applied.
The system will automatically revert the changes made to the "Follow-Up Date" field without any notification.

Preparing for Microsoft MB-910 Microsoft Dynamics 365 Fundamentals Customer Engagement Apps (CRM)? Now land the interview.

73% of qualified candidates get rejected because of weak resumes. Build an ATS-optimized, recruiter-ready resume in under 5 minutes - free to start.

Build My Resume Free