Filter state, slicer selections, visual visibility, and selected data points

The entire data model, although plausible for report design, it describes chart presentation choices and not the specific feature semantics asked here.

Only filter settings, however, this interpretation reflects visual formatting behavior rather than the analytical intent evaluated by the question.

Only the current page, although plausible for report design, it describes chart presentation choices and not the specific feature semantics asked here.

A conditional formatting setup that affects color encoding only, while the prompt asks about navigation or analytical behavior

A layout optimization that changes user perception of the report but not the semantic rule being tested

Hierarchies are automatically created by Power BI, although plausible for report design, it describes chart presentation choices and not the specific feature semantics asked here.

In Model view, right-click a field and Create Hierarchy, then drag other fields into it

Hierarchies can only be created in Power Query, although plausible for report design, it describes chart presentation choices and not the specific feature semantics asked here.

Use DAX to create a hierarchy measure, however, this interpretation reflects visual formatting behavior rather than the analytical intent evaluated by the question.

CREATE in Service, ASSIGN in Desktop, although it appears secure at first glance, it does not reflect the required role-filter expression behavior in Power BI.

Both in Power BI Service, however, this mixes up security filter propagation rules and does not match how row-level security is actually evaluated.

Both in Power BI Desktop, although it appears secure at first glance, it does not reflect the required role-filter expression behavior in Power BI.

CREATE roles in Power BI Desktop, ASSIGN users in Power BI Service

A permission strategy that belongs to workspace access control rather than row-level data filtering rules

To share the report with others, although plausible for report design, it describes chart presentation choices and not the specific feature semantics asked here.

To create a backup of the dataset, however, this interpretation reflects visual formatting behavior rather than the analytical intent evaluated by the question.

To save a specific view/state of the report with applied filters

To save the entire report file, although plausible for report design, it describes chart presentation choices and not the specific feature semantics asked here.

A conditional formatting setup that affects color encoding only, while the prompt asks about navigation or analytical behavior

A function behavior that would be correct only if filter context were removed, which is not the condition defined in this question

Percentages always display correctly in Power BI, although it sounds technically credible, it does not align with how DAX functions propagate context in this scenario.

The data type is wrong, although it sounds technically credible, it does not align with how DAX functions propagate context in this scenario.

Percentages cannot be directly summed or averaged; you need to calculate Total Margin / Total Sales at the aggregate level

The visual is not configured correctly, however, this wording confuses row context, filter context, or evaluation timing and therefore misses the exact DAX behavior being tested.

When you need filters to flow in both directions, but use sparingly as it can cause ambiguity

Only for many-to-many relationships, although related to schema design, it does not describe the cardinality or relationship direction behavior asked in this item.

Always, for maximum flexibility, although related to schema design, it does not describe the cardinality or relationship direction behavior asked in this item.

Never, it's not recommended, however, this confuses data modeling structure with report-layer behavior and therefore misses the requested concept.

A schema decision that improves usability in the Fields pane but does not implement the required relational behavior

Sales for the current day only, although it sounds technically credible, it does not align with how DAX functions propagate context in this scenario.

Total sales for the entire year, although it sounds technically credible, it does not align with how DAX functions propagate context in this scenario.

A function behavior that would be correct only if filter context were removed, which is not the condition defined in this question

Year-over-year comparison, however, this wording confuses row context, filter context, or evaluation timing and therefore misses the exact DAX behavior being tested.

Running total from the beginning of the year to the current date in context

The cell will show an error, although plausible for report design, it describes chart presentation choices and not the specific feature semantics asked here.

The cell will have a green background, although plausible for report design, it describes chart presentation choices and not the specific feature semantics asked here.

The cell will have a red background

The cell will have no formatting, however, this interpretation reflects visual formatting behavior rather than the analytical intent evaluated by the question.

A conditional formatting setup that affects color encoding only, while the prompt asks about navigation or analytical behavior

A calculation pattern that is useful for measures in general but does not satisfy the specific context transition requirement here

Delete the OrderDate relationship, although it sounds technically credible, it does not align with how DAX functions propagate context in this scenario.

Use USERELATIONSHIP in a CALCULATE to activate the inactive relationship

Create two Date tables, however, this wording confuses row context, filter context, or evaluation timing and therefore misses the exact DAX behavior being tested.

It's not possible to filter by ShipDate, although it sounds technically credible, it does not align with how DAX functions propagate context in this scenario.

It forces all visuals to aggregate by row context instead of filter context

It guarantees bidirectional filtering without any ambiguity or performance impact, although related to schema design, it does not describe the cardinality or relationship direction behavior asked in this item.

A relationship setup that may work for simple visuals but breaks the model semantics expected for this analytical question

It removes the need for keys between tables because Power BI infers joins automatically

It creates predictable filter propagation from descriptive attributes to transactional data for accurate aggregations