Domain 4 of the CompTIA Data+ (DA0-002) exam is all about presenting data in ways that drive decisions, and that’s where creating dashboards, reports, and interactive visuals comes in. Think of this as the difference between handing someone a printed summary of last month’s sales (a report), showing them a pre-set wall of real-time numbers (a dashboard), and giving them a clickable tool that lets them explore the data themselves (an interactive visual). For an IT professional, knowing which type to build—and how to build it correctly—is essential because stakeholders rarely want raw data; they want clarity, insight, and the ability to answer follow-up questions without waiting for a new spreadsheet.
Jump to a section
A simple way to picture Creating Dashboards, Reports, and Interactive Visuals
A restaurant menu is the central tool for communicating what a kitchen offers to a guest. It organises dishes into categories—starters, mains, desserts, specials—so a diner can quickly find what they want. The menu’s design matters: clear descriptions, prices, and sometimes photos help the guest decide. Behind the scenes, the kitchen uses a different document—a prep list—that tells the chef exactly how much of each ingredient to chop, marinate, and portion before service begins. The prep list is detailed, fixed, and only for internal use; it lists precise quantities and step-by-step instructions. Meanwhile, during dinner service, the head chef watches a live ticket screen on the pass. Each new order pops up in real time: table 4 wants the steak medium-rare, table 7 has a gluten allergy, table 9 needs their bill. That live ticket screen is interactive—the chef can touch it to mark an order as started, completed, or to flag an issue.
In IT terms, the guest menu is your report: a polished, static snapshot designed for an audience to read and understand. The prep list is your static dashboard: a pre-built view that shows key numbers at a glance, like daily sales totals or ingredient levels, but the reader doesn’t change what they see. The live ticket screen is your interactive dashboard or visual: it updates in real time, lets a user drill into details (tap a table to see that customer’s order history), filter by date, or change the view from bar chart to line graph. Knowing when to produce a neat menu (report), when to prepare a standard summary (dashboard), and when to build a live, clickable screen (interactive visual) is the skill this chapter teaches for the CompTIA Data+ exam.
Dashboards, reports, and interactive visuals are three distinct tools for communicating data, and the DA0-002 exam expects you to understand their differences, purposes, and best-use scenarios. Let’s define each one from the ground up.
A report is a static, formatted presentation of data that is typically generated on a schedule (daily, weekly, monthly) and then distributed. Think of a PDF or a printed page that shows a table of numbers, a chart, and maybe a summary statement. You cannot click on a report to see more details; what you see is what you get. Examples include a monthly sales summary sent to executives via email, a printed inventory snapshot handed out at a morning meeting, or a compliance report that shows whether security patches have been applied. Reports are excellent for documenting what happened at a specific point in time, for audits, and for stakeholders who only need a quick view without interactivity.
A dashboard is a visual display of the most important information needed to achieve one or more objectives, consolidated on a single screen so the information can be monitored at a glance. Dashboards can be static or interactive. A static dashboard updates periodically (say, every 15 minutes or every hour) but the viewer does not change the data view—they simply look at the dashboard as it refreshes. An interactive dashboard allows users to filter, drill down into details, change time ranges, or switch between chart types. Common elements on a dashboard include key performance indicators (KPIs)—those are the most important metrics, like total revenue, number of new customers, or system uptime percentage. Dashboards are used for monitoring real-time or near-real-time operations, such as a network operations centre watching server health or a marketing team tracking campaign performance.
An interactive visual is a more specific term for a chart, graph, or map that the user can manipulate. Think of a bar chart where you can click on a bar to see the data behind it, a line graph with a slider to adjust the time period, or a map where hovering over a region shows its sales numbers. Interactive visuals often live inside dashboards or as standalone elements in web applications. They are built using tools like Tableau, Power BI, or even JavaScript libraries (D3.js, Chart.js). The key feature is that the user is not just a passive reader—they can explore, filter, and highlight data to answer their own questions.
Why do these three exist separately? Because different audiences and different situations call for different levels of detail and interactivity. A C-suite executive may only want a static monthly report—they don’t have time to click around. A data analyst investigating a drop in sales needs an interactive dashboard where they can filter by region, product, and date. A technician monitoring server load needs a real-time dashboard that shows live CPU usage and alerts if something goes wrong. Using the wrong type for the audience leads to confusion or wasted effort: giving a highly interactive dashboard to someone who just wants a one-page summary frustrates them, while giving a static report to a data analyst who needs to explore is inefficient.
The DA0-002 exam tests your ability to choose the right presentation type based on a scenario. You might see a question like: “A marketing manager wants to see a summary of last quarter’s campaign performance, without needing to click or filter. Which should you create?” The correct answer is a report, because a report is static and meets the requirement of a one-time view. Another question: “A sales team needs to monitor their daily targets and be able to drill into each region to see individual rep performance. What should you build?” The answer is an interactive dashboard, because it combines monitoring with interactivity.
Building these visuals involves several technical steps: first, you connect to a data source (a database, a spreadsheet, a cloud service). Second, you clean and prepare the data—this means handling missing values, ensuring consistent date formats, and creating calculated columns if needed (for example, a profit column that subtracts cost from revenue). Third, you choose the appropriate chart type: bar charts for comparing categories, line charts for trends over time, pie charts for proportions (though these are often discouraged because they are hard to read), scatter plots for relationships, and maps for geographical data. Fourth, you design the layout: reports are often paginated with headers and footers, dashboards are designed to fit one screen, and interactive visuals need clear tooltips and filters. Fifth, you publish or share the output—this could be printing a PDF, embedding a dashboard in a web portal, or sending a link to a live Power BI report.
Common pitfalls include overcomplicating the visual (too many colours, chart junk), choosing the wrong chart type (using a pie chart for more than 4 categories), violating accessibility guidelines (using colour alone to convey meaning), and failing to match the level of interactivity to the audience’s technical comfort. The exam will test your ability to spot these mistakes in scenarios.
For complete beginners, remember the acronym “DSI” to keep the categories straight: D is for Dashboard (monitoring, real-time, often interactive), S is for Static Report (fixed, printed, for record-keeping), I is for Interactive Visual (clickable charts that let users explore). The central idea is always: know your audience and the question they need to answer.
Gather Requirements from the Stakeholder
Interview the person who will use the output. Ask: what question are you trying to answer? How often will you look at this? Do you need to interact (click, filter) or just read? This determines whether you build a report, dashboard, or interactive visual.
Connect to and Prepare the Data Source
Connect your tool (like Power BI, Tableau, or Excel) to the database, spreadsheet, or API that holds the data. Clean the data: remove duplicates, handle missing values, and ensure dates are in a consistent format. This step is critical because bad data produces bad visuals.
Choose and Create the Appropriate Visualisations
Select chart types that match the data and the stakeholder’s need. For a report, you might use tables and bar charts. For a dashboard, you place KPIs, line charts, and maps on one screen. For an interactive visual, you add slicers, drill-down, and cross-filtering between charts.
Design the Layout and Apply Best Practises
Arrange elements so the most important information is at the top-left (where the eye goes first). Use a consistent colour scheme. Add titles, axis labels, and tooltips. Ensure that any filters (slicers) are clearly labelled. For reports, use headers, footers, and page numbers. For dashboards, keep everything on one screen without scrolling.
Publish, Share, and Set Up a Refresh Schedule
Export reports to PDF or print them. Publish dashboards to a server or cloud service (like Power BI Service, Tableau Server) so others can view them via a link. Set a refresh schedule: daily for most business dashboards, every few minutes for real-time monitoring, and monthly for reports. Also configure security—who can see what (row-level security).
Imagine you work as a junior data analyst at a medium-sized online retail company called “GreenCart”. GreenCart sells eco-friendly products across the UK and Ireland. The CEO wants a better handle on business performance without constantly asking the IT team for custom reports. Your manager asks you to create three different outputs: a monthly executive report, a real-time sales dashboard for the sales director, and an interactive visual for the marketing team to explore customer demographics.
Step 1: You start with requirements gathering. You interview the CEO, who says: “I need a one-page PDF every month that shows total revenue, gross profit, top 5 products, and a comparison to the same month last year. I don’t need to click anything; I read this on my tablet while commuting.” That’s a classic report: static, formatted, delivered on a schedule. You decide to use Microsoft Power BI to create a paginated report (sometimes called “Report Builder” in the Power BI ecosystem) because Power BI is the tool your company uses, and paginated reports output to PDF. You set it to run on the 1st of each month, pulling data from the company’s SQL Server database.
Step 2: The sales director asks for a dashboard that shows daily sales by region, with a live counter for orders placed today, and the ability to click on a region to see individual store performance. This is an interactive dashboard. You build it in Power BI Desktop. You set up a real-time data refresh using DirectQuery (a connection mode that queries the database live rather than importing all data) so the numbers update every 5 minutes. You place three KPIs at the top: “Orders Today”, “Revenue Today”, and “Returns Today”. Below that, you add a map of the UK and Ireland colour-coded by sales volume. When the sales director clicks on “Manchester” on the map, the chart below changes to show Manchester’s top-selling products. You also add slicers—these are filter panels that let the user narrow the view to a specific date range or product category. The whole dashboard fits one screen without scrolling, which is a best practice.
Step 3: The marketing team wants to play with customer demographics data. They are not data-savvy, but they want to understand which age groups and locations are buying which products, so they can plan campaigns. You create an interactive visual that is essentially a set of linked charts. You build a scatter plot of customer age versus average order value, a bar chart of product categories by region, and a table that shows individual customer segments. All three are connected so that when a user clicks on a bar in the product category chart, the other charts automatically filter to show only data from that category. This is called cross-filtering or drill-through. You publish this as a “dashboard” in Power BI’s service (the online sharing platform), but technically it is a set of interactive visuals on one page.
Throughout this process, you also consider data security. The sales director should see all regions, but the regional managers should only see their own region. You implement row-level security (RLS)—a feature that filters data based on the user’s identity. So when a regional manager logs in to view the dashboard, Power BI automatically hides any data that does not belong to their region.
Finally, you document everything: the data sources, the refresh schedule, the RLS rules, and the definitions of each KPI (e.g., “what counts as a return?”). This documentation is crucial because if someone changes a business rule in six months, they need to understand why the dashboard was built that way.
In real practice, almost every IT professional who works with data will create some combination of reports, dashboards, and interactive visuals. The key lessons you want to remember from this scenario: start with requirements, choose the right format for the audience, use the tool’s interactive features (slicers, cross-filtering, drill-through) for exploratory needs, keep static outputs clean and simple, and always secure data by user role.
The DA0-002 exam explicitly tests objective 4.2 with questions that require you to distinguish between dashboards, reports, and interactive visuals, and to know when each is appropriate. Here is exactly what you need to memorise and watch out for.
First, the exam will present a short scenario (a sentence or two) and ask: “Which type of visualisation should the data analyst create?” The trap is often that the scenario includes clues that seem to point to a dashboard, but actually the requirement is for a static report. For example, a scenario that says “monthly” and “printed” should scream “report”, not dashboard. Another trap: “real-time” and “monitoring” always point to a dashboard (static or interactive). “Interactive” and “explore” point to an interactive visual or interactive dashboard—the exam may treat these as overlapping.
Second, the exam tests knowledge of chart types and best practices. You must know:
Bar charts are for comparing discrete categories (e.g., sales by product).
Line charts are for trends over continuous time (e.g., revenue by month).
Pie charts are for showing parts of a whole, but only with 2-4 categories; more than that becomes unreadable. The exam often tests that pie charts are a poor choice for many categories.
Scatter plots show correlation between two numerical variables.
Heat maps show density or intensity across two dimensions.
Tables are for precise values, but not for quick pattern recognition.
Third, the exam covers design principles:
The “ink-to-data ratio” means eliminate unnecessary visual elements (gridlines, excessive colours, 3D effects) that don’t carry data.
Use colour purposefully, not decoration. The exam will give a scenario with a dashboard that uses red and green to indicate whether a KPI is on target (green) or below target (red). That is a good use of colour. A dashboard that uses rainbow colours for no reason is a violation of best practice.
Accessibility: do not rely solely on colour; use patterns or labels as well, because some viewers are colour-blind.
Fourth, the exam tests the concept of data aggregation. If you are creating a dashboard or report, you often need to aggregate data—sum it, average it, count it—to see the big picture. The exam will ask: “A manager wants to see total sales for each region. In this dashboard, the data source contains individual transactions. What must the analyst do?” The answer is to aggregate the data (sum sales by region). The trap is that a beginner might think they can just display the raw transactions, but that’s too detailed for a dashboard.
Fifth, the exam includes questions about filters and interactivity:
Slicers are visual filter controls that let users select a value (e.g., a date range from a calendar).
Drill-down allows the user to click on a category to see its subcategories (e.g., click a region to see its cities).
Drill-through takes the user to a different page that shows detailed data about the clicked item.
Tooltips are pop-up boxes that show extra data when you hover over a data point.
The exam will ask you to identify which interactivity feature is used in a described scenario. For instance: “A user clicks on the ‘North’ bar on a bar chart, and the dashboard navigates to a new page showing individual stores in the North. This is an example of … drill-through.”
Sixth, the exam tests knowledge of publishing and sharing:
Reports can be exported to PDF, printed, or emailed.
Dashboards can be shared via a secure link, embedded in a web page, or displayed on a TV in a operations centre.
Data refresh is critical: a dashboard showing real-time sales is useless if it only refreshes once a week. The exam will ask about refresh schedules appropriate for different scenarios (e.g., monthly report updates once a month; real-time dashboard updates every few minutes).
Finally, be ready for questions that ask you to choose the best tool for the job based on the organisation’s environment. The exam does not favour one specific tool (like Tableau vs Power BI), but it does expect you to know general capabilities: a spreadsheet tool (Excel, Google Sheets) can be used for simple charts and static reports, a dedicated business intelligence tool (Power BI, Tableau) is better for dashboards and interactivity, and programming libraries (Python’s Matplotlib, JavaScript’s D3.js) are for custom interactive visuals embedded in web apps. The correct answer will often be broad: “a business intelligence tool like Power BI or Tableau” rather than a specific product name.
A report is a static, paginated document designed for distribution and printing, while a dashboard is a single-screen visual display for monitoring.
Interactive visuals (like clickable charts with sliders or drill-through) let users explore data, but they should only be used when the audience needs that capability.
The choice between a dashboard, report, or interactive visual depends on the audience’s need for interactivity, the update frequency required, and the device where it will be viewed.
Chart type matters: use bar charts for comparing categories, line charts for trends, scatter plots for correlations, and pie charts only for parts-of-a-whole with 2-4 segments.
Always apply the principle of high ink-to-data ratio: remove decorations (gridlines, 3D effects, excessive colours) that do not represent data.
Slicers, drill-down, drill-through, and tooltips are specific interactive features tested on the exam—know their definitions and scenarios.
Data security such as row-level security must be implemented in dashboards that are shared with users who should only see their own subset of data.
The exam never tests a specific tool (e.g., Power BI vs Tableau), but it does test general capabilities like supporting cross-filtering or scheduling data refresh.
These come up on the exam all the time. Here's how to tell them apart.
Dashboard
Single-screen view designed for monitoring at a glance
Often updated in real-time or on a frequent schedule (minutes/hours)
Includes interactive elements like slicers, drill-down, and KPIs
Report
Multi-page or paginated document for detailed reading
Usually static and generated on a schedule (weekly/monthly)
Minimal interactivity; designed for printing or PDF distribution
Static Dashboard
Contains pre-set visuals that the user cannot modify or filter
Refreshes data on a schedule but the view does not change per user action
Suitable for passive monitoring (e.g., a TV in a lobby)
Interactive Dashboard
Allows users to apply filters, drill-down, and change time ranges
Responds to user input in real time (e.g., clicking a region shows its cities)
Suitable for analysts who need to explore data
Pie Chart
Shows parts of a whole with 2-4 categories
Hard to compare individual slices accurately
Poor choice for comparing many categories or values that sum to more than 100%
Bar Chart
Compares values across discrete categories
Easy to compare lengths accurately
Ideal for many categories and for showing exact differences
Drill-Down
Expands a single visual to show more detailed data within the same chart
User clicks on a category (e.g., a year) and the chart expands to show months
Stays on the same page/dashboard
Drill-Through
Navigates the user to a different page that shows detailed data about the clicked item
User clicks on a data point (e.g., a region) and is taken to a new report page
Leaves the current dashboard page
Mistake
A dashboard and a report are the same thing, just with different names.
Correct
A report is a static, formatted document (often paginated) used for distribution and record-keeping, while a dashboard is a visual display (often single-screen) used for monitoring at a glance. They serve different audiences and use cases.
In everyday language, people use the words interchangeably. The CompTIA exam expects a technical distinction based on purpose and interactivity.
Mistake
More colours and fancy 3D effects make a chart more professional and clear.
Correct
Unnecessary colours, 3D effects, and decorative elements reduce the clarity of data, violating the principle of high ink-to-data ratio. Simple, clean charts are best.
Beginners think visual flair equals professionalism, but data visualisation best practise values clarity and honesty above decoration. The exam rewards simplicity.
Mistake
Pie charts are always a bad choice and should never be used.
Correct
Pie charts can be effective for showing parts of a whole with 2-4 categories. The problem is they are overused for many categories or for comparing values that are not parts of a whole.
The blanket rule ‘never use pie charts’ is common in online advice, but the exam acknowledges that pie charts are acceptable in limited, appropriate scenarios.
Mistake
Interactive visuals are always better than static reports because users can explore more.
Correct
Interactive visuals are better for exploration, but they are not always better for a fixed audience that needs a quick, unchanging summary. Giving an interactive dashboard to someone who just wants a printed PDF can be confusing and unnecessary.
Technologists often prefer interactivity, but the exam tests that you match the output to the user’s need, not to your preference.
Mistake
Once you build a dashboard, the data is always up to date automatically without any action.
Correct
Dashboards rely on a data refresh scheduled in the tool (e.g., every 15 minutes, daily). If the data source does not refresh, the dashboard shows stale data. Some live connections exist but require appropriate infrastructure.
Beginners think a dashboard is ‘magically’ live; they don’t understand the underlying data refresh mechanism. The exam tests this practical knowledge.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
In Power BI, a report is a multi-page interactive document built from a dataset, while a dashboard is a single-page canvas that displays visualisations (tiles) pinned from one or more reports. However, the DA0-002 exam expects the general definition: a report is static and paginated; a dashboard is for monitoring.
No. The exam tests general concepts, not specific tools. You need to understand what features a business intelligence tool should have (e.g., filtering, drill-through, scheduling refresh), not how to click specific buttons.
Use a bar chart when you are comparing separate categories (apples vs oranges). Use a line chart when your data has a time series (sales by month) because lines show trends well.
A KPI (Key Performance Indicator) is a single number that tracks progress toward a goal, like ‘total revenue’ or ‘customer satisfaction score’. It’s often shown large at the top of a dashboard with a conditional colour (green if on target, red if not).
Yes, Excel supports slicers, timelines, and limited chaining of charts (by using PivotCharts and slicers together). It is less powerful than dedicated tools like Power BI but suitable for simple interactive visuals.
Row-level security (RLS) filters data so that different users see only the rows they are authorised to see. For example, a regional manager sees only their region’s sales. It is important for compliance and data privacy.
You've finished Creating Dashboards, Reports, and Interactive Visuals. Continue through the DA0-002 study guide to build a complete picture of the exam.
Done with this chapter?