Which of the following statements correctly describes a key difference between single-layer and multi-layer PCBs?
Think about how many circuit layers each PCB type has.
Single-layer PCBs have circuits on one side only. Multi-layer PCBs stack several circuit layers inside the board, allowing more complex connections.
You are designing a simple electronic device with low component count and low cost priority. Which PCB type is most suitable?
Consider cost and complexity for simple devices.
Single-layer PCBs are cheaper and simpler, making them ideal for low complexity and low cost devices.
Given a dataset with PCB designs and their layer counts, which DAX measure correctly calculates the average number of layers used per PCB type?
Measure = AVERAGEX(VALUES(PCBs[Type]), CALCULATE(AVERAGE(PCBs[LayerCount])))
Think about calculating average per group (PCB type).
AVERAGEX with VALUES groups by PCB type and calculates average layer count per type correctly.
You want to create a dashboard comparing the number of PCBs produced by layer count (single-layer vs multi-layer) over time. Which visualization type is best?
Consider comparing categories over time.
A stacked column chart clearly shows counts of different PCB layer types per month, making comparison easy.
In your BI model, you have a table 'PCBs' with columns 'PCB_ID', 'LayerCount', and 'ProductionDate'. You create a measure to count multi-layer PCBs as:
MultiLayerCount = COUNTROWS(FILTER(PCBs, PCBs[LayerCount] > 1))
However, the measure returns the total count of all PCBs regardless of layer count. What is the most likely cause?
Think about how filter context works in DAX measures.
FILTER alone does not change filter context in a measure without CALCULATE. Wrapping FILTER inside CALCULATE applies the filter correctly.
