Pass Your Microsoft DP-600 Exam Easy!

This action is appropriate when a fact table includes a verbose description repeated across millions of rows. Dimensional normalization can reduce repeated text and improve compression. However, the question instead requires Simplify to a clear star schema with controlled filter directions. because relationship design affects both query work and analytical correctness.

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 Simplify to a clear star schema with controlled filter directions. because relationship design affects both query work and analytical correctness.

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 Simplify to a clear star schema with controlled filter directions. because relationship design affects both query work and analytical correctness.

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 Remove or adjust the guest's workspace membership and recheck direct item grants. because access reviews must cover all effective permissions rather than only identity deactivation elsewhere.

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 Remove or adjust the guest's workspace membership and recheck direct item grants. because access reviews must cover all effective permissions rather than only identity deactivation elsewhere.

This action is appropriate when an engineer creates pipelines and notebooks but should not manage other users' workspace membership. Contributor permits eligible item authoring without the full access administration powers of higher roles. However, the question instead requires Remove or adjust the guest's workspace membership and recheck direct item grants. because access reviews must cover all effective permissions rather than only identity deactivation elsewhere.

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 Inspect the item's permissions and the applicable data-level access rules. because workspace membership does not automatically override fine-grained data security restrictions.

This action is appropriate when an engineer gives a colleague read access to a lakehouse and assumes it also authorizes unrestricted table-file reads. Control-plane access and underlying data-plane authorization must both be evaluated. However, the question instead requires Inspect the item's permissions and the applicable data-level access rules. because workspace membership does not automatically override fine-grained data security restrictions.

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 Inspect the item's permissions and the applicable data-level access rules. because workspace membership does not automatically override fine-grained data security restrictions.

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 the supported View as role or equivalent role-testing workflow. because role simulation helps detect filter mistakes before granting real users access.

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 the supported View as role or equivalent role-testing workflow. because role simulation helps detect filter mistakes before granting real users access.

This action is appropriate when a report passes desktop testing but a non-admin user sees all rows after publication. Testing as a privileged author can mask the restrictions applied to ordinary viewers. However, the question instead requires Use the supported View as role or equivalent role-testing workflow. because role simulation helps detect filter mistakes before granting real users access.

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 Review cumulative effective role grants and any overly broad DefaultReader assignment. because multiple grants can combine, so a restrictive role does not cancel a separate broad permission.

This action is appropriate when two research groups may read separate folders in one shared lakehouse Files area. File and folder authorization must be set at the data plane, not inferred from folder naming. However, the question instead requires Review cumulative effective role grants and any overly broad DefaultReader assignment. because multiple grants can combine, so a restrictive role does not cancel a separate broad permission.

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 Review cumulative effective role grants and any overly broad DefaultReader assignment. because multiple grants can combine, so a restrictive role does not cancel a separate broad permission.

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 Reassess the data classification and update the affected item's label through governance review. because labels should track actual content sensitivity rather than remain a one-time setup step.

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 Reassess the data classification and update the affected item's label through governance review. because labels should track actual content sensitivity rather than remain a one-time setup step.

This action is appropriate when a report export must retain appropriate information protection when moved into a supported Office format. Sensitivity label effects vary by artifact and export path and should be tested. However, the question instead requires Reassess the data classification and update the affected item's label through governance review. because labels should track actual content sensitivity rather than remain a one-time setup step.

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 Check share permissions and underlying dataset security in addition to endorsement. because endorsement is discoverability metadata and cannot replace authorization.

This action is appropriate when a recently promoted dataset has stale calculations and analysts assume the badge guarantees accuracy. Endorsement indicates recommended status, not automatic numerical correctness. However, the question instead requires Check share permissions and underlying dataset security in addition to endorsement. because endorsement is discoverability metadata and cannot replace authorization.

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 Check share permissions and underlying dataset security in addition to endorsement. because endorsement is discoverability metadata and cannot replace authorization.

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 effective broad ReadAll grants before relying on restrictive OneLake roles. because a separate full-data grant can defeat intended least-privilege isolation.

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 effective broad ReadAll grants before relying on restrictive OneLake roles. because a separate full-data grant can defeat intended least-privilege isolation.

This action is appropriate when a workspace role gives an engineer item creation rights, but an owner wants to restrict customer rows in all queries. Workspace creation rights are not a substitute for row-level data filtering. However, the question instead requires Review effective broad ReadAll grants before relying on restrictive OneLake roles. because a separate full-data grant can defeat intended least-privilege isolation.

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 Audit nonhuman and user principals separately and revoke the no-longer-approved data grants. because service identities are independent access paths that a guest account review might miss.

This action is appropriate when a user shares a dataset to the entire company to avoid handling access requests. Broad sharing expands the audience beyond the stated business requirement. However, the question instead requires Audit nonhuman and user principals separately and revoke the no-longer-approved data grants. because service identities are independent access paths that a guest account review might miss.

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 Audit nonhuman and user principals separately and revoke the no-longer-approved data grants. because service identities are independent access paths that a guest account review might miss.

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 Configure applicable governance controls and review compliance rather than relying on naming. because programmatic or procedural enforcement is more reliable than an optional description field.

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 Configure applicable governance controls and review compliance rather than relying on naming. because programmatic or procedural enforcement is more reliable than an optional description field.

This action is appropriate when a storage owner wants evidence of which security roles currently grant access to a sensitive table. Security assessment needs actual grants, not assumptions about item ownership. However, the question instead requires Configure applicable governance controls and review compliance rather than relying on naming. because programmatic or procedural enforcement is more reliable than an optional description field.

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 Test the intersection of effective model restrictions and OneLake security for each principal. because layered security can create compounded restrictions that require end-to-end verification.

This action is appropriate when a semantic model uses a fixed cloud connection identity and an architect assumes every reader's SQL RLS is applied automatically. Fixed identity and single sign-on yield different security evaluation behavior. However, the question instead requires Test the intersection of effective model restrictions and OneLake security for each principal. because layered security can create compounded restrictions that require end-to-end verification.

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 Test the intersection of effective model restrictions and OneLake security for each principal. because layered security can create compounded restrictions that require end-to-end verification.