Refer to the exhibit. The Data Architect is implementing a validation policy for incoming master data. What does this specific JSON policy achieve?
Exhibit
{
"rule_id": "VAL_001",
"field": "BillingCountry",
"pattern": "^[A-Z]{2}$",
"action": "REJECT",
"on_error": "LOG_AND_NOTIFY"
}Trap 1: It converts all incoming country names to a two-letter format.
The policy defines a pattern for rejection, not a transformation or mapping function. It does not contain logic to translate long-form names like 'United States' into 'US'; instead, it proactively rejects any data that does not already conform to the predefined two-letter uppercase format.
Trap 2: It automatically updates the BillingCountry to the correct value if…
The policy lacks a 'CORRECT' or 'TRANSFORM' action. The logic specified is 'REJECT' on error, which means the system does not attempt to fix or infer the intended value, but rather blocks the record entirely, requiring the source system to correct the data before a successful resubmission.
Trap 3: It allows any country code but logs it for later manual review by a…
The policy includes an action of 'REJECT', which is a hard block on the transaction. While it logs the error, the record itself is prevented from entering the system, meaning the business process dependent on that record will fail until the data is corrected and re-submitted by the source.
- A
It converts all incoming country names to a two-letter format.
Why it fails: The policy defines a pattern for rejection, not a transformation or mapping function. It does not contain logic to translate long-form names like 'United States' into 'US'; instead, it proactively rejects any data that does not already conform to the predefined two-letter uppercase format.
- B
It rejects any record where the BillingCountry does not match the two-letter ISO code.
The regex pattern ^[A-Z]{2}$ mandates a strict two-letter format. By setting the action to REJECT, the system prevents invalid country codes from being processed, thereby maintaining high data quality by ensuring that only compliant records are accepted into the master database for further downstream consumption.
- C
It automatically updates the BillingCountry to the correct value if an error is found.
Why it fails: The policy lacks a 'CORRECT' or 'TRANSFORM' action. The logic specified is 'REJECT' on error, which means the system does not attempt to fix or infer the intended value, but rather blocks the record entirely, requiring the source system to correct the data before a successful resubmission.
- D
It allows any country code but logs it for later manual review by a steward.
Why it fails: The policy includes an action of 'REJECT', which is a hard block on the transaction. While it logs the error, the record itself is prevented from entering the system, meaning the business process dependent on that record will fail until the data is corrected and re-submitted by the source.