You are building a dashboard on a Raspberry Pi to display temperature sensor data in real-time. The sensor updates every second. Which data refresh strategy ensures the dashboard shows the latest data without overloading the device?
Think about updating only what changes frequently to save resources.
Streaming data updates only the changing value, which is efficient for real-time sensor data on limited hardware like Raspberry Pi.
Given a sensor data table with columns Timestamp and Temperature, which DAX measure correctly calculates the average temperature for the last 5 minutes?
AverageTempLast5Min = CALCULATE(AVERAGE(SensorData[Temperature]), FILTER(SensorData, SensorData[Timestamp] >= NOW() - TIME(0,5,0)))
Use CALCULATE with FILTER and NOW() minus 5 minutes.
Option C correctly uses CALCULATE with FILTER and NOW() - TIME(0,5,0) to filter last 5 minutes.
You want to show how temperature changes every second over the last 10 minutes on your dashboard. Which visualization type is best for this purpose?
Think about showing continuous data over time.
A line chart is best for showing continuous changes over time, like temperature every second.
Given this DAX measure to get the latest temperature reading:LatestTemp = MAXX(FILTER(SensorData, SensorData[Timestamp] = MAX(SensorData[Timestamp])), SensorData[Temperature])
What is the problem with this measure?
Consider how MAX inside FILTER behaves in row context.
Using MAX inside FILTER on the same column causes context issues, so FILTER returns no rows and the measure returns blank.
You have multiple sensors sending temperature and humidity data every second. You want to build a dashboard on Raspberry Pi that shows each sensor's latest readings and historical trends. Which data model design is best?
Think about efficient queries for latest and historical data separately.
Option A separates latest readings for quick access and archives historical data, optimizing performance on limited hardware.