Question 500
Eastport Research Hospital processes medical research systems and directory accounts during an approved maintenance window. The investigation finds: A customer identifier is supposed to be unique but repeated keys enter a reporting table unchecked. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
A controlled duplicate-key input is detected and reconciled according to the expected data contract. The observation provides evidence that the proposed fix (Validate key cardinality or deduplication rules before accepting the transformed dataset.) addressed the reported issue (A customer identifier is supposed to be unique but repeated keys enter a reporting table unchecked.) for Eastport Research Hospital and its medical research systems and directory accounts. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
Inserting a null transaction identifier fails or is routed through the documented rejection path. This is suitable evidence for another condition (A financial table allows nullable transaction IDs despite audit requirements for a valid identifier on every accepted row.) after a different response (Apply a NOT NULL constraint or equivalent supported validation where appropriate.). For Eastport Research Hospital, it does not prove the required result: A controlled duplicate-key input is detected and reconciled according to the expected data contract.
A synthetic duplicate burst triggers the intended uniqueness warning even if total row volume is unchanged. This is suitable evidence for another condition (A data quality dashboard shows only overall row count and overlooks a sharp decline in uniqueness of important business keys.) after a different response (Add cardinality and distinctness checks with measurable thresholds to the dataset acceptance process.). For Eastport Research Hospital, it does not prove the required result: A controlled duplicate-key input is detected and reconciled according to the expected data contract.
A missing-key test row follows the configured reject or quarantine behavior and accepted rows have valid IDs. This is suitable evidence for another condition (An essential source identifier is nullable in the incoming schema and downstream joins lose records without warning.) after a different response (Define an explicit non-null validation rule or expectation for the identifier.). For Eastport Research Hospital, it does not prove the required result: A controlled duplicate-key input is detected and reconciled according to the expected data contract.