Statement 1: No. When User1 creates Workspace3, User1 automatically becomes the Admin of that workspace. Access to a workspace (as Admin, Member, Contributor, or Viewer) must be granted explicitly at the workspace level. The prompt does not state that User1 ever added User3 or Group1 to Workspace3. Being a domain contributor (as explained in Statement 2) does not automatically grant access to the workspaces within that domain.

Statement 2: Yes. The prompt states that Group1 (which contains User1 and User3) is added to Domain1. In Microsoft Fabric, there are two primary domain-level roles: Domain admin and Domain contributor. Since User1 is already the Domain admin, the action of "adding Group1" is interpreted as assigning the Domain contributor role to all members of that group. Therefore, User3 gains Domain contributor access to Domain1.

Statement 3: No. User2 is the admin for Workspace2 and Domain2. User1 is the admin for Workspace3. There is no action described in the prompt that connects User2 to Workspace3 or Domain1. Therefore, User2 has no access to Workspace3.

Microsoft Fabric Documentation | Workspace roles: This document confirms that workspace roles (Admin, Member, Contributor, Viewer) are separate from domain roles and must be explicitly assigned within the workspace's "Access" pane. It also confirms that the creator of a workspace automatically becomes its Admin.

Source: https://learn.microsoft.com/en-us/fabric/governance/roles (See sections "Workspace roles" and "Create a workspace").

Microsoft Fabric Documentation | Domains: This document defines the "Domain admin" and "Domain contributor" roles. It clarifies that a Domain contributor can assign workspaces (in which they are an Admin or Member) to the domain. This role does not grant implicit access to view or contribute to other workspaces already in the domain.

Source: https://learn.microsoft.com/en-us/fabric/governance/domains (See section "Roles in domains").

Microsoft Fabric deployment pipelines are designed to move item metadata (definitions and structure), not the data itself.

1. Data: The data within semantic models is not copied to the target stage. The semantic model structure is deployed, but it must be refreshed in the target workspace (Workspace1_TEST) to be populated with data.
2. Dataflow Gen1: Dataflow Gen1 (the legacy Power BI dataflow) is not a supported item for deployment pipelines. Only Dataflow Gen2 is supported for deployment.
3. Refresh Policies: Specific item configurations, including scheduled refresh policies for semantic models, are not copied during deployment. These must be manually reconfigured in the target stage.

Microsoft Fabric Documentation: "Understand the deployment pipelines process"

Ref 1 (Data): Under the section "Items that aren't copied," the documentation lists: "Data (for semantic models, dataflows, and datamarts)."

Ref 2 (Dataflow Gen1): Under the section "Supported items" and its subsection on limitations, Dataflow Gen1 is listed as an unsupported item.

Ref 3 (Refresh Policies): Under the section "Item properties that aren't copied," the documentation explicitly lists: "Semantic model refresh schedule."

Source: https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process

BirthDate: The default() masking function is used to apply a predefined mask based on the column's data type. For date or datetime data types, the default() function masks the value to 1900-01-01, which precisely matches the requirement.

EmailAddress: The partial(prefix, padding, suffix) function is used to mask string data, exposing a specified number of characters at the beginning (prefix) and end (suffix), while replacing the middle section with a padding string.

• The requirement is to show the "first leading character," so prefix = 1.
• The requirement is to show the "last five characters," so suffix = 5.
• The option 'partial(1, "@", 5)' correctly implements this logic, using "@" as the padding string. The email() function is incorrect as it has a fixed format (first letter and .com suffix) that does not match the "last five characters" requirement. The random() function is incorrect as it is only used for numeric data types.

Microsoft Fabric Documentation (Dynamic Data Masking):

default() function: "For date/time data types (date, datetime2, datetime, datetimeoffset, smalldatetime, time), default() masks with 1900-01-01 00:00:00.0000000 (or corresponding value for date or time)."

Source: Microsoft Learn. (2024). Dynamic data masking in Microsoft Fabric data warehousing. Section: "Dynamic data masking built-in masking functions", Subsection: "default()".

partial(prefix, padding, suffix) function: "Masking method that exposes the first and last characters according to the specified prefix and suffix values and a custom padding string... prefix [is the] Number of characters at the beginning to expose. ... suffix [is the] Number of characters at the end to expose."

Source: Microsoft Learn. (2024). Dynamic data masking in Microsoft Fabric data warehousing. Section: "Dynamic data masking built-in masking functions", Subsection: "partial(prefix, padding, suffix)".

