9.9.1: Review Questions
- Page ID
- 58329
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\ket}[1]{\left| #1 \right>}\)
\(\newcommand{\bra}[1]{\left< #1 \right|}\)
\(\newcommand{\braket}[2]{\left< #1 \vphantom{#2} \right| \left. #2 \vphantom{#1} \right>}\)
\(\newcommand{\braopket}[3]{\left< #1 \vphantom{#2}\vphantom{#3} \right| #2 \vphantom{#1}\vphantom{#3} \left| #3 \vphantom{#1}\vphantom{#2} \right>}\)
\(\newcommand{\qmvec}[1]{\mathbf{\vec{#1}}}\)
\(\newcommand{\op}[1]{\hat{\mathbf{#1}}}\)
\(\newcommand{\expect}[1]{\langle #1 \rangle}\)
\(\newcommand{\dfn}[1]{\emph{\textbf{#1}}}\)
Review Questions
Multiple Choice
-
A hiring funnel showing 1,000 applicants narrowing to 50 interviews, then 10 offers, then 3 hires is best visualized with:
-
a) Pie chart b) Sankey diagram c) Scatter plot d) Radar chart
-
-
Stephen Few created the bullet chart as an improvement over:
-
a) Bar charts b) Line charts c) Dashboard gauges and meters d) Pie charts
-
-
According to Shneiderman's mantra, the correct sequence for interactive data exploration is:
-
a) Details first, then overview b) Overview first, zoom and filter, details on demand c) Filter first, then zoom, then overview d) Details on demand, then filter
-
Short Answer
-
Compare treemaps and bar charts for showing budget allocation across 8 departments. When is each preferable?
-
Explain three principles of effective dashboard design. For each, describe what happens when the principle is violated.
-
What is the difference between a data story for a technical audience (data team) and an executive audience (C-suite)? How would you adapt the same finding for each?
-
Only 10-15% of users interact with interactive dashboard features. How should this statistic influence your dashboard design decisions?
True/False
-
True or False: Radar charts are effective for comparing 20+ variables across multiple entities.
-
True or False: A Sankey diagram's band width is proportional to the quantity flowing between stages.
-
True or False: Real-time dashboards should always refresh every second to be most useful.
Answer Key:
1-b, 2-c, 3-b, 4. Bar chart: better for precise value comparison (aligned baseline). Treemap: better for showing hierarchy and part-to-whole within limited space (e.g., departments with sub-teams). Use bar chart when precision matters; treemap when hierarchical overview and space efficiency matter. 5. (1) Visual hierarchy: violated = all elements same size/weight, user can't find key info. (2) Minimize cognitive load: violated = cluttered, too many colors/charts, user overwhelmed. (3) Responsive design: violated = dashboard unreadable on mobile or small screens. 6. Technical: more detail, show methodology, include uncertainty/caveats, can use complex charts. Executive: headline finding first, simple charts, focus on business impact and recommended action, keep to 1-2 key insights. 7. Design the default static view to tell the complete story. Add interactivity as enhancement, not requirement. Label interactive elements clearly. Don't hide critical insights behind clicks. 8. False (5-8 variables max recommended), 9. True, 10. False (refresh rate should match the data's nature and user needs — financial trading needs seconds, monthly sales dashboard needs hourly/daily).


