Pass Your Microsoft DP-600 Exam Easy!

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 Consider source-side materialization or reusable measures based on intended semantics. because model size and refresh work may fall when unnecessary calculated columns are removed.

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 Consider source-side materialization or reusable measures based on intended semantics. because model size and refresh work may fall when unnecessary calculated columns are removed.

This action is appropriate when a semantic model stores transaction GUIDs in multiple high-cardinality string columns that reports never use. Wide high-cardinality data can consume memory without adding analytical value. However, the question instead requires Consider source-side materialization or reusable measures based on intended semantics. because model size and refresh work may fall when unnecessary calculated columns are removed.

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 Check inherited access through the user's Fabric workspace role. because workspace-level permissions can confer capabilities across multiple items independent of direct shares.

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 Check inherited access through the user's Fabric workspace role. because workspace-level permissions can confer capabilities across multiple items independent of direct shares.

This action is appropriate when a model owner must manage workspace content and access settings on behalf of the analytics team. Administrative operations require broader workspace capabilities than ordinary report consumption. However, the question instead requires Check inherited access through the user's Fabric workspace role. because workspace-level permissions can confer capabilities across multiple items independent of direct shares.

This action is appropriate when a report viewer can open the report but cannot create their own report from its underlying model. Viewing a report and authoring new content on the model are different permission paths. However, the question instead requires Revoke the overbroad share and grant access to an approved security group. because a scoped audience better enforces intended information exposure than an unrestricted sharing link.

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 Revoke the overbroad share and grant access to an approved security group. because a scoped audience better enforces intended information exposure than an unrestricted sharing link.

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 Revoke the overbroad share and grant access to an approved security group. because a scoped audience better enforces intended information exposure than an unrestricted sharing link.

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 Use appropriate workspace and model management permissions in addition to RLS. because row filters restrict query results, not who can administer the data model.

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 Use appropriate workspace and model management permissions in addition to RLS. because row filters restrict query results, not who can administer the data model.

This action is appropriate when a manager can access two territories and a hard-coded RLS role displays only one. Identity-driven mappings support more than one authorized region without rewriting static role expressions. However, the question instead requires Use appropriate workspace and model management permissions in addition to RLS. because row filters restrict query results, not who can administer the data model.

This action is appropriate when a partner should not discover a confidential compensation table through a semantic model at all. OLS hides a table or column rather than merely filtering its rows. However, the question instead requires Narrow the OneLake security role to the approved table objects. because object selection in a role prevents a coarse data grant from exposing unrelated datasets.

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 Narrow the OneLake security role to the approved table objects. because object selection in a role prevents a coarse data grant from exposing unrelated datasets.

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 Narrow the OneLake security role to the approved table objects. because object selection in a role prevents a coarse data grant from exposing unrelated datasets.

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 Check organization label policies and whether the Fabric labeling feature is enabled for the intended users. because published label definitions are not automatically available to every user and workload.

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 Check organization label policies and whether the Fabric labeling feature is enabled for the intended users. because published label definitions are not automatically available to every user and workload.

This action is appropriate when an analyst assumes changing a sensitivity label automatically grants a colleague permission to open an item. Labels and ACLs are different controls: classification does not create read access. However, the question instead requires Check organization label policies and whether the Fabric labeling feature is enabled for the intended users. because published label definitions are not automatically available to every user and workload.

This action is appropriate when a company requires formally validated shared semantic models to be distinguishable from merely popular drafts. Certification is a governed trust mark beyond informal promotion. However, the question instead requires Route certification through the designated Fabric certification administrators or approved process. because the certification privilege can be governed separately from item creation.

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 Route certification through the designated Fabric certification administrators or approved process. because the certification privilege can be governed separately from item creation.

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 Route certification through the designated Fabric certification administrators or approved process. because the certification privilege can be governed separately from item creation.

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 Review the SQL endpoint access mode and its governing security policy before changing it. because user identity and delegated identity evaluate permissions through different paths.

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 Review the SQL endpoint access mode and its governing security policy before changing it. because user identity and delegated identity evaluate permissions through different paths.

This action is appropriate when a data analyst requires read-only access to one governed OneLake table through several Fabric engines. Data-plane policies can apply consistently across eligible engines without broad workspace edit rights. However, the question instead requires Review the SQL endpoint access mode and its governing security policy before changing it. because user identity and delegated identity evaluate permissions through different paths.

This action is appropriate when an outside collaborator receives a report link but lacks permission to the shared semantic model behind it. Successful report access depends on all underlying content permissions. However, the question instead requires Grant read or Build access as needed while withholding edit or workspace-author rights. because the principle of least privilege separates querying a model from changing its definitions.

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 Grant read or Build access as needed while withholding edit or workspace-author rights. because the principle of least privilege separates querying a model from changing its definitions.

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 Grant read or Build access as needed while withholding edit or workspace-author rights. because the principle of least privilege separates querying a model from changing its definitions.

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 Review sharing changes and relevant audit logs, then document the authorized audience. because governance review connects a sharing event to traceable ownership and approval.

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 Review sharing changes and relevant audit logs, then document the authorized audience. because governance review connects a sharing event to traceable ownership and approval.

This action is appropriate when a compliance analyst wants to discover all items with a restricted sensitivity classification. Central inventory allows classification review across workspaces. However, the question instead requires Review sharing changes and relevant audit logs, then document the authorized audience. because governance review connects a sharing event to traceable ownership and approval.

This action is appropriate when a model author sees full data while a Viewer only sees an authorized subset. Effective row visibility can differ by principal even on a shared model. However, the question instead requires Inspect the data source access model and the required model connection identity. because build authorizes model reuse, not necessarily read rights on separate source items.

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 Inspect the data source access model and the required model connection identity. because build authorizes model reuse, not necessarily read rights on separate source items.

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 Inspect the data source access model and the required model connection identity. because build authorizes model reuse, not necessarily read rights on separate source items.