The answer is that entity permissions for the ticket table are not configured for portal users. This is the most likely cause because Power Apps portals rely entirely on Dataverse entity permissions to control record visibility; without explicit 'Read' permissions assigned to a web role—such as 'Authenticated Users'—the portal cannot query or display any records, even those created by the user themselves. On the PL-900 exam, this concept tests your understanding that portal access is separate from data access, and a common trap is assuming that simply publishing the portal or using a modern browser grants record visibility. Remember: a portal user can log in and see the interface, but without entity permissions, Dataverse remains invisible to them. Memory tip: think of entity permissions as the "gatekeeper"—no permission, no records, no matter who created them.
PL-900 Practice Question: Describe the business value of Microsoft Power Platform
This PL-900 practice question tests your understanding of describe the business value of microsoft power platform. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company has a Power Apps portal for external partners to submit support tickets. Partners report that they cannot see the tickets they created. The portal uses Dataverse. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Entity permissions for the ticket table are not configured for portal users.
In Power Apps portals, visibility of Dataverse records is governed by entity permissions, not by the portal being published or the browser used. When partners cannot see tickets they created, the most likely cause is that the entity permissions for the ticket table are not configured to grant 'Read' access to the appropriate portal web roles (e.g., 'Authenticated Users' or a custom role). Without these permissions, the portal cannot query and display the records, even though the data exists in Dataverse.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The partners are using an unsupported browser.
Why it's wrong here
Browser compatibility would cause UI issues but not data access problems.
✓
Entity permissions for the ticket table are not configured for portal users.
Why this is correct
Portal users need specific entity permissions to read records; by default, they may not have access.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The portal is not published to the external network.
Why it's wrong here
If the portal were not published, partners would not be able to submit tickets at all.
✗
The Dataverse environment is in maintenance mode.
Why it's wrong here
Maintenance mode would prevent all operations, not just viewing.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume the issue is a network or browser problem, but the PL-900 exam specifically tests understanding that Power Apps portals rely on Dataverse security and entity permissions to control record visibility, not on portal publishing status or browser compatibility.
Detailed technical explanation
How to think about this question
Entity permissions in Power Apps portals are stored as records in the 'adx_entitypermission' table in Dataverse, and they define which web roles can perform CRUD operations on specific tables. The permission scope (e.g., 'Global', 'Account', 'Contact', 'Self') determines record visibility; for partners to see only their own tickets, the scope should be set to 'Contact' or 'Self' with a relationship to the ticket table's 'Customer' or 'Created By' field. A common misconfiguration is setting the scope to 'Global' without proper filtering, which can expose all records or none.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Describe the business value of Microsoft Power Platform — This question tests Describe the business value of Microsoft Power Platform — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Entity permissions for the ticket table are not configured for portal users. — In Power Apps portals, visibility of Dataverse records is governed by entity permissions, not by the portal being published or the browser used. When partners cannot see tickets they created, the most likely cause is that the entity permissions for the ticket table are not configured to grant 'Read' access to the appropriate portal web roles (e.g., 'Authenticated Users' or a custom role). Without these permissions, the portal cannot query and display the records, even though the data exists in Dataverse.
What should I do if I get this PL-900 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PL-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-900 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.