A retail operations team wants to build a model-driven app over the standard Account table in Microsoft Dataverse, and they want the app and its components packaged so they can later move it to a separate production environment. Inside which container should the maker create the app to keep the tables, forms, and views portable across environments?
- AA solution, then add the Account table and create the model-driven app inside it Correct
- BA Dataverse table, then promote the table directly into a deployable model-driven app
- CAn environment, then build the app at the environment root so it travels with the database
- DA dashboard, then attach the Account table and publish the app from the dashboard
Why A is correct: Correct. The grounding recommends creating a model-driven app from a solution, because a solution is a package that can contain Dataverse tables, forms, views, apps, flows, and other components, so you can easily move it to other environments or preserve a copy in source control.
Why B is wrong: A Dataverse table holds records and is added to the app, but a table is not the package that bundles forms, views, and the app for portability across environments; the solution is the container for that.
Why C is wrong: An environment is a space that stores data and apps and holds one Dataverse database, but it is the boundary you move components between, not the portable package you carry; solutions are what move between environments.
Why D is wrong: A dashboard surfaces lists and charts to users at runtime; it is an app component, not a packaging container that bundles tables and views for export to another environment.