Explanation:

Box 1: Yes
Change it to Direct User/Basic access level and Team privileges. This creates a security role with team member's privilege inheritance.
Note: For roles assigned to teams with Basic-level access user privilege, the role's inheritance configuration also comes into play. If the team has the Member's privilege inheritance set to Team privileges only, then the user will only be able make use of that privilege for records owned by the team.

Box 2: No
The manager of the Property Management business unit is already a member of a Fabrikam business unit, which has the root security role Box 3: Yes Reference:
https://docs.microsoft.com/en-us/power-platform/admin/security-roles-privileges

B: The Export Profile is the core concept of the Data Export Service. The Export Profile gathers set up and configuration information to synchronize data with the destination database. As part of the Export Profile, the administrator provides a list of entities to be exported to the destination database.
D: Only entities that have change tracking enabled can be added to the Export Profile.
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/replicate-data-microsoft-azure-sql-database

Instead use access team templates and give access to members in the two departments.
Reference:
https://community.dynamics.com/crm/b/crmdevmigrationconfigandcustomization/posts/access-teams-and-access-team-templates

You will find options related to the isolation mode and location for the assembly. These refer to options that apply to on-premise deployments. Dataverse is not available for on-premises deployments, so you will always accept the default options of SandBox and Database for these options.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/register-plug-in