random(start, end) function (Incorrect Option): "Use the random function to mask any numeric data type with a random value within a specified range."

Source: Microsoft Learn. (2024). Dynamic data masking in Microsoft Fabric data warehousing. Section: "Dynamic data masking built-in masking functions", Subsection: "random(start, end)".

Here is a step-by-step evaluation of the query:

1. sort by Location desc, UnitsSold desc: The table is first sorted by Location in descending alphabetical order (Washington DC, Seattle, San Francisco, New York). Within each location, it's sorted by UnitsSold in descending numerical order.
2. extend Rank=row_rank_dense(UnitsSold, prev(Location) != Location): This adds a Rank column. The row_rank_dense(Term, Restart) function assigns a rank based on the Term (UnitsSold) and restarts the rank (sets it back to 1) whenever the Restart condition (prev(Location) != Location) is true.

This query effectively partitions the data by Location and then assigns a dense rank based on UnitsSold (highest UnitsSold gets rank 1, the next highest gets 2, etc.).

Resulting Table (abbreviated):

"Washington DC", "Contoso", 400, Rank 1 "Washington DC", "Litware", 300, Rank 2 "Seattle", "Contoso", 300, Rank 1 "Seattle", "Fabrikam", 100, Rank 2 "Seattle", "Litware", 100, Rank 2 "San Francisco", "Litware", 500, Rank 1 "San Francisco", "Relecloud", 500, Rank 1 "New York", "Litware", 1000, Rank 1 "New York", "Contoso", 300, Rank 2 "New York", "Relecloud", 300, Rank 2 "New York", "Fabrikam", 200, Rank 3

Statement Analysis:

1. Litware from New York...: No. The top row is "Washington DC", "Contoso" because of the sort by Location desc.
2. Fabrikam in Seattle...: Yes. In the "Seattle" group, "Contoso" (300) gets rank 1. "Fabrikam" (100) has the next highest UnitsSold value, so it gets rank 2. "Litware" (100) shares this rank.
3. Litware in San Francisco...: Yes. "Litware in San Francisco" (500) has the highest UnitsSold for its location, getting rank 1. "Litware in New York" (1000) also has the highest UnitsSold for its location, getting rank 1.

Microsoft (Azure Data Explorer Documentation): row_rank_dense() function.

This document explains that row_rank_dense(Term, Restart) assigns a rank starting at 1. The rank increments when Term changes, and the rank restarts at 1 when the Restart expression evaluates to true. In this case, the rank restarts for each new Location.

Source: https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/row-rank-dense-function

Microsoft (Azure Data Explorer Documentation): sort operator.

This document confirms that sort by Location desc will order the locations alphabetically in reverse, placing "Washington DC" before "New York".

Source: https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/sort-operator

Microsoft (Azure Data Explorer Documentation): prev() function.

This document clarifies that prev(Location) returns the value of the Location column from the preceding row, making the expression prev(Location) != Location the condition that identifies the first row of each new location group.

Source: https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/prev-function

The task is to apply Dynamic Data Masking (DDM) to an existing column.

1. Box 1 (ALTER): The ALTER TABLE command is required because the dbo.CreditCard table already exists, and we are modifying its properties.
2. Box 2 (ALTER): The ALTER COLUMN clause is used within ALTER TABLE to specify which column's definition is being modified—in this case, to add a mask.
3. Box 3 (PARTIAL): The PARTIAL function is the specific DDM function that masks data by showing a defined number of leading (prefix) and trailing (suffix) characters. The syntax PARTIAL(2, "XXXXXXXX", 4) directly maps to the requirement to show the first two characters (prefix=2) and the last four characters (suffix=4).

The final correct T-SQL statement would be: ALTER TABLE dbo.CreditCard ALTER COLUMN [CreditCard] ADD MASKED WITH (FUNCTION = 'PARTIAL(2,"XXXXXXXX",4)')

Microsoft Learn (Microsoft Fabric Documentation). Dynamic data masking in Microsoft Fabric data warehousing.

Section: "Implement dynamic data masking"

Explanation: This official documentation confirms that Dynamic Data Masking is the correct feature to use in a Fabric data warehouse to limit sensitive data exposure to non-privileged users (like the data analysts with the Viewer role).

Microsoft Learn (T-SQL Documentation). Dynamic Data Masking.

Sections: "Masking Functions" (sub-section "Partial") and "Examples" (sub-section "Adding a mask to an existing column").

Explanation: This document defines the T-SQL syntax. It shows that ALTER TABLE ... ALTER COLUMN ... ADD MASKED is the correct syntax for adding a mask to an existing column. It also explicitly defines the partial(prefix, [padding], suffix) function as the method for exposing a set number of first and last characters, which matches the question's requirement.

The recommendation must select a functional streaming solution.

1. Eventstream: This no-code/low-code option is disqualified. Eventstream is built on Azure Event Hubs, which has a 1 MB maximum message size limit. All three sources (10 MB, 25 MB, and 5 MB) exceed this limit, making Eventstream technically non-viable.
2. Streaming Dataflow: This option is retired and has been superseded by other Real-Time Intelligence features in Fabric.
3. A data pipeline: This is a batch orchestration tool (Data Factory) and does not meet the requirement for a "streaming solution."
4. Apache Spark Structured Streaming: This is the only remaining solution. Although it is code-intensive and violates the "minimize development effort" preference, it is the only tool in the list that can technically handle streaming data of all types (structured, semi-structured, binary) with message sizes far exceeding the 1 MB limit.

Microsoft Fabric Documentation (Event Hubs/Eventstream Limit): "Azure Event Hubs, which underlies Fabric Eventstream... The maximum size of an event [message] is 1 MB."

Source: Microsoft. (2024). Azure Event Hubs quotas and limits. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-quotas (Section: "Event Hubs quotas and limits").

Microsoft Fabric Documentation (Data Pipelines): "A data pipeline... is used to perform batch data movement and transformation tasks."

Source: Microsoft. (2024). What is Data Factory in Microsoft Fabric?. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/fabric/data-factory/data-factory-overview (Section: "Data pipelines").

Microsoft Documentation (Streaming Dataflows Retirement): "Streaming dataflows has been retired... We recommend migrating to Azure Stream Analytics on Azure or using the Spark Structured Streaming feature..."

Source: Microsoft. (2023). Streaming dataflows. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-streaming (Note block).

Apache Spark Documentation (Structured Streaming): "Structured Streaming is a scalable and fault-tolerant stream processing engine built on the Spark SQL engine... You can use the same DataFrame/Dataset API for batch and streaming." Spark is not limited by a 1 MB message size and can read binary files (for images).

Source: Apache Software Foundation. (2024). Structured Streaming Programming Guide. Apache Spark Documentation. Retrieved from https://spark.apache.org/docs/latest/structured-streaming-programming-guide.html.

To configure the ForEach activity (named "Extraction Loop"), its Items property must be set to an array from the output of the preceding activity.

1. The preceding activity is named Lookup Schema and Table.
2. The dynamic content expression to access another activity's output is @activity('ActivityName').
3. The Lookup activity returns its results (the list of tables) as an array within the value property of its output object.

Therefore, the correct expression to pass the array of tables to the ForEach loop is @activity('Lookup Schema and Table').output.value.

Microsoft Learn (Fabric Documentation): Lookup activity

Location: learn.microsoft.com/en-us/fabric/data-factory/lookup-activity

Reference: In the "Output" section, the documentation specifies that when the firstRowOnly property is set to false (the default), the Lookup activity's output contains a value property, which is the "List of rows returned from the data source." This list is the array that the ForEach activity needs.

Microsoft Learn (Fabric Documentation): Tutorial: Copy multiple tables in bulk

Location: learn.microsoft.com/en-us/fabric/data-factory/tutorial-bulk-copy-portal

Reference: In Step 5: Configure the ForEach activity, sub-step 3 instructs the user to set the Items property by adding dynamic content. The exact expression provided is @activity('LookupTableList').output.value (using "LookupTableList" as their example activity name), which directly maps to the scenario in the question.

Microsoft Learn (Fabric Documentation): ForEach activity

Location: learn.microsoft.com/en-us/fabric/data-factory/foreach-activity

Reference: The "Syntax" and "Properties" sections confirm that the items property expects a "collection to be iterated over" and can be defined using an expression, such as the output from another activity.

The mssparkutils.notebook.runMultiple() method is used to execute multiple notebooks, which can be structured as a Directed Acyclic Graph (DAG). To establish the required execution order where Load_Orders runs only after Load_Salesperson completes, you must define this relationship within the JSON configuration.

1. dependencies: This key is used within an activity's definition (in this case, Load_Orders) to specify an array of prerequisite activities (by name) that must complete successfully before this activity can begin.
2. runMultiple: This is the specific method within the mssparkutils.notebook utility that parses the JSON DAG and orchestrates the parallel and sequential execution of the defined notebook activities.

