Building reports — quiz
8 questions covering this module. Scorecards, tables, charts, calculated fields and blends.
What makes a scorecard genuinely useful?
- Compact numbers
- A comparison date range showing the change
- A border
- A long title
Answer: A comparison date range showing the change — A number alone gives no sense of whether it is good or bad.
Which setting makes a dense table scannable?
- Wrap text
- Bars or heatmap on a metric column
- More rows per page
- A summary row
Answer: Bars or heatmap on a metric column — Visual encoding in cells beats reading digits.
A time series with a 30-value breakdown dimension gives:
- A clear chart
- 30 unreadable lines
- An error
- A pivot table
Answer: 30 unreadable lines — Filter to the top few or use a table.
Optional metrics allow the viewer to:
- Change the date
- Add metrics from a menu themselves
- Edit the report
- Export data
Answer: Add metrics from a menu themselves — It keeps the default view clean.
Where should a reusable calculation be created?
- In each chart
- At the data source level
- In Theme
- In a filter
Answer: At the data source level — Chart-level fields cannot be reused and tend to diverge.
SUM(Revenue)/SUM(Sessions) differs from SUM(Revenue/Sessions) because:
- It is faster
- The second averages per-row ratios, weighting rows equally
- The first fails on nulls
- They are identical
Answer: The second averages per-row ratios, weighting rows equally — Ratio of sums is the correct form for a rate.
Every metric in your blend is null. Likely cause?
- Wrong chart type
- The join keys do not match in format
- Too many sources
- Caching
Answer: The join keys do not match in format — Normalise the key with a calculated field before blending.
Join keys in a blend must be:
- Metrics
- Dimensions
- Dates only
- Calculated fields
Answer: Dimensions — Blends join on dimensions.