An airline company wants to use Power Apps to manage its lost luggage desk. You need to determine whether the company should build a canvas app or a…

The decision between building a canvas app versus a model-driven app is primarily driven by the desired user experience (UX) and the underlying data structure. Canvas apps provide complete, pixel-perfect control over the user interface (UI) and layout, making them ideal when a specific design is required. They can also connect to a wide array of data sources. In contrast, model-driven apps are built upon the data model within Microsoft Dataverse. Their UI is largely generated from the data components, offering a consistent, responsive layout but less design freedom. Therefore, understanding the layout requirements and the intended data sources are the most critical questions to determine the appropriate app type.

A. Both canvas and model-driven apps are low-code platforms, designed to be accessible to users without traditional coding skills.

B. User access and security for both app types are managed through Microsoft Azure AD, so this does not help differentiate between them.

E. Both app types are designed to be responsive and are fully functional on mobile and tablet devices, so this is not a deciding factor.

1. Microsoft Learn. (n.d.). Overview of creating apps in Power Apps. Microsoft Docs. Retrieved from https://learn.microsoft.com/en-us/power-apps/maker/app-types-overview.

Section: Canvas apps: "If you want to design a highly customized user interface... your choice is a canvas app." This supports option C.

Section: Model-driven apps: "Model-driven app development is a component-focused approach... much of the layout is determined for you and largely designated by the components you add to the app." This contrasts with canvas apps

reinforcing option C. It also states these apps are built on Dataverse

supporting option D.

2. Microsoft Learn. (n.d.). What are model-driven apps in Power Apps?. Microsoft Docs. Retrieved from https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/model-driven-app-overview.

Section: Model-driven app design: "Unlike canvas app development where the designer has complete control over app layout

with model-driven apps much of the layout is determined for you..." This directly supports option C as a key differentiator.

Section: Advantages of the model-driven approach: This section emphasizes that the approach is centered on data modeling within Microsoft Dataverse

which directly supports option D.

3. Microsoft Learn. (n.d.). What are canvas apps in Power Apps?. Microsoft Docs. Retrieved from https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/getting-started.

Introduction: "Canvas apps give you the flexibility to arrange the user experience and interface the way you want it." This supports option C.

Section: Connect to data: "Your canvas app can connect to data in Microsoft data sources... or third-party data sources." This highlights the data source flexibility

making option D a critical question.