Pass Your Microsoft DP-600 Exam Easy!

This action is appropriate when a model creates hundreds of calculated columns for values that can be computed in source SQL. Model size and refresh work may fall when unnecessary calculated columns are removed. However, the question instead requires Move stable descriptions to an appropriate dimension when relationships support it. because dimensional normalization can reduce repeated text and improve compression.

This action is appropriate when a model uses bidirectional filters on every relationship and reports contain ambiguous results. Relationship design affects both query work and analytical correctness. However, the question instead requires Move stable descriptions to an appropriate dimension when relationships support it. because dimensional normalization can reduce repeated text and improve compression.

This action is appropriate when a model consumes high memory during refresh and the team assumes adding a second report page will solve it. Data model memory pressure cannot be fixed by a cosmetic change to report layout. However, the question instead requires Move stable descriptions to an appropriate dimension when relationships support it. because dimensional normalization can reduce repeated text and improve compression.

This action is appropriate when a guest loses an approved contract role, but previously authorized workspace access remains. Access reviews must cover all effective permissions rather than only identity deactivation elsewhere. However, the question instead requires Use the Contributor workspace role when its authoring capabilities match the duty. because contributor permits eligible item authoring without the full access administration powers of higher roles.

This action is appropriate when a finance viewer should browse approved reports but must not edit workspace items. Viewer is the least powerful standard workspace role, and viewing a report may still require data access. However, the question instead requires Use the Contributor workspace role when its authoring capabilities match the duty. because contributor permits eligible item authoring without the full access administration powers of higher roles.

This action is appropriate when an auditor wants to explain why an analyst can edit a model despite no direct item sharing invitation. Workspace-level permissions can confer capabilities across multiple items independent of direct shares. However, the question instead requires Use the Contributor workspace role when its authoring capabilities match the duty. because contributor permits eligible item authoring without the full access administration powers of higher roles.

This action is appropriate when a published model is shared to a broad organization-wide link despite containing restricted financial metrics. A scoped audience better enforces intended information exposure than an unrestricted sharing link. However, the question instead requires Review separate item permissions and applicable OneLake data permissions. because control-plane access and underlying data-plane authorization must both be evaluated.

This action is appropriate when an analyst has a workspace Viewer role but still cannot query a particular restricted dataset. Workspace membership does not automatically override fine-grained data security restrictions. However, the question instead requires Review separate item permissions and applicable OneLake data permissions. because control-plane access and underlying data-plane authorization must both be evaluated.

This action is appropriate when a partner must view one approved report without editing unrelated workspace assets. Item sharing narrows exposure when a user only needs one published asset. However, the question instead requires Review separate item permissions and applicable OneLake data permissions. because control-plane access and underlying data-plane authorization must both be evaluated.

This action is appropriate when a reviewer needs to validate how a role filters rows without changing production user membership. Role simulation helps detect filter mistakes before granting real users access. However, the question instead requires Test effective RLS as the actual consuming identity and inspect its model-role assignments. because testing as a privileged author can mask the restrictions applied to ordinary viewers.

This action is appropriate when regional sales users should each see only sales records for their assigned territory in one semantic model. RLS limits the rows returned to a user without maintaining duplicated models per region. However, the question instead requires Test effective RLS as the actual consuming identity and inspect its model-role assignments. because testing as a privileged author can mask the restrictions applied to ordinary viewers.

This action is appropriate when a team thinks an RLS predicate will prevent a dataset administrator from changing model permissions. Row filters restrict query results, not who can administer the data model. However, the question instead requires Test effective RLS as the actual consuming identity and inspect its model-role assignments. because testing as a privileged author can mask the restrictions applied to ordinary viewers.

This action is appropriate when a read-only data role accidentally includes both public and restricted Delta tables. Object selection in a role prevents a coarse data grant from exposing unrelated datasets. However, the question instead requires Define scoped OneLake security roles for the approved file paths. because file and folder authorization must be set at the data plane, not inferred from folder naming.

This action is appropriate when a user belongs to several OneLake roles and gains more data visibility than the author expected. Multiple grants can combine, so a restrictive role does not cancel a separate broad permission. However, the question instead requires Define scoped OneLake security roles for the approved file paths. because file and folder authorization must be set at the data plane, not inferred from folder naming.

This action is appropriate when a compliance role may see a customer table but not the national-identifier column. CLS prevents sensitive columns from being exposed through an otherwise authorized table. However, the question instead requires Define scoped OneLake security roles for the approved file paths. because file and folder authorization must be set at the data plane, not inferred from folder naming.

This action is appropriate when an incident reveals that one workspace's classification label is outdated after its business data became regulated. Labels should track actual content sensitivity rather than remain a one-time setup step. However, the question instead requires Review the label's supported downstream protection and export behavior. because sensitivity label effects vary by artifact and export path and should be tested.

