Analytics-DA-201 - Connect to and Transform Data (24% of the exam) - Section 1.4
Change default field properties, rename columns, convert between discrete and continuous and between dimension and measure, and create aliases.
Practice question for this objective
lock_openFree sampleConnect to and Transform Dataeasy
A [Shipping Priority] dimension holds the members Low, Medium, High and Critical. Whenever the analyst drags this field onto Rows in any new worksheet, the members appear alphabetically as Critical, High, Low, Medium, but the team always wants them to read Low, Medium, High, Critical without re-sorting each sheet. Which action makes that order the field's standing behaviour across new views?
AApply a manual sort on the axis in one worksheet, which carries that order to every other worksheet using the field.
BSet a Default Sort on the field as a default property, defining the manual order Low, Medium, High, Critical so it applies wherever the field is used.check_circle Correct
CConvert the field from a dimension to a measure so the members order themselves by value rather than alphabetically.
DCreate aliases on the members so their display names begin with numbers that force the desired sequence.
A default sort set in a field's Default Properties imposes a chosen member order consistently across every worksheet that uses the field. Worksheet-level sorts are local, but a default sort is a property of the field, so defining the manual order Low to Critical once makes that sequence appear automatically in new views.
Why A is wrong: A sort applied on an axis is local to that worksheet and does not propagate to other sheets that use the same field.
Why B is correct: Correct: a default sort stored in the field's Default Properties imposes the chosen member order across every view that uses the field.
Why C is wrong: Turning the field into a measure would aggregate it and remove the discrete members entirely, so there would be no Low to Critical headers to order.
Why D is wrong: Aliases change only the displayed text; renaming members would not impose a custom order and would also change how the categories read.
Answers that look right on this material and are not. Each one is a distractor from a different question in the Analytics-DA-201 bank for this domain.
A discrete field can only ever hold text values, whereas a continuous field can only ever hold numeric values.
errorWhy it is wrong: This is tempting because text is usually discrete and numbers are often continuous, but discreteness is about how values are laid out, not the data type; a date or a number can be made discrete.
Tableau keeps the smooth gradient but reverses its direction so high profit reads orange instead of green.
errorWhy it is wrong: Switching to discrete does not merely reverse a gradient; it changes the colour encoding from a continuous range to separate categorical swatches.
Tableau converts Order Date into a measure and aggregates it as a sum.
errorWhy it is wrong: Discrete versus continuous controls how a field is laid out, not whether it is a measure, so the change does not aggregate the dates as a sum.