Exam PL-600 All Questions

View all questions & answers for the PL-600 exam

Exam PL-600 topic 1 question 8 discussion

Actual exam question from Microsoft's PL-600

Question #: 8
Topic #: 1

A client uses Dynamics 365 Sales, Power BI datasets, and Power BI dataflows.
The Dynamics 365 Sales implementation has security roles that restrict data export. You need to ensure that data has the same restrictions in Power BI as it does in Dynamics 365 Sales.
You need to design the security to avoid sensitive data from being seen.
Which two actions should you recommend? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.

A. Use Microsoft Dataverse restrictions before setting up the Power BI reports.
B. Limit the role in Dynamics 365 Sales to only data allowed so it cannot be exported to Microsoft Excel.
C. Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI.
D. Share Power BI dashboards only with users who are supported to see this data.

Show Suggested Answer

Suggested Answer: CD 🗳️

by N8n0z at May 15, 2021, 2:37 p.m.

Comments

Submit Cancel

CDDT

Highly Voted 3 years, 11 months ago

Goals: 1) avoid sensitive data from seen, 2) prevent export to Excel from Power BI datasets. A. NO resolve 1) NO resolve 2) : I can see data different from D365 in Power BI if I don’t limit by R-L-S! B. NO resolve 1) NO resolve 2) : I can Export data from Power BI and I can see sensitive data from Power BI; C. NO resolve 1) OK resolve 2): I’m not able to export data from Power BI (disable option from dataset) and D365 (test) D. OK resolve 1) NO resolver 2) So C and D

upvoted 38 times

BrettusMaximus

3 years ago

C, D C is the only option to disable Power BI https://docs.microsoft.com/en-us/business-applications-release-notes/october18/intelligence-platform/power-bi-desktop/per-report-control-data-export

upvoted 6 times

...

Eskape

Highly Voted 3 years, 10 months ago

I would say A and C

upvoted 19 times

...

sky295

Most Recent 2 weeks, 2 days ago

Selected Answer: AD

Both Options B and C are incorrect !! Option B: "Limit the role in Dynamics 365 Sales to only data allowed so it cannot be exported to Microsoft Excel." - This is about preventing export in Dynamics 365, which doesn't help with Power BI. Option C: Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI - Similar to option B, and also about export. Therefore, A and D are the correct choices. As per docs, When Power BI uses a DirectQuery connection to Dataverse, security roles defined in Dataverse automatically apply role level security (RLS) in Power BI. Users see only data permitted by their Dynamics 365 security role." -- Option A Use workspace roles and dashboard sharing to limit access to sensitive reports. Combined with Dataverse role level security, this enforces end-to-end security. -- Option D

upvoted 1 times

...

Hamed64

3 weeks, 4 days ago

Selected Answer: AD

Not correct: B. Limit the role in Dynamics 365 Sales to only data allowed so it cannot be exported to Microsoft Excel While this helps within Dynamics 365, it doesn't directly control what users can see in Power BI. C. Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI Export restrictions are helpful, but they don’t enforce row-level security in Power BI. The focus should be on data access, not just export capabilities.

upvoted 1 times

...

MrEz

4 months ago

Selected Answer: CD

PowerBI is does not inherit the role permission from dataverse, they are independent (you could see data in PowerBI you are prohibited in Dataverse). c) therefore you would have to set up limits in dataverse AND Power BI d) sharing a power PI report gives access to the data (in dependent what you are prevented from seeing in dataverse)

upvoted 1 times

...

ManishKumarHouston

6 months, 2 weeks ago

Selected Answer: AC

Correct Answers: A. Use Microsoft Dataverse restrictions before setting up the Power BI reports. Reason: Microsoft Dataverse security roles enforce row-level and column-level security, which applies to data exported to Power BI. Setting up these restrictions ensures that users can only access data they are authorized to see. C. Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI. Reason: By restricting the ability to export data to Microsoft Excel in Dynamics 365 Sales, you prevent sensitive data from being inadvertently shared. Ensuring similar export restrictions in Power BI ensures that the data remains secure across both systems.

upvoted 2 times

...

8743423

7 months, 1 week ago

Selected Answer: AD

A. Use Microsoft Dataverse restrictions before setting up the Power BI reports. Explanation: Microsoft Dataverse is the underlying data platform for Dynamics 365, and it enforces security policies (such as row-level security) that can restrict access to sensitive data based on user roles. Using Dataverse restrictions in Power BI ensures that only authorized users can access the relevant data, maintaining consistency between Dynamics 365 Sales and Power BI. D. Share Power BI dashboards only with users who are supported to see this data. Explanation: Sharing Power BI dashboards only with users who have the appropriate permissions ensures that sensitive data is not inadvertently exposed to unauthorized individuals. This helps maintain the security model set in Dynamics 365 Sales by controlling access to the data at the Power BI level.

upvoted 2 times

...

RSITS

1 year ago

