In a model-driven app, the navigation structure is defined by the site map. To provide users with a "single screen" for data entry, you must first ensure the underlying table (e.g., Contact or a custom Customer table) is accessible. Modifying the site map to add a new subarea that points to this table will place a link in the app's left-hand navigation pane. This allows users to navigate to the table's view and then open a form (the data entry screen) to create new customer records. This is the standard method for exposing data entities to users within a model-driven app.

A. Create a canvas app.

This is incorrect because the requirement is to configure the existing model-driven app, not to build a separate, different type of app.

C. Create a Power Automate flow.

This is incorrect as Power Automate is used for automating business processes, not for creating or configuring user interface elements like data entry screens.

D. Use a Power Virtual Agents app.

This is incorrect because Power Virtual Agents is a service for creating chatbots, which is not relevant to providing a data entry form in a model-driven app.

---

1. Microsoft Learn. "Create a model-driven app site map." Microsoft Docs. This document explains that the site map is the primary way to define navigation in a model-driven app. It states

"The site map designer is used to set up the navigation for your model-driven app... Use it to drag and drop components into the designer

preview your work

and instantly publish it." This confirms the site map is the tool for making components like data entry screens accessible.

2. Microsoft Learn. "Add a page to your model-driven app." Microsoft Docs. This guide details the process of adding components to an app. In the section "Add a Dataverse table page to the navigation (site map)

" it explicitly states

"When you add a Dataverse table to your app's navigation

all the views

forms

charts

and dashboards for that table are available for users of your app." This directly supports that modifying the site map is the correct action.

3. Microsoft Learn. "Overview of the model-driven app designer." Microsoft Docs. This overview describes the core components of a model-driven app. Under the "Site map" section

it clarifies

"The site map specifies the navigation for your model-driven app

" reinforcing its role in controlling user access to different parts of the application

including data entry forms.