Giving model-driven apps canvas strengths
The wrong answers pick a model-driven app for work that needs a canvas app, or credit model-driven apps with canvas strengths: connectors to SharePoint, Excel, Salesforce or SQL Server, Power Fx on control properties, and free placement of controls on a blank canvas. A canvas app starts from the user experience, gives the maker full control of layout and connects to many data sources at once. A model-driven app uses Dataverse as its only data platform, and its layout is largely determined by the components added.
See it in a sample questionCrediting canvas apps with automatic behaviour
The wrong answers credit canvas apps with behaviour that a model-driven app supplies on its own: a layout that adapts to each device, and navigation from a record to its related records. Canvas apps are responsive only if the maker designs them that way, and their relationship navigation is available only where it is designed with Power Fx. A model-driven app generates a responsive UI automatically and navigates through relationships automatically, provided the relationships exist.
See it in a sample questionConfusing public, personal and system views
The wrong answers offer a personal view or a system view where a public view is needed. A personal view is owned by one individual and is visible only to that person unless shared. System views, such as the Associated and Lookup views, are not shown in the view selector and cannot be used in a subgrid on a form. A public view is the general-purpose view that all app users reach through the view selector once it is made available, and it can feed a subgrid or a dashboard list.
See it in a sample questionStretching Co-Owner beyond use, edit and share
The wrong answers stretch the Co-Owner permission past use, edit and share. They give a Co-Owner the right to delete the app or change its owner, or count running the app as something only a Co-Owner can do. The User permission lets a person run the app only. Co-Owner adds editing and re-sharing on top of that. Deleting the app and changing its owner stay with the original owner.
See it in a sample questionMixing up canvas layout controls and settings
The wrong answers reach for a gallery, a plain Container, a component, Group, Split-screen or Sidebar when a canvas app needs child controls positioned automatically. A gallery repeats a template per record, children of a plain Container keep X and Y formulas, and Split-screen and Sidebar are screen layout templates. The Horizontal container and Vertical container place children and distribute space so no X or Y is set. Fill portions sets the ratio between sibling containers. Flexible width is an on or off toggle, and Align and Justify position children.
See it in a sample question