Publishing an app scopes visibility to RPT1, RPT2, and DB1 while hiding RPT3
You have a Power BI tenant that contains a workspace named WS1. WS1 contains the following items: • A semantic model named SM1. • A report named RPT1 that is connected to SM1. • A report named RPT2 that is connected to SM1. • A report named RPT3 that is connected to SM1. • A dashboard named DB1 that contains content from RPT1 and RPT2. You need to grant workspace access to a group named Group1. The solution must meet the following requirements: • Group1 must be able to view RPT1, RPT2, and DB1. • Group1 must be prevented from viewing RPT3. • Group1 must be prevented from creating new reports and dashboards by using SM1. • Group1 must be prevented from sharing the reports and dashboards to other users. • Administrative effort must be minimized. What should you do?
Community Votes
75% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
An app publishes a hand-picked subset of workspace content to an audience — viewers get exactly the chosen reports and dashboard, with no model access and no share rights, all configured once.
Group1 must view RPT1, RPT2, and dashboard DB1 but not RPT3, must not build new content from SM1, must not be able to share onward, and the setup must minimize administrative effort.
Assigning the Viewer workspace role — it exposes every item in WS1 including RPT3, which is the first thing the requirements forbid.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Publishing an app (A) lets you select precisely which reports and dashboards enter the app — RPT1, RPT2, and DB1 in, RPT3 out. App consumers hold read-only access to that packaged content: they cannot connect to SM1 to author new reports or dashboards, cannot reshare app content, and the single publish action covers the whole group at once, minimizing administrative effort on every requirement.Why the Other Options Are Wrong
The Viewer role for WS1 (B) grants visibility of all workspace content including RPT3, breaching the exclusion requirement outright. A OneDrive shared folder (C) distributes PBIX files as raw artifacts — recipients could open the model and build from it, violating the no-authoring rule while adding file-management overhead. Sharing each item individually (D) means three separate share operations to maintain, and share links carry reshare options that must be managed per item — the opposite of minimal effort.Community Comment Notes
A well-endorsed comment explains that publishing an app allows selectively including RPT1, RPT2, and DB1 while excluding RPT3, with no model access and no sharing. The OneDrive camp's reasoning relies on users opening PBIX files, which both breaches the authoring restriction and maximizes administrative effort.Official Reference
Related Analysis
Practice All PL-300 Questions
Access 116 questions with complete answers and detailed explanations.
View Full PL-300 Practice Test →