Which function activates different physical relationships between tables during a query execution?

Which function activates different physical relationships between tables during a query execution?

• A. USERELATIONSHIP()
• B. TREATAS()
• C. CROSSFILTER()
• D. PATH()

Answer: (A)

Activating different physical relationships between tables during a query execution is done with USERELATIONSHIP() because it allows a specific, alternative relationship between two tables to be used for that calculation. When a model has multiple relationships between the same tables (for example, a fact table linked to a date table by both OrderDate and ShipDate), you can use this function inside a CALCULATE to choose which relationship to apply for that measure. For instance, to sum by ShipDate, you’d activate the ShipDate relationship just for that evaluation, leaving other relationships intact for other calculations. The other options don’t swap which physical relationship is used. TREATAS() creates a virtual relationship by applying filters from one table to another, without changing the actual relationships. CROSSFILTER() adjusts how existing relationships propagate filters (the direction or behavior) but doesn’t switch to a different relationship. PATH() traverses hierarchies in parent-child structures, not relationships between tables.

Activating different physical relationships between tables during a query execution is done with USERELATIONSHIP() because it allows a specific, alternative relationship between two tables to be used for that calculation. When a model has multiple relationships between the same tables (for example, a fact table linked to a date table by both OrderDate and ShipDate), you can use this function inside a CALCULATE to choose which relationship to apply for that measure. For instance, to sum by ShipDate, you’d activate the ShipDate relationship just for that evaluation, leaving other relationships intact for other calculations.

The other options don’t swap which physical relationship is used. TREATAS() creates a virtual relationship by applying filters from one table to another, without changing the actual relationships. CROSSFILTER() adjusts how existing relationships propagate filters (the direction or behavior) but doesn’t switch to a different relationship. PATH() traverses hierarchies in parent-child structures, not relationships between tables.