Question 650
Engineers believe they have resolved this failure: A CRM migration converts customers' non-Latin names to replacement characters in the target. Which follow-up evidence is most convincing?
Explanation
Correct Answer
Multilingual names and search values round-trip exactly. The observed state validates the proposed fix: Use a validated Unicode-capable source-to-target encoding path and reload affected records. It addresses this cause: The transfer pipeline uses an incompatible character encoding for source text.
Incorrect Answers
Even if this observation were recorded, it would support a case where a customer database transfer carries obsolete account records that were supposed to be deleted under a retention policy. It would not verify that multilingual names and search values round-trip exactly.
That result would matter when a mapping application drops geometries when moving spatial columns between SQL engines. It does not establish that multilingual names and search values round-trip exactly, which is the evidence needed here.
That result would matter when a T-SQL job from SQL Server fails on PostgreSQL because it uses engine-specific temporary table and variable syntax. It does not establish that multilingual names and search values round-trip exactly, which is the evidence needed here.