Original practice scenario: A hypothetical banking application portal checks whether a submission contains required documents. Requirements depend on applicant type and submission date. Design an explainable rules engine.
Read model answer +
Separate document completeness from substantive application approval. A technically complete file set can still require authorized review, and an unreadable file is different from an absent one.
Work through it
Version the requirement matrix by applicant category and effective date, validating the category and date before selecting applicable document rules.
Identify submitted document type, version and readability status, distinguishing absent, expired, conflicting and not-yet-reviewed evidence in the result.
Return stable rule identifiers and specific next actions, retaining the original requirement version when the applicant resubmits or policy changes.
Tradeoffs to discuss
Strict required-document rules improve consistency but need clear exception handling; manual discretion supports unusual cases while requiring accountable review.
Common pitfalls
Do not mark an unavailable parsing service as a passed content check.
A later policy version must not silently redefine why an earlier submission was classified incomplete.
Original practice scenario: A hypothetical banking analytics dataset links borrowers to facilities and facilities to several collateral records. Explain how to produce a borrower-level exposure summary.
Read model answer +
Define the exposure measure at facility grain and treat collateral allocation as a separate relationship. Joining raw facility amounts to every collateral record can multiply the apparent exposure.
Work through it
Validate facility identity, borrower ownership and the reporting cutoff, aggregating any transaction-level amounts to one intended facility measure first.
Prepare collateral and allocation summaries independently, preserving shared collateral relationships and any approved allocation weights rather than assigning full value repeatedly.
Join compatible summaries to borrowers and reconcile total exposure before and after enrichment, returning missing ownership or allocation evidence separately.
Tradeoffs to discuss
Borrower summaries are easier to review but can conceal facility-specific constraints; retained detail supports drill-down and reconciliation.
Common pitfalls
Do not sum collateral values as though they were interchangeable with exposure amounts.
This practice report describes data assembly, not a lending decision or a verified valuation methodology.
