Create model-driven apps
48 practice questions under this official exam objective (AB-410), each with the answer key, an option-by-option explanation and instant feedback.
Questions under this objective
48 total · page 1 of 3App Access Checker Input for Model-Driven App Access
The Power Platform App access checker diagnoses why an individual user cannot open a model-driven app by taking a single user identity as its input. F
Reusable form UI and client-side code in model-driven apps
This AB-410 case study tests extensibility choices for model-driven apps: use a JavaScript web resource to avoid server-side code and a Power Apps com
Model-driven app AI: Copilot Studio vs App assistant agent
This AB-410 scenario tests in-app AI assistance for a model-driven support-case app. The correct components are B (Copilot Studio agent) and D (App as
Restricting Model-Driven App View Access by Security Role
Learn how to secure sensitive columns in a model-driven app by restricting public view access to specific security roles like managers.
Model-Driven App Business Rules for Country and Passport Fields
In a model-driven app, both conditional value population and conditional field visibility on a form can be handled with a Business rule on the custome
Do Business Rules Meet Dynamic Client-Side Form Control?
In this AB-410 scenario, a business rule that shows inline error messages does dynamically enforce client-side behavior on a model-driven app form in
Configuring access to public and personal views
This case study tests Dataverse view access control: restrict the public Senior Technicians view by assigning security roles in the app designer, and
Which Form Components Support Inline Editing and Related Data?
This AB-410 drag-and-drop item tests model-driven app form components, matching each account manager requirement to the right component. The page esta
Which Table Ownership Ties Records to a Business Unit?
This Dataverse question tests table ownership types and how they affect business unit association and security role configuration. It establishes that
How Do You Validate the Dog Pickup Date in the Model-Driven App?
This Contoso Suites hotspot asks which mechanism and which expression guarantee a dog is not picked up sooner than two days after spaying or neutering
Care Staff Security Role Privileges in Contoso Model-Driven App
For Contoso Suites' care staff security role, the Contact table needs Organization-level Read only (view adopters without editing), the Dog table need
Adding Dog Weight to the Resident Form in a Model-Driven App
In the Contoso Suites case study, care staff must update a dog's weight from the Resident record even though Weight lives on the Dog table. The page e
How Should ADatum Restrict Service Request Data Access?
This ADatum case study hotspot asks which Dataverse security changes remove excess access to client data on Service Request and Qualification records.
Moving Dataverse Table, Data, and Sitemap Changes Between Environments
This AB-410 drag-and-drop item tests Microsoft Dataverse application lifecycle management (ALM): schema customizations such as a new table and sitemap
Impact of Adding a Stage to an Existing Business Process Flow
This AB-410 hotspot tests how Microsoft Power Platform business process flow (BPF) versioning affects Account records after a new stage is inserted at
How do you grant and troubleshoot model-driven app access?
This hotspot asks how to let users open a model-driven app deployed to multiple departments and how to diagnose access failures. The page establishes
Does updating a mailbox name change a user's sign-in name?
Changing the name on a user's mailbox record in Dynamics 365 Email Configuration only edits mailbox settings and leaves the sign-in name untouched. Th
Can Power Automate Cloud Flows Control Model-Driven Form Behavior in Real Time?
Model-driven apps require client-side logic — form JavaScript event handlers or business rules — to change component behavior instantly as users inter
What Business Rule Scope Applies in Canvas vs Model-Driven Apps?
Dataverse business-rule scope controls whether logic runs against the table or a model-driven form. This question establishes Entity/Table scope for t
Which three approaches enforce validation across multiple Power Platform forms?
Uniform validation across multiple Power Platform forms is best implemented with table-level business rules, reusable Power Fx functions, and client s