This action is appropriate when a published profit report contains confidential customer details and needs a visible protection classification. Labels communicate and can help enforce organizational information protection policies. However, the question instead requires Review the label's supported downstream protection and export behavior. because sensitivity label effects vary by artifact and export path and should be tested.

This action is appropriate when a tenant has labels defined but workspace authors cannot select them on Fabric items. Published label definitions are not automatically available to every user and workload. However, the question instead requires Review the label's supported downstream protection and export behavior. because sensitivity label effects vary by artifact and export path and should be tested.

This action is appropriate when a report owner cannot certify a shared dataset because they lack the required organizational authority. The certification privilege can be governed separately from item creation. However, the question instead requires Validate freshness and correctness independently of item endorsement. because endorsement indicates recommended status, not automatic numerical correctness.

This action is appropriate when a project shares an endorsed data product but consumers still receive an access denied message. Endorsement is discoverability metadata and cannot replace authorization. However, the question instead requires Validate freshness and correctness independently of item endorsement. because endorsement indicates recommended status, not automatic numerical correctness.

This action is appropriate when several reports appear in the catalog and consumers need to identify their team's recommended version. Promotion signals an owner's recommendation but does not itself grant data access. However, the question instead requires Validate freshness and correctness independently of item endorsement. because endorsement indicates recommended status, not automatic numerical correctness.

This action is appropriate when a data owner grants ReadAll on a restricted lakehouse and assumes a later fine-grained role automatically reduces it. A separate full-data grant can defeat intended least-privilege isolation. However, the question instead requires Define supported row restrictions at the data plane or semantic model. because workspace creation rights are not a substitute for row-level data filtering.

This action is appropriate when a user can manage a lakehouse item but is surprised by a restricted table governed through OneLake security. Control-plane management and table-row data visibility are distinct permission scopes. However, the question instead requires Define supported row restrictions at the data plane or semantic model. because workspace creation rights are not a substitute for row-level data filtering.

This action is appropriate when a lakehouse SQL endpoint shows different security behavior when switching from delegated to user identity. User identity and delegated identity evaluate permissions through different paths. However, the question instead requires Define supported row restrictions at the data plane or semantic model. because workspace creation rights are not a substitute for row-level data filtering.

This action is appropriate when an external analyst requests permission to update Power BI semantic measures despite only needing read access. The principle of least privilege separates querying a model from changing its definitions. However, the question instead requires Replace organization-wide sharing with a governed access group and owner approval. because broad sharing expands the audience beyond the stated business requirement.

This action is appropriate when a partner's guest account is disabled but an active service principal continues to consume shared data. Service identities are independent access paths that a guest account review might miss. However, the question instead requires Replace organization-wide sharing with a governed access group and owner approval. because broad sharing expands the audience beyond the stated business requirement.

This action is appropriate when a temporary external consultant needs a single published dashboard for a two-week engagement. Limited duration and scope reduce exposure beyond the approved engagement. However, the question instead requires Replace organization-wide sharing with a governed access group and owner approval. because broad sharing expands the audience beyond the stated business requirement.

This action is appropriate when a policy team needs to prevent new confidential datasets from being published without classification. Programmatic or procedural enforcement is more reliable than an optional description field. However, the question instead requires Export and review effective role membership and data permission assignments. because security assessment needs actual grants, not assumptions about item ownership.

This action is appropriate when a regulated team must demonstrate who changed a semantic model and when. Traceable activity records help establish change accountability. However, the question instead requires Export and review effective role membership and data permission assignments. because security assessment needs actual grants, not assumptions about item ownership.

This action is appropriate when a production report is shared using an unreviewed link and the team needs an access history. Governance review connects a sharing event to traceable ownership and approval. However, the question instead requires Export and review effective role membership and data permission assignments. because security assessment needs actual grants, not assumptions about item ownership.

This action is appropriate when a report consumer has Build permission but cannot connect to a protected source lakehouse. Build authorizes model reuse, not necessarily read rights on separate source items. However, the question instead requires Verify the effective connection identity and model security before assuming delegated per-user filtering. because fixed identity and single sign-on yield different security evaluation behavior.

This action is appropriate when a team combines OneLake table access rules and semantic RLS and sees unexpected effective filters. Layered security can create compounded restrictions that require end-to-end verification. However, the question instead requires Verify the effective connection identity and model security before assuming delegated per-user filtering. because fixed identity and single sign-on yield different security evaluation behavior.

This action is appropriate when a user can query a warehouse via SQL but receives an error opening its semantic model. Source SQL permissions do not automatically establish access to a separate semantic model item. However, the question instead requires Verify the effective connection identity and model security before assuming delegated per-user filtering. because fixed identity and single sign-on yield different security evaluation behavior.