Adding a Dashboard for Visual Insights in the App
Short answer
B Add a dashboard to the model-driven app so managers see aggregated visual insights alongside the list of rows.
Question
A company wants to provide managers with visual insights into business performance data. Managers require aggregated and visual representations of data directly within the app to be viewed in parallel with a list of rows. You need to configure the visual representation of data. What should you do?
Key Takeaways
The question tests knowledge that dashboards embed visual, aggregated representations within a model-driven app next to views; the trap is choosing Power BI or a custom page, which are separate surfaces rather than the native in-app parallel display.
For model-driven apps, dashboards provide aggregated charts and visual KPIs shown alongside a list of rows directly inside the app. This page explains why adding a dashboard (option B) satisfies the requirement for in-app visual insights viewed in parallel with row lists.
Common mistake: Choosing D (Create a Power BI semantic model) because Power BI produces visuals, but a semantic model is a data artifact in Power BI, not something rendered inside the app next to the row list; C (custom page) applies to canvas apps, not the row-list context described.
Expert Analysis
Why the Answer Is Correct
Option B is correct because a dashboard in a model-driven app is exactly the feature that displays aggregated charts, views, and KPI tiles side by side with a list of rows inside the app itself. The requirement's phrasing—"aggregated and visual representations... directly within the app" viewed "in parallel with a list of rows"—maps directly to dashboards, which can combine multiple views and charts in one screen. Dashboards are configured in the app designer and can be set as the app's default or main viewing surface for managers.Why the Other Options Are Wrong
Option A, app navigation, only controls which sitemap areas and menus appear; it renders no data visuals. Option C, a custom page, is a canvas-based element added to model-driven apps, but building one is unnecessary and does not natively present aggregated chart-and-row-list pairings the way dashboards do. Option D, a Power BI semantic model, is a backend data model in the Power BI service; it defines measures and relationships but produces no in-app display by itself, and Power BI visuals would require a separate embed or integration rather than a direct parallel view.Community Comment Notes
The single community comment supports the same conclusion, with exam_upskill selecting "B. Add a dashboard." No dissenting comments were posted, so the community and the feature-level analysis of model-driven app dashboards align here.Official Reference
Exam Strategy
When a question says visuals must appear directly within the app alongside a row list, think model-driven dashboard—not Power BI or custom pages. Check for keywords like "aggregated," "in parallel with a list of rows," and "directly within the app," which all point to dashboards.
Frequently Asked Questions
Why not create a Power BI semantic model for these in-app visuals?
A semantic model is a Power BI data artifact that defines measures and relationships; it renders nothing inside the app. Dashboards provide the actual in-app visual display next to rows.
When would a custom page be the right choice instead of a dashboard?
Choose a custom page when you need bespoke, canvas-style layouts or logic not covered by native dashboard components. For standard charts beside a row list, a dashboard is simpler and native.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded.
From public community threads 1
-
exam_upskill 👍 1 Answered BB. Add a dashboard.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.