Explanation:

In Azure DevOps workspace (project) security settings, role assignments determine access levels for groups:
Viewer (equivalent to the Readers security group): Grants read-only access to work items, code, pipelines, and other artifacts. Ideal for review-only scenarios where users need to view but not edit content.
Contributor (equivalent to the Contributors security group): Allows full edit and contribute privileges, such as updating work items, code reviews, and pipeline runs. Suitable for active participation in reviews that may involve feedback or changes.
Based on the group names implying review-focused access, Viewer fits Group1 for passive observation, while Contributor fits Group2 for interactive review tasks. These align with default Azure DevOps permissions for secure, least-privilege access.

For a Type 2 slowly changing dimension (SCD), you typically need to add the following types of columns that do not exist in the source system:
An effective start date and time (E): This column records the date and time from which the data in the row is effective.
An effective end date and time (A): This column indicates until when the data in the row was effective. It allows you to keep historical records for changes over time.
A surrogate key (C): A surrogate key is a unique identifier for each row in a table, which is necessary for Type 2 SCDs to differentiate between historical and current records.
References: Best practices for designing slowly changing dimensions in data warehousing solutions, which include Type 2 SCDs, are commonly discussed in data warehousing and business intelligence literature and would be part of the modeling guidance in a Fabric tenant's documentation.

You need to recommend which type of Fabric capacity SKU meets the data analytics requirements for the Research division.
Requirement: "The Research division workspaces must use a dedicated, on-demand capacity that has per- minute billing." Fabric capacity SKUs:
F (Fabric) = dedicated Fabric capacity, available on pay-as-you-go with per-minute billing.
P (Premium) and EM are Power BI capacities (not Fabric-native).
A refers to Azure Analysis Services capacity.
The only correct option is F SKU.

In Microsoft Fabric, semantic models (formerly datasets) can be managed using external tools like Tabular Editor. To push or publish changes directly to a Fabric workspace from Tabular Editor, the workspace must support XMLA endpoint connectivity with read-write access.
Explanation of Each Option
A). For Workspace1, enable Git integration.
Git integration allows source control and versioning of items in a Fabric workspace. It is intended for lifecycle management of artifacts and does not provide the connectivity required for Tabular Editor to publish semantic model changes.
B). For Workspace1, create a managed private endpoint.
A managed private endpoint provides secure connectivity between Fabric and external data sources. It is not related to the ability to publish semantic models through XMLA.
C). For Model1, enable external sharing.
External sharing governs who can access the model outside the organization. This does not affect publishing workflows from developer tools.
D). For Capacity1, set XMLA Endpoint to Read Write.
This is the correct choice. The XMLA endpoint provides a programmatic connection point for external tools like Tabular Editor. By default, the XMLA endpoint is enabled only in read-only mode. Changing the setting to Read Write allows developers to push changes, update metadata, and deploy semantic models directly from Tabular Editor into the Fabric workspace.
Summary
To publish changes to a Fabric semantic model using Tabular Editor, the XMLA endpoint of the assigned capacity must be set to Read Write. Without this configuration, Tabular Editor can only connect in read-only mode and cannot deploy updates.
References
Use the XMLA endpoint in Microsoft Fabric
Manage capacities in Microsoft Fabric
Tabular Editor and XMLA endpoint

Explanation: