U.S. Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft PL-600 Exam - Topic 3 Question 79 Discussion

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.
C) Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI. and D) Share Power BI dashboards only with users who are supported to see this data.
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.

Microsoft PL-600 Exam - Topic 3 Question 79 Discussion

Actual exam question for Microsoft's PL-600 exam
Question #: 79
Topic #: 3
[All PL-600 Questions]

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.

Show Suggested Answer Hide Answer
Suggested Answer: C, D

by Ligia at Feb 12, 2025, 11:22 AM

Limited Time Offer

25%

Off

Get Premium PL-600 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Stefany
7 months ago
B is essential, no point in exporting sensitive data at all!
upvoted 0 times
...
Alyce
7 months ago
Wait, can you really enforce those restrictions in Power BI?
upvoted 0 times
...
Vanna
7 months ago
D seems a bit too limiting, what if more users need access?
upvoted 0 times
...
Rachael
8 months ago
I think C is the best option here, covers all bases!
upvoted 0 times
...
Keneth
8 months ago
A is definitely a good move for data security.
upvoted 0 times
...
Darrin
8 months ago
Sharing Power BI dashboards only with authorized users seems like a good practice, but I wonder if that alone is enough to secure sensitive data.
upvoted 0 times
...
Karl
8 months ago
I feel like option C makes sense too, but I can't recall if we specifically covered how to enforce that in both systems.
upvoted 0 times
...
Kizzy
8 months ago
I think limiting the role in Dynamics 365 Sales is crucial, especially to prevent data from being exported to Excel. That sounds familiar from our practice questions.
upvoted 0 times
...
Carli
8 months ago
I remember discussing the importance of using Microsoft Dataverse restrictions, but I'm not entirely sure if that's the best first step here.
upvoted 0 times
...
Lisbeth
8 months ago
Ah, I see. So it's all about ensuring the data restrictions carry over from Dynamics 365 to Power BI. I'll need to be really careful with the setup to make sure no sensitive information slips through. Definitely an important security consideration.
upvoted 0 times
...
Nobuko
8 months ago
This seems straightforward enough. I'll limit the Dynamics 365 Sales roles to only allow export of the necessary data, and then make sure the Power BI dashboards are only shared with the appropriate users. Shouldn't be too difficult to implement.
upvoted 0 times
...
Jolene
8 months ago
I'm a bit confused on the best approach here. Should I be focusing more on the Dynamics 365 Sales security or the Power BI side? I want to make sure I don't miss anything.
upvoted 0 times
...
Goldie
8 months ago
Okay, I think I have a plan. I'll need to use the Dataverse restrictions first, then limit the Dynamics 365 Sales roles to only allow access to the necessary data. That should help prevent sensitive information from being exported.
upvoted 0 times
...
Gayla
9 months ago
Hmm, this looks like a tricky one. I'll need to carefully consider the security implications and how to ensure the data restrictions carry over from Dynamics 365 to Power BI.
upvoted 0 times
...
Aileen
1 year ago
Ah, the age-old dilemma of data security versus productivity. I'd say C and D are the way to go - lock down the exports in both systems, and then carefully share the dashboards with the right folks. Although, I do hope the users don't try to hack the system and export the data themselves. That would be a real hoot, wouldn't it?
upvoted 0 times
Kelvin
1 year ago
Let's hope they don't try to export the data themselves, that would be a real headache!
upvoted 0 times
...
Sophia
1 year ago
D) Share Power BI dashboards only with users who are supported to see this data.
upvoted 0 times
...
Izetta
1 year ago
C) Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI.
upvoted 0 times
...
...
Nu
1 year ago
Hmm, let's see here. I'd say B and C are the way to go. Limit the roles in Dynamics, and then make sure that exporting to Excel is a no-go in both systems. Gotta keep those data leaks plugged up, am I right? Although, I do hope the users don't try to break out their crayons and draw their own charts...
upvoted 0 times
Aliza
1 year ago
Yeah, it's important to have those measures in place to protect the data. Let's hope the users stick to the approved dashboards.
upvoted 0 times
...
Malcom
1 year ago
Agreed, limiting roles in Dynamics and restricting exporting to Excel should help keep things secure.
upvoted 0 times
...
Ryan
1 year ago
B and C sound like a solid plan. We definitely don't want any sensitive data leaking out.
upvoted 0 times
...
...
Enola
1 year ago
Ah, the old 'hide it and they can't see it' approach. I like it! But seriously, C and D are the way to go. Gotta keep that sensitive data under lock and key, and then let the right people peek through the window. Simple as that!
upvoted 0 times
Carey
1 year ago
Agreed, it's all about controlling access to sensitive data.
upvoted 0 times
...
Veronika
1 year ago
Exactly, restricting export and sharing only with authorized users is key.
upvoted 0 times
...
Sean
1 year ago
D) Share Power BI dashboards only with users who are supported to see this data.
upvoted 0 times
...
Jovita
1 year ago
C) Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI.
upvoted 0 times
...
...
Elfriede
1 year ago
I believe we should also share Power BI dashboards only with users who are supported to see this data to ensure data security.
upvoted 0 times
...
Erick
1 year ago
Ah, the age-old balancing act between security and accessibility. It seems like C and D are the way to go here - lock down the exports in both Dynamics and Power BI, and then carefully share the dashboards with only the authorized users. No need to risk a data breach just to get some pretty visualizations!
upvoted 0 times
Rodolfo
1 year ago
D) Share Power BI dashboards only with users who are supported to see this data.
upvoted 0 times
...
Gerry
1 year ago
C) Limit the role and ensure that exporting to Microsoft Excel is not allowed in both Dynamics 365 Sales and Power BI.
upvoted 0 times
...
...
Theodora
1 year ago
I agree with Malissa. We need to make sure sensitive data is protected in both Dynamics 365 Sales and Power BI.
upvoted 0 times
...
Malissa
1 year ago
I think we should limit the role in Dynamics 365 Sales to only data allowed so it cannot be exported to Microsoft Excel.
upvoted 0 times
...

Save Cancel