Question 960
Two deployment environments use different currency lookup codes, causing inconsistent reports. What is the MOST appropriate immediate corrective approach?
Explanation
Correct Answer
Version reference data alongside schema and apply idempotent migration scripts. This targets the primary issue because untracked static data can drift even when table definitions match. Verification: Both environments contain the same expected currency code set. Prevent recurrence: Review seed-data changes like schema changes.
Incorrect Answers
Remove sensitive values and parameterize environment configuration outside version control. The relevant technical condition instead is that version reference data alongside schema and apply idempotent migration scripts.
Redact secrets from diagnostics and use structured error codes. The relevant technical condition instead is that version reference data alongside schema and apply idempotent migration scripts.
Using protected branch triggers, environment approval gates and deployment-specific identities would not correct two deployment environments use different currency lookup codes, causing inconsistent reports. Version reference data alongside schema and apply idempotent migration scripts.