Question 2

Explanation

D. Utilize role-based access control (RBAC) for project records. Explanation: Role-based access control (RBAC) is the most suitable feature to achieve the desired access control in this scenario. RBAC allows the consulting firm to assign specific roles to users and define the permissions associated with each role. By assigning the "project manager" role with edit permissions and other team members with view permissions, the firm can ensure that only project managers can edit project data while others can only view it. RBAC provides a granular level of control and is commonly used for access control in various systems, including Dataverse. A. Define data model for projects and roles: While defining a data model is important for organizing and structuring data, it does not directly address access control. It focuses on the structure and relationships of the data, rather than permissions and roles. B. Create business rules for data validation: Data validation rules ensure that data entered into the system meets certain criteria or conditions. While important for data integrity, data validation rules do not directly address access control. C. Configure table permissions for project management: Configuring table permissions can be a part of RBAC implementation, but it does not encompass the entire RBAC framework. RBAC involves assigning roles and permissions at a more granular level, allowing for more flexibility and control than simply configuring table permissions.