Question 660
An earlier incident involved this issue: A table holding values above a 32-bit range fails import because its destination integer column is too small. Which continuing safeguard would address the risk?
Explanation
Correct Answer
Check actual data ranges rather than only declared source types during conversion. The original failure arose from: Numeric type mapping did not account for the real source value domain. The control reduces that failure mode.
Incorrect Answers
The failure in the question arises because numeric type mapping did not account for the real source value domain. A safeguard to test application configuration changes as part of migration dry runs serves situations where a migration rehearsal finishes copying data but the target application fails because its database hostnames still point at the old deployment rather than this one.
The proposed check would include nested, Unicode and malformed document fixtures in conversion testing, helping with cases where a PostgreSQL target rejects records from a source JSON-like document column because some values contain invalid encoding. The recurring exposure described here is that numeric type mapping did not account for the real source value domain.
Here, numeric type mapping did not account for the real source value domain. The option concerns the separate risk of a situation in which a database migration moves tables but dozens of stored procedures continue using source-engine functions.