Original practice scenario: A fictional banking system receives backdated adjustments after a monthly statement is issued. How should its statement query support both original and corrected views?
Read model answer +
Separate effective transaction time from knowledge time. Reproducing an issued statement requires the records known at issuance, while a corrected view may incorporate later accepted adjustments.
Work through it
Store immutable event revisions with effective and recorded timestamps, and identify each statement by its cutoff and data snapshot.
Apply accepted debit, credit and reversal rules within that snapshot, reconciling opening balance plus movements to closing balance in the account currency.
Test late adjustments, timezone boundaries, duplicate events and a correction that changes a prior month; link corrected statements to the originals.
Tradeoffs to discuss
Bitemporal histories cost storage and query complexity but allow both operational reporting and faithful historical reproduction.
Common pitfalls
Do not overwrite the data that supported an issued statement.
A transaction date and its ingestion date answer different reporting questions.
Original practice scenario: A hypothetical Canadian banking support assistant answers English and French questions from fictional policy documents. How should language quality be evaluated?
Read model answer +
Evaluate factual support and task completion separately from language fluency. Parallel translations can hide errors in terminology, regional phrasing or evidence retrieval across document languages.
Work through it
Create matched and independently authored questions in both languages, including ambiguous requests, unsupported policies and code-switching where relevant.
Score retrieval relevance, citation entailment, key terminology and appropriate inability responses using a documented rubric and qualified reviewers.
Report results by language and question category, testing inconsistent document versions and preserving user language without inventing missing policy details.
Tradeoffs to discuss
Matched questions make comparisons easier but may underrepresent natural language differences; independent questions improve realism with less direct comparability.
Common pitfalls
Do not treat automatic translation quality as proof of correct financial policy.
Use synthetic account examples and avoid requesting private customer information.
