In PCB design, the via size is closely related to the drill diameter. Which statement correctly describes this relationship?
Think about how the plating process reduces the hole size.
The drill diameter is larger than the finished via size because plating adds copper thickness to the walls, reducing the final hole size.
You need to design a via with a finished size of 0.4 mm. The plating thickness is 0.025 mm on each side of the hole. What drill diameter should you specify?
Add twice the plating thickness to the finished via size.
Drill diameter = via size + 2 * plating thickness = 0.4 + 2*0.025 = 0.45 mm.
Given a dataset of vias with columns 'ViaSize' and 'DrillDiameter', which DAX measure correctly calculates the average drill diameter for each via size category?
Average Drill Diameter = AVERAGEX(VALUES(Vias[ViaSize]), CALCULATE(AVERAGE(Vias[DrillDiameter])))
Use AVERAGEX over distinct via sizes to get average per category.
Option B uses AVERAGEX over distinct ViaSize values and calculates average DrillDiameter per group, correctly computing average per category.
You want to create a dashboard that shows the distribution of via sizes and their corresponding drill diameters across multiple PCB layers. Which visualization type is best suited for this purpose?
Consider how to show relationship between two numeric variables and categories.
A scatter plot effectively shows the relationship between via size and drill diameter, with color differentiating PCB layers.
Consider this DAX measure intended to calculate the drill diameter for a given via size by adding plating thickness twice:
Drill Diameter = Vias[ViaSize] + 2 * Vias[PlatingThickness]
Why does this measure produce incorrect results when used in a report?
Think about how DAX handles row context in measures.
Measures cannot use direct column references without aggregation because they lack row context, leading to errors or incorrect results.