Source: Microsoft Learn (Official Vendor Documentation)

Article: Use Microsoft Spark utilities (mssparkutils) in Fabric

Section: mssparkutils.notebook.runMultiple(DAG)

Reference: The official documentation explicitly shows the runMultiple method is used to "run multiple notebooks in parallel or with a predefined topological structure (DAG)." The accompanying example code demonstrates that the dependencies key is used within the activities JSON array to define the execution order between notebooks. For instance, an activity "NotebookSimple2" is shown with "dependencies": ["NotebookSimple"] to make it run after "NotebookSimple". This directly validates the answer.

To add a constraint to an existing table, the correct Transact-SQL statement begins with ALTER TABLE.

In a Microsoft Fabric Data Warehouse, primary key constraints have two specific requirements:

1. They must be NONCLUSTERED. This is because the table's physical data structure is typically a CLUSTERED COLUMNSTORE INDEX (the default) or a heap, not a clustered index based on the primary key.
2. They must be NOT ENFORCED. Fabric is optimized for large-scale data ingestion and analytics. Enforcing uniqueness on every load operation would be a significant performance bottleneck. The system trusts that the data is unique, but it does not check, relying on upstream data integrity processes.

Therefore, the only valid sequence is to ALTER the table, ADD a NONCLUSTERED primary key, and specify that it is NOT ENFORCED.

Microsoft Learn. (n.d.). Primary keys, foreign keys, and unique keys in Warehouse in Microsoft Fabric. Retrieved November 14, 2025, from https://learn.microsoft.com/en-us/fabric/data-warehouse/table-constraints

Reference (Section: "Primary Key"): This document explicitly states, "Warehouse supports PRIMARY KEY and UNIQUE constraints, when NOT ENFORCED and NONCLUSTERED capabilities are used." This confirms the two key required attributes.

Microsoft Learn. (n.d.). Constraints in Microsoft Fabric. Retrieved November 14, 2025, from https://learn.microsoft.com/en-us/fabric/data-warehouse/constraints

Reference (Section: "Primary Key, Unique, and Foreign Key"): This documentation confirms the T-SQL syntax and limitations, noting that Fabric supports PRIMARY KEY constraints but they "must be NONCLUSTERED and NOT ENFORCED."

Microsoft Learn. (n.d.). ALTER TABLE table_constraint (Transact-SQL). Retrieved November 14, 2025, from https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-table-table-constraint-transact-sql?view=fabric

Reference (Section: "Syntax"): The official syntax for adding a table constraint is shown as: ALTER TABLE [ ... ] ADD CONSTRAINT [ ... ] { PRIMARY KEY | UNIQUE } [ NONCLUSTERED ] ( column [ ... ] ) [ NOT ENFORCED ]. This confirms the correct order of the provided code segments.

Statement 1: The row_cumsum() function calculates a cumulative (running) sum. The query is sorted by VendorID, and the second argument, VendorID != prev(VendorID), acts as a restart predicate. This predicate evaluates to true when the VendorID changes from the previous row, correctly restarting the cumulative sum of total_amount for each new VendorID partition.

Statement 2: The row_window_session() function calculates the starting value of a session. The query uses tpep_pickup_datetime as the time column, 1h as the maximum lookup window, and payment_type != prev(payment_type) as the restart predicate. This correctly identifies the first tpep_pickup_datetime value for each payment_type partition.

Microsoft Learn (Kusto Query Language): row_cumsum() function.

Location: Official documentation for Azure Data Explorer (KQL).

Reference: The documentation specifies the syntax row_cumsum(Column, [RestartPredicate]). It states, "The cumulative sum restarts when RestartPredicate (if provided) evaluates to true." This directly supports its use in Statement 1 for partitioning by VendorID.

Microsoft Learn (Kusto Query Language): row_window_session() function.

Location: Official documentation for Azure Data Explorer (KQL).

Reference: The documentation provides the syntax row_window_session(TimeColumn, MaxLookupWindow, [MinLookBack], [RestartPredicate]). It is used to "calculate session start values of a column." This matches the requirement in Statement 2 to find the first pickup time, using payment_type as the partition (restart predicate).

Microsoft Learn (Kusto Query Language): prev() function.

Location: Official documentation for Azure Data Explorer (KQL).

Reference: The documentation for the prev() function is essential for understanding the RestartPredicate used in both statements. It explains that prev(Column) returns the value of Column from the previous row in a serialized row set, which is fundamental to detecting a change in VendorID or payment_type.