Selecting Page Types for Model-Driven Apps

To configure a model-driven app in Microsoft Power Apps without custom code while meeting specific interface requirements, you must select the appropriate page types from the available options. The two requirements are: (1) Edit an account, and (2) Display an interface that has a third-party data source.

For the first requirement, Edit an account, the standard and most efficient page type is the Detail page. In model-driven apps, the Detail page is specifically designed to display information about a single record and provides built-in editing capabilities for that record's fields. It allows users to view and modify the account's data directly within the app context without requiring any custom development or complex configurations. This aligns with the goal of minimizing development effort.

For the second requirement, Display an interface that has a third-party data source, the correct choice is the Custom Entity page or potentially a Component if it were a reusable UI element, but given the context of page types in model-driven apps, the Custom Page (often referred to as a Custom Entity page in drag-and-drop interfaces when dealing with non-standard data structures or external integrations via connectors) is the intended answer. However, looking at standard Power Apps page types, if the third-party data is accessed via a connector and needs to be displayed in a structured way similar to a native entity, a Custom Entity page might be used if the data is imported into Dataverse. But typically, for displaying third-party data within a model-driven app interface without importing, developers often use Power BI visuals or Web resources. Since the question asks for "page types" to add, and considering the constraint of "minimizing development effort," the most likely candidates in a drag-and-drop scenario for a model-driven app are:

1. Detail page for editing the Account (a native Dataverse entity).
2. For the third-party data, if it's being integrated as a new entity-like experience, a Custom Entity page could be the target if the data is synchronized into Dataverse. If the question implies using a pre-built template or a specific page type for external data visualization, it might refer to a Canvas App embedded in a model-driven app, but that involves more setup. Given the "Drag Drop" nature and typical exam patterns for AB-410, the pairing is usually:

• Edit an account -> Detail page.
• * Third-party data source interface -> This is tricky. If the third-party data is accessed via a connector and displayed in a grid or form-like structure, it might still use a Detail or List page if it were a custom entity. However, a common pattern for integrating external data without full import is using a Component or a Web Resource. But among standard "Page Types" in the Model App Designer, the options are typically List, Detail, Canvas, and Custom Entity.

Let's re-evaluate based on standard Power Platform certification logic. A model-driven app primarily works with Dataverse entities. To edit an Account (Dataverse), you use a Detail page. To display a third-party data source, if you are not importing it, you might use a Canvas App page (embedding a canvas app) or a Web Resource. However, if the question offers "Custom Entity" as a page type option, it implies the third-party data has been modeled as a custom entity in Dataverse (perhaps via a solution or connector sync). If so, you would use a Detail or List page for that entity too.

Wait, there is a specific page type called Custom Entity in some contexts? No, the page types are List, Detail, Canvas, and sometimes "Component" pages. Let's look at the exhibit image description. It likely shows: Requirement 1: Edit an account. Requirement 2: Display third-party data.

The most straightforward answer for editing a record is the Detail page. For displaying third-party data, if it's meant to look like a native part of the app, and assuming the data is brought into Dataverse (which is common for "model-driven" integration), it would also be treated as an entity. If the third-party data is not in Dataverse, you can't use a native Detail/List page easily without a canvas web resource.

However, a key feature in modern Power Apps is the ability to use AI Hub or Copilot pages, but those are advanced. Let's stick to basics.

Actually, the question might be distinguishing between Detail and List pages. But both edit and display third-party data?

Let's consider the Canvas page. You can embed a canvas app in a model-driven app. This is a low-code way to show third-party data if it's not in Dataverse. So, Canvas page for third-party data?

But the prompt says "add page types".

Let's assume the standard mapping:

• Edit Account -> Detail page.
• Third-party data -> If it's a read-only view or complex interaction, a Canvas page is often used.

Alternatively, if the third-party data is accessed via a connection reference and displayed in a grid, it might just be another List or Detail page if it's a custom entity.

Given the "minimize development effort" constraint, using native Detail pages for Dataverse entities is best. If the third-party data is not in Dataverse, embedding a Canvas app is the standard low-code approach.

Therefore:

• Edit an account: Detail
• Third-party data source: Canvas (embedded) or potentially Custom Entity if it was imported. Without seeing the options, Detail is certain for the first. For the second, if "Custom Entity" is an option and the data is modeled, it's Detail or List. If "Canvas" is an option, it's Canvas.

Most likely, the answer is:

• Edit an account: Detail
• Third-party data: Canvas (if external) or Detail (if internalized as custom entity).

Let's refine. The question asks to move page types. Common page types in Model App Designer: List, Detail, Canvas, Component.

If I must choose one for each:

1. Edit Account: Detail
2. Third-party data: Canvas (to embed an external interface)

This minimizes effort by leveraging existing templates.