Cisco®
Oracle
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
All Vendors
  2. Home
  3. Exams
  4. Microsoft
  5. DP-600

Free Microsoft DP-600 Exam Braindumps (page: 7)

Page 7 of 41
PDF with 198 Questions

HOTSPOT (Drag and Drop is not supported)
You have a Fabric tenant that contains a workspace named Workspace1. Workspace1 contains a warehouse named DW1. DW1 contains two tables named Employees and Sales. All users have read access to Dw1.

You need to implement access controls to meet the following requirements:
For the Sales table, ensure that the users can see only the sales data from their respective region. For the Employees table, restrict access to all Personally Identifiable Information (PII).

Maintain access to unrestricted data for all the users.

What should you use for each table? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Column-level security
For the Employees table, restrict access to all Personally Identifiable Information (PII).

Synapse Analytics, Column-level security
Column-Level security allows customers to control access to table columns based on the user's execution context or group membership.

Column-level security simplifies the design and coding of security in your application, allowing you to restrict column access to protect sensitive data. For example, ensuring that specific users can access only certain columns of a table pertinent to their department.

Use cases
Some examples of how column-level security is being used today:
A financial services firm allows only account managers to have access to customer social security numbers (SSN), phone numbers, and other personal data.

A health care provider allows only doctors and nurses to have access to sensitive medical records while preventing members of the billing department from viewing this data.

Box 2: Row-level security (RLS)
For the Sales table, ensure that the users can see only the sales data from their respective region.

SQL Server, Row-level security
Row-level security (RLS) enables you to use group membership or execution context to control access to rows in a database table.

Row-level security simplifies the design and coding of security in your application. RLS helps you implement restrictions on data row access. For example, you can ensure that workers access only those data rows that
are pertinent to their department. Another example is to restrict customers' data access to only the data relevant to their company.

Use cases
Here are design examples of how row-level security (RLS) can be used:
A hospital can create a security policy that allows nurses to view data rows for their patients only.

A bank can create a policy to restrict access to financial data rows based on an employee's business division or role in the company.

A multitenant application can create a policy to enforce a logical separation of each tenant's data rows from every other tenant's rows. Efficiencies are achieved by the storage of data for many tenants in a single table. Each tenant can see only its data rows.


Reference:

https://learn.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/column-level-security https://learn.microsoft.com/en-us/sql/relational-databases/security/row-level-security



You have a Fabric tenant that contains a workspace named Workspace1 and a user named User1. User1 is assigned the Contributor role for Workspace1.

You plan to configure Workspace1 to use an Azure DevOps repository for version control. You need to ensure that User1 can commit items to the repository.

Which two settings should you enable for User1? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

  1. Users can sync workspace items with GitHub repositories
  2. Users can create and use Data workflows
  3. Users can create Fabric items
  4. Users can synchronize workspace items with their Git repositories

Answer(s): C,D

Explanation:

To integrate Git with your Microsoft Fabric workspace, you need to set up the following prerequisites for both Fabric and Git.

Fabric prerequisites
To access the Git integration feature, you need a Fabric capacity. A Fabric capacity is required to use all supported Fabric items
In addition, the following tenant switches must be enabled from the Admin portal:
* (C) Users can create Fabric items
* (D) Users can synchronize workspace items with their Git repositories
* For GitHub users only: Users can synchronize workspace items with GitHub repositories
These switches can be enabled by the tenant admin, capacity admin, or workspace admin, depending on your organization's settings.


Reference:

https://learn.microsoft.com/en-us/fabric/cicd/git-integration/git-get-started



You have a Fabric tenant that contains a workspace named Workspace1. Workspace1 contains a data pipeline named Pipeline1 and a lakehouse named Lakehouse1.

You perform the following actions:

-Create a workspace named Workspace2.
-
-Create a deployment pipeline named DeployPipeline1 that will deploy items from Workspace1 to Workspace2.
-
-Add a folder named Folder1 to Workspace1. Move Lakehouse1 to Folder1.
-
-Run DeployPipeline1.
-
Which structure will Workspace2 have when DeployPipeline1 is complete?

  1. \Folder1\Pipeline1
    \Folder1\Lakehouse1
  2. \Pipeline1
    \Lakehouse1
  3. \Pipeline1
    \Folder1\Lakehouse1
  4. \Folder1\Lakehouse1

