Why are centerlines important in technical drawings created with line and centerline tools?
Think about what symmetrical parts need to show clearly in a drawing.
Centerlines mark the center of circles and symmetrical features, helping to locate and align parts accurately.
Given a dataset of line segments with their lengths, which DAX measure correctly calculates the total length of all centerlines?
LinesTable = Table with columns: LineType ("Centerline" or "Regular"), Length (numeric)
Remember that CALCULATE with a direct filter condition requires special syntax.
SUMX with FILTER correctly sums lengths only for centerlines. Option D is invalid syntax because CALCULATE needs FILTER for row context filters.
You want to create a dashboard showing the count of different line types (centerline, construction line, regular line) used in multiple drawings. Which visualization is best?
Think about comparing counts across multiple drawings and categories.
A stacked bar chart clearly shows counts of each line type per drawing, making comparisons easy. Pie charts are less effective for multiple categories and groups.
What error does this DAX measure produce?CenterlineCount = COUNTROWS(FILTER(LinesTable, LinesTable[LineType] == "Centerline"))
Check the correct operator for equality in DAX filter expressions.
DAX uses a single '=' for equality, not '=='. Using '==' causes a syntax error.
You have a large dataset of drawings with line details. The report shows total centerline length per project. The current DAX measure is slow:
TotalCenterlineLength = SUMX(FILTER(LinesTable, LinesTable[LineType] = "Centerline"), LinesTable[Length])
Which optimization improves performance without changing the result?
CALCULATE with FILTER can be more efficient than SUMX with FILTER.
Using CALCULATE with FILTER leverages filter context better and improves performance. Option A adds storage cost and complexity. Option A removes filters incorrectly. Option A counts rows, not sums length.