Option D uses IF to check if the value is 'Pending' and replaces it with 'Not Started'. Other values remain unchanged.
Option D also works because the last argument in SWITCH acts as the default for unmatched cases, but IF is more straightforward for a single replacement.
Option D tries to replace characters by position, which is not suitable here.
Option D replaces substring occurrences, which could cause unintended replacements if 'Pending' appears inside other words.
Option C is correct because it uses the new column with replaced values, so the chart reflects the updated categories.
Option C shows original values, so 'Pending' will appear instead of 'Not Started'.
Option C filters only 'Pending', ignoring other statuses.
Option C requires manual label changes, which is error-prone and not dynamic.
Option A uses SWITCH with multiple replacements and a default fallback to original value, which is efficient and clear.
Option A is correct logically but more complex and nested; however, it also works but is less efficient.
Option A replaces characters by position, which is incorrect for categorical replacements.
Option A replaces substring 'A' everywhere, which can cause wrong replacements.
NewStatus = IF(Table[Status] == "Old", "New", Table[Status])
DAX uses a single '=' for equality comparison, not '=='. Using '==' causes a syntax error.
Option B is incorrect because '==' is a syntax error, not a type error.
Option B is wrong; the expression does not work.
Option B is unrelated to the operator used.
Option A is best because a mapping table allows easy updates and efficient lookups without complex nested logic.
Option A becomes hard to maintain and slow with many replacements.
Option A is not suitable for categorical replacements.
Option A is error-prone and not scalable for ongoing data refreshes.