Answer(s): D

Explanation:

The folder structure is copied.

Note 1:
Folders in deployment pipelines
Folders enable users to efficiently organize and manage workspace items in a familiar way. When you deploy content that contains folders to a different stage, the folder hierarchy of the applied items is automatically applied.

In Deployment pipelines, folders are considered part of an item’s name (an item name includes its full path). Note 2: Microsoft Fabric, The deployment pipelines process
The deployment process lets you clone content from one stage in the deployment pipeline to another, typically from development to test, and from test to production.

During deployment, Microsoft Fabric copies the content from the source stage to the target stage. The connections between the copied items are kept during the copy process.

Deploying content from a working production pipeline to a stage that has an existing workspace, includes the following steps:
Deploying new content as an addition to the content already there. Deploying updated content to replace some of the content already there.


Reference:

https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process



Your company has a finance department.

You have a Fabric tenant, an Azure Storage account named storage1, and a Microsoft Entra group named
Group1. Group1 contains the users in the finance department.

You need to create a new workspace named Workspace1 in the tenant. The solution must meet the following requirements:
Ensure that the finance department users can create and edit items in Workspace1. Ensure that Workspace1 can securely access storage1 to read and write data.

Ensure that you are the only admin of Workspace1. Minimize administrative effort.

You create Workspace1.

Which two actions should you perform next? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

  1. Assign the Contributor role to Group1.
  2. Create a workspace identity.
  3. Assign the Admin role to yourself.
  4. Assign the Contributor role to each finance department user.

Answer(s): A,B

Explanation:

A: Ensure that the finance department users can create and edit items in Workspace1. Group1 contains the users in the finance department.

B: Ensure that Workspace1 can securely access storage1 to read and write data.

A Fabric workspace identity is an automatically managed service principal that can be associated with a Fabric workspace. Fabric workspaces with a workspace identity can securely read or write to firewall-enabled Azure Data Lake Storage Gen2 accounts through trusted workspace access for OneLake shortcuts. Fabric items can use the identity when connecting to resources that support Microsoft Entra authentication. Fabric uses workspace identities to obtain Microsoft Entra tokens without the customer having to manage any credentials.

Workspace identities can be created in the workspace settings of any workspace except My workspaces. A workspace identity is automatically assigned the workspace contributor role and has access to workspace items.

Incorrect:
Not D: More administrative effort.


Reference:

https://learn.microsoft.com/en-us/fabric/security/workspace-identity



You have a Fabric tenant that contains the workspaces shown in the following table.



You have a deployment pipeline named Pipeline1 that deploys items from Workspace_DEV to Workspace_TEST. In Pipeline1, all items that have matching names are paired.

You deploy the contents of Workspace_DEV to Workspace_TEST by using Pipeline1. What will the contents of Workspace_TEST be once the deployment is complete?

  1. Lakehouse1 Lakehouse2 Notebook1 Notebook2 Pipeline1 SemanticModel1
  2. Lakehouse1 Notebook1 Pipeline1 SemanticModel1
  3. Lakehouse2 Notebook2 SemanticModel1
  4. Lakehouse2 Notebook2 Pipeline1 SemanticModel1

Answer(s): A

Explanation:

The items in Workspace_DEV is added to Workspace_TEST. The items already in Workspace_TEST are kept.

NOTE: Microsoft Fabric, The deployment pipelines process
The deployment process lets you clone content from one stage in the deployment pipeline to another, typically from development to test, and from test to production.

During deployment, Microsoft Fabric copies the content from the source stage to the target stage. The connections between the copied items are kept during the copy process.

Deploying content from a working production pipeline to a stage that has an existing workspace, includes the following steps:
Deploying new content as an addition to the content already there.

Deploying updated content to replace some of the content already there.


Reference:

https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process



Viewing page 7 of 41
Viewing questions 25 - 28 out of 198 questions



Post your Comments and Discuss Microsoft DP-600 exam prep with other Community members:

DP-600 Exam Discussions & Posts