Question 560
The previous outage involved this problem: A finance database is moved to an inexpensive region without considering contracts requiring data to remain in-country. What long-term control addresses the risk?
Explanation
Correct Answer
Apply data-location controls to temporary transfer resources as well as final instances. This is preventive rather than a one-time repair; it addresses the underlying failure: Target placement was selected before validating data location and backup residency restrictions.
Incorrect Answers
For the situation in which an application with very large binary fields is migrated through a generic CSV export and attachment data is truncated, it makes sense to test maximum object sizes and binary fields before bulk migration. Here, target placement was selected before validating data location and backup residency restrictions, so the safeguard misses the recurring fault.
This would test application configuration changes as part of migration dry runs. It is useful when a migration rehearsal finishes copying data but the target application fails because its database hostnames still point at the old deployment, but it does not prevent the issue here: target placement was selected before validating data location and backup residency restrictions.
This control would validate database extension support in homogeneous migrations, not just core engine names; it responds to the risk in which a PostgreSQL migration job creates tables but fails on an unsupported extension used by the source. It would not address the current root cause: target placement was selected before validating data location and backup residency restrictions.