Manufacturing file review in PCB Design - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the purpose of a drill file in manufacturing

Which of the following best describes the main purpose of a drill file in a PCB manufacturing file set?

A It provides the bill of materials for component placement.

B It contains the copper layer artwork for signal routing.

C It specifies the locations and sizes of holes to be drilled on the PCB.

D It defines the solder mask openings on the PCB surface.

💡 Hint

Think about what holes are needed for components and vias.

The drill file lists all hole locations and sizes needed for vias and component leads. It does not contain copper or mask information.

❓ dax_lod_result

intermediate

Calculating total PCB layers using DAX

Given a table 'PCB_Layers' with columns 'LayerName' and 'IsActive' (TRUE/FALSE), which DAX measure correctly counts the number of active layers?

A Active Layers = CALCULATE(COUNTROWS(PCB_Layers), PCB_Layers[IsActive] = TRUE)

B Active Layers = COUNT(PCB_Layers[IsActive])

C Active Layers = SUM(PCB_Layers[IsActive])

D Active Layers = COUNTROWS(FILTER(PCB_Layers, PCB_Layers[IsActive] = TRUE()))

💡 Hint

Filter the table to only active layers before counting rows.

Option D filters the table to only rows where IsActive is TRUE, then counts those rows. Option D counts all values, including FALSE. Option D sums booleans which is invalid. Option D has incorrect filter syntax.

❓ visualization

advanced

Best visualization for layer thickness distribution

You have manufacturing data showing thickness measurements for each PCB layer over multiple batches. Which visualization best helps identify layers with inconsistent thickness?

A A box plot per layer showing thickness distribution across batches.

B A stacked bar chart showing total thickness per batch.

C A line chart showing average thickness over time for all layers combined.

D A pie chart showing proportion of layers by thickness category.

💡 Hint

Look for a chart that shows spread and outliers per category.

A box plot per layer clearly shows the spread, median, and outliers of thickness measurements, helping identify inconsistency. Other charts do not show distribution well.

🔧 Formula Fix

advanced

Identifying error in SQL query for manufacturing defect counts

Given this SQL query to count defects per PCB batch: SELECT BatchID, COUNT(DefectID) AS DefectCount FROM Defects WHERE DefectType = 'Critical' GROUP BY BatchID HAVING DefectCount > 5; What error will this query produce?

A Syntax error because HAVING cannot use alias DefectCount.

B No error; query runs correctly and returns batches with more than 5 critical defects.

C Runtime error due to missing GROUP BY column DefectType.

D Logical error because WHERE cannot filter DefectType before aggregation.

💡 Hint

Check if aliases can be used in HAVING clauses in SQL.

In many SQL dialects, the HAVING clause cannot reference column aliases defined in the SELECT clause. The alias DefectCount is not recognized in HAVING, causing a syntax error.

🎯 Scenario

expert

Optimizing manufacturing file review dashboard performance

You have a Power BI dashboard showing manufacturing file review metrics with multiple slicers and detailed tables. Users report slow loading times. Which approach will most effectively improve performance without losing key insights?

A Increase the number of visuals on the page to distribute load.

B Use aggregations and pre-calculated summary tables to reduce data volume.

C Remove all slicers and replace tables with static images.

D Disable data refresh to avoid loading delays.

💡 Hint

Think about reducing the amount of data processed at runtime.

Using aggregations and summary tables reduces the data Power BI processes, improving performance while keeping interactive insights. Removing slicers or disabling refresh reduces functionality. Adding visuals increases load.

Practice

1. What is the main purpose of a manufacturing file review in PCB design?

easy

A. To prevent costly errors during PCB production

B. To design new PCB layouts

C. To write software for PCB testing

D. To order components for assembly

Solution

1. Step 1: Understand the role of manufacturing file review

   Manufacturing file review checks files like Gerber and drill files before production.

2. Step 2: Identify the main goal

   The goal is to catch errors early to avoid costly mistakes in production.

3. Final Answer:

   To prevent costly errors during PCB production -> Option A

4. Quick Check:

   Manufacturing file review = prevent errors [OK]

Hint: Focus on error prevention in production files [OK]

Common Mistakes:

• Confusing design with review process
• Thinking review is for ordering parts
• Mixing software testing with file review

2. Which file type is NOT typically checked during a PCB manufacturing file review?

easy

A. Source code files

B. Drill files

C. Component placement files

D. Gerber files

Solution

1. Step 1: List common files reviewed

   Gerber, drill, and component placement files are standard in manufacturing review.

2. Step 2: Identify the odd file out

   Source code files relate to software, not PCB manufacturing files.

3. Final Answer:

   Source code files -> Option A

4. Quick Check:

   Manufacturing review excludes software files [OK]

Hint: Remember manufacturing files are physical layout files [OK]

Common Mistakes:

• Including software files in manufacturing review
• Confusing component files with source code
• Assuming all project files are reviewed

3. Given a BI dashboard showing counts of errors found in Gerber, drill, and component files, which visualization best helps identify the file type with most errors?

medium

A. Table listing file names only

B. Line chart showing error counts over time

C. Scatter plot of file sizes vs error counts

D. Pie chart showing error counts by file type

Solution

1. Step 1: Understand the goal of visualization

   The goal is to identify which file type has the most errors.

2. Step 2: Choose visualization type

   A pie chart clearly shows proportions of errors by file type, making comparison easy.

3. Final Answer:

   Pie chart showing error counts by file type -> Option D

4. Quick Check:

   Pie chart = compare parts of whole [OK]

Hint: Use pie charts to compare parts of a whole quickly [OK]

Common Mistakes:

• Using line charts for categorical comparison
• Choosing tables without summary
• Scatter plots confuse error focus

4. A BI report shows zero errors in drill files, but the drill file was not uploaded. What is the likely issue?

medium

A. The report is correctly showing zero errors

B. The drill file was missing, causing no data to check

C. The drill file has no errors by default

D. The BI tool automatically fixes missing files

Solution

1. Step 1: Analyze the zero error count

   Zero errors can mean no errors or no data to check.

2. Step 2: Consider missing file impact

   If the drill file was not uploaded, the BI tool has no data to analyze, so it shows zero errors incorrectly.

3. Final Answer:

   The drill file was missing, causing no data to check -> Option B

4. Quick Check:

   Missing file = no data, not zero errors [OK]

Hint: Check if files are uploaded before trusting zero errors [OK]

Common Mistakes:

• Assuming zero means no errors
• Believing BI tools fix missing data automatically
• Ignoring file upload status

5. You want to create a BI report that highlights PCB manufacturing errors by file type and severity. Which approach best combines these two aspects for clear decision-making?

hard

A. Display a line chart of errors over time without file type distinction

B. List all errors in a long table sorted by file name

C. Use a stacked bar chart with file types on X-axis and error counts stacked by severity

D. Show a pie chart of total errors without severity details

Solution

1. Step 1: Identify key data dimensions

   We need to show errors by file type and severity together.

2. Step 2: Select visualization that combines categories and subcategories

   A stacked bar chart groups errors by file type and stacks severity levels, making it easy to compare both.

3. Final Answer:

   Use a stacked bar chart with file types on X-axis and error counts stacked by severity -> Option C

4. Quick Check:

   Stacked bar = compare categories + subcategories [OK]

Hint: Stacked bars show parts of categories clearly [OK]

Common Mistakes:

• Using tables that are hard to scan
• Ignoring severity in summary charts
• Choosing charts that miss key comparisons