PL-900 Demonstrate the capabilities of Power Apps Practice Question
A model-driven app uses a custom button that runs a Power Automate flow to send an email notification. Users report that the button sometimes does not appear on the command bar. The app maker checks the form customizations and confirms the button is configured correctly. What is the most likely cause?
⚠ Common exam trap
PL-900 often tests the distinction between a button being hidden due to visibility rules versus being disabled due to a broken flow or missing permission, so candidates must recognize that 'button missing entirely' points to display rules, not runtime failures.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The custom button is configured with visibility rules that hide it for certain security roles.
Command bar buttons in model-driven apps support visibility rules that can be scoped by security role, so a button configured correctly on the form can still be hidden from specific users if their role is excluded. Since the maker confirmed the form customization is correct, the most likely cause is role-based visibility logic that hides the button for the affected users.
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 user's browser does not support the Power Apps client.
Why it's wrong here
Browser capability is irrelevant: Power Apps runs in all current browsers and would block the whole app, not intermittently hide one command. Conditional command visibility is governed by the button's enable/visibility rules and form factor, so the browser is never the cause.
- ✗
The app is opened in the phone form factor, and the button is only shown on web.
Why it's wrong here
Command bar buttons can be restricted to specific form factors, so a phone user would not see a web-only button. However, the symptom is intermittent rather than device-specific, which points to rule-based visibility tied to record data or user permissions instead.
- ✓
The custom button is configured with visibility rules that hide it for certain security roles.
Why this is correct
Command bar buttons can be hidden by role-based visibility rules, so users lacking the required security role never see the button. Since the form customisation is confirmed correct, the differing security role assignments across users explain the intermittent absence.
- ✗
The Power Automate flow is disabled or not shared with the user.
Why it's wrong here
A disabled or unshared flow breaks the button's action, not its rendering; the command still appears and fails on click. Flow state is checked at run time, so it cannot explain a button vanishing from the command bar.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-900 question from scratch — 701 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.