Which statement best describes the primary purpose of the schematic in the PCB design workflow?
Think about what a schematic shows before the physical board is designed.
The schematic is a diagram that shows how components connect electrically. It does not show physical placement or manufacturing details.
Given a table 'Components' with columns 'ComponentID' and 'Quantity', which DAX measure correctly calculates the total number of components used in the PCB design?
Think about summing quantities versus counting unique IDs.
SUM adds all quantities to get the total count. COUNT counts rows, DISTINCTCOUNT counts unique IDs, and AVERAGE calculates the mean quantity.
You want to create a dashboard showing the number of PCB projects at each manufacturing stage (e.g., Fabrication, Assembly, Testing). Which visualization type is best to clearly communicate this status?
Consider which chart best shows parts of a whole at a single point in time.
A pie chart effectively shows the proportion of projects in each manufacturing stage at a glance.
In a BI model, you have a 'Designs' table with PCB schematic data and a 'Manufacturing' table with production details. What is the best relationship type between these tables to analyze manufacturing status per design?
Think about how many manufacturing records can exist per design.
One design can have multiple manufacturing records (e.g., batches), so one-to-many is appropriate.
Consider this DAX measure intended to calculate PCB yield percentage:PCB Yield = DIVIDE(SUM(Manufacturing[GoodUnits]), SUM(Manufacturing[TotalUnits])) * 100
Which issue will cause this measure to produce incorrect results?
Consider what happens when dividing by zero in DAX.
DIVIDE handles division by zero safely by returning blank or an alternate result, but if TotalUnits is zero, the measure returns blank, which might be interpreted as error or missing data.
