Explanation:

Explanation:

Box 1: Role-based security
Dataverse uses role-based security to group together a collection of privileges. These security roles can be associated directly to users, or they can be associated with Dataverse teams and business units.
Box 2: Field-level security
Sometimes record-level control of access is not adequate for some business scenarios. Dataverse has a field- level security feature to allow more granular control of security at the field level. Field-level security can be enabled on all custom fields and most system fields.
Box 3: Record-level security
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/wp-security-cds

Xrm.WebApi.online.executeMultiple executes a collection of action, function, or CRUD operations.
Xrm.WebApi.online.execute executes a single action, function, or CRUD operation.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-webapi
/online/executemultiple
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-webapi
/online/execute

Explanation:
1. Parental : Any action taken on a record of the parenttable is also taken on the related child table records.
2. Cascade user owned: Perform the action on all referencing entity records owned by the same user as the referenced entity.
3.Referential: Any related records can be navigated to, and actions taken on one will not affect the other.

By default, model-driven apps allows a specified set of query string parameters to be passed to a form. You use these parameters to set default values when you create a new record in the application. Each parameter must use a standard naming convention that includes a reference to the column logical name.
There are two ways to specify which query string parameters will be accepted by the form:
* Edit form properties
* Edit form XML
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/configure-form-accept-custom- querystring-parameters