PL-900 Demonstrate the capabilities of Power Apps Practice Question
Which THREE of the following are capabilities of model-driven apps? (Choose THREE.)
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
✓
Business rules to enforce data validation on forms.
Option B is correct because model-driven apps support business rules that run on forms and at the data layer to enforce validation, set field values, and control visibility without writing code. Option D is correct because model-driven apps render in the Unified Interface, which provides a consistent, touch-optimized experience across tablet and mobile devices via the Power Apps mobile app. Option E is correct because the Unified Interface is responsive and automatically adapts its layout and controls to the available screen size and orientation. Option A is not correct because drag-and-drop custom layout design is a hallmark of canvas apps, whereas model-driven apps derive their layout from the data model and form designer rather than free-form drag-and-drop placement. Option C is not correct because a built-in camera control for capturing images is a canvas app control/media capability, not an inherent model-driven app capability.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ability to design custom layouts using drag-and-drop.
Why it's wrong here
Drag-and-drop layout design belongs to canvas apps, where makers position controls freely on a blank canvas. It tempts because model-driven apps do include a modern app designer, but that designer configures sitemaps, forms and views rather than freeform pixel layout.
- ✓
Business rules to enforce data validation on forms.
Why this is correct
Business rules in model-driven apps run client-side and server-side against Dataverse tables, enforcing field validation, required values, and conditional logic without custom code. This satisfies the stem's validation requirement directly, unlike canvas-only features. They apply consistently across forms and views, making them a core model-driven capability.
- ✗
Built-in camera control to capture images.
Why it's wrong here
Camera capture is provided by the Camera control in canvas apps, not by model-driven apps, which render forms from Dataverse metadata. It tempts because mobile model-driven apps can attach images through file columns, but that uses the device file picker rather than a built-in camera control.
- ✓
Unified interface for tablet and mobile devices.
Why this is correct
Model-driven apps render through the Unified Interface, which presents the same sitemap, forms and views consistently across desktop, tablet and phone. This satisfies the cross-device capability the question requires, without separate app builds per form factor.
- ✓
Responsive design that adapts to screen size.
Why this is correct
Model-driven apps render through the Unified Interface, which is inherently responsive, reflowing forms, views and dashboards across desktop, tablet and mobile without separate layouts. This satisfies the stem's requirement for a genuine model-driven capability, since responsiveness comes from the platform's metadata-driven rendering rather than per-app customisation.
Go deeper
Related to this question
About these practice questions
This PL-900 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.