I say A & C: A: related with the "avoid sensitive data from being seen" condition. We can setup field level security so only the allowed users can see sensitive data. C: related to the condition of ensure that no export is allowed as is configured previously. "The Dynamics 365 Sales implementation has security roles that restrict data export. You need to ensure that data has the same restrictions in Power BI as it does in Dynamics 365 Sales."

upvoted 1 times

...

amifar

1 year, 6 months ago

Selected Answer: CD

I would say C and D.

upvoted 2 times

...

sabinsharma

1 year, 10 months ago

I agree it should be C and D

upvoted 2 times

...

Cloudz_1

2 years, 1 month ago

Selected Answer: CD

C and D

upvoted 3 times

...

Parth91

2 years, 2 months ago

Selected Answer: CD

C. Limiting the role and ensuring that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI can help ensure that data export is restricted to both tools. By restricting data export at both ends, it is possible to ensure that sensitive data is not leaked. D. Sharing Power BI dashboards only with users who are authorized to see the data can help ensure that sensitive data is not leaked. By restricting access to Power BI dashboards, it is possible to ensure that only authorized users can view the data. This can also help ensure that unauthorized users do not have the ability to export data from Power BI.

upvoted 1 times

...

Parth91

2 years, 2 months ago

Selected Answer: CD

C. Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI. D. Share Power BI dashboards only with users who are supported to see this data. By limiting the role in Dynamics 365 Sales and ensuring that exporting to Microsoft Excel is not allowed, sensitive data can be restricted from being exported to Power BI. Additionally, sharing Power BI dashboards only with users who are authorized to see the data can further ensure that sensitive data is not exposed. Using Microsoft Dataverse restrictions before setting up the Power BI reports can also help to limit access to sensitive data.

upvoted 2 times

...

Ninashnash

2 years, 3 months ago

Selected Answer: AD

A. Use Microsoft Dataverse restrictions before setting up the Power BI reports. This option is recommended because Microsoft Dataverse, as a data platform for Dynamics 365, provides an additional layer of security and access control. By applying the appropriate Dataverse restrictions before setting up the Power BI reports, you can ensure that data in Power BI respects the same security roles and restrictions as in Dynamics 365 Sales. D. Share Power BI dashboards only with users who are supported to see this data. This option is recommended because it involves sharing Power BI dashboards only with users who are supposed to see the data, which helps maintain the same level of data access restrictions as in Dynamics 365 Sales. This ensures that sensitive data is only accessible to authorized users in Power BI, similar to the access control in Dynamics 365 Sales.

upvoted 4 times

Ninashnash

2 years, 3 months ago

Why not B and C? B. Limit the role in Dynamics 365 Sales to only data allowed so it cannot be exported to Microsoft Excel. This option is not recommended because it only focuses on limiting the role in Dynamics 365 Sales to data that can be exported to Microsoft Excel. Power BI can access and display data from Dynamics 365 Sales through various means, not just Excel exports. Limiting the role to data that can be exported to Excel does not guarantee the same level of data protection in Power BI as in Dynamics 365 Sales. C. Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI. This option is not recommended because it only focuses on limiting the exporting of data to Microsoft Excel, which is not sufficient to ensure the same data restrictions in Power BI as in Dynamics 365 Sales. Data can be accessed in Power BI through various other means, so limiting the role to not allow data exporting to Excel does not completely address the issue.

upvoted 3 times

...

EgyEng

2 years, 5 months ago

C & D You can prevent data export form both security role and Power BI https://community.powerbi.com/t5/Service/Disable-Data-Export-just-to-a-particular-report/m-p/556601

upvoted 1 times

...

waltXc

2 years, 6 months ago

ChatGPT says it's C and D :D , I don't know how right it is.

upvoted 1 times

DimpleG

2 years, 5 months ago

for me it suggests B and D To ensure that data has the same restrictions in Power BI as it does in Dynamics 365 Sales, I would recommend the following two actions: B. Limit the role in Dynamics 365 Sales to only data allowed so it cannot be exported to Microsoft Excel: This will restrict the data export in Dynamics 365 Sales itself, preventing users from exporting data to Microsoft Excel or other applications, and ensure that only the allowed data is accessed by the users. D. Share Power BI dashboards only with users who are authorized to see this data: This will ensure that only authorized users can access and view the Power BI dashboards that contain Dynamics 365 Sales data. The sharing settings in Power BI can be used to limit access to the dashboards, and users can be added or removed based on their roles and responsibilities. Therefore, the recommended actions are B and D.

upvoted 1 times

...

dlnuser

2 years, 6 months ago

CD should be correct. A is not necessary because access to the Dataverse database is already regulated by the same security roles as the ones in Dynamics 365. Presumably, if RLS is necessary to hide sensitive data, this should also have already been configured--the question does specify that our only task is to replicate the restriction in Power BI, and if the Dataverse dataset is already properly secured, it will still be secured when used for Power BI visualizations. B is already done as per the question. C is necessary to restrict data export in Power BI. People can export data from Power BI reports if it's not also restricted in Power BI, and this is not already done as the question only mentions D365 security being set up.

upvoted 1 times

...

Load full discussion...