CORES Loss Data Collection & Analysis 3 — Questions and Answers
Question 1: Which Basel II event-type category captures losses from unauthorized trading by an employee acting within the scope of their employment?
- External Fraud
- Internal Fraud (Correct answer)
- Clients, Products & Business Practices
- Execution, Delivery & Process Management
Correct answer: Internal Fraud
Unauthorized trading by an employee is classified under Internal Fraud (ET1), specifically the sub-category of unauthorized activity.
Question 2: What is the primary purpose of maintaining a 'boundary event' taxonomy in a loss database?
- To separate losses by geography
- To distinguish operational losses that also have credit or market risk components (Correct answer)
- To flag events exceeding regulatory thresholds
- To identify losses caused by third-party vendors
Correct answer: To distinguish operational losses that also have credit or market risk components
Boundary event taxonomy ensures proper classification when a loss spans multiple risk types, preventing double-counting in capital calculations.
Question 3: Which quality control mechanism is BEST suited to detect systematic underreporting of small operational losses by front-office business lines?
- External audit of the loss database
- Benchmarking internal loss frequency against peer consortium data
- Increasing mandatory reporting thresholds
- Automated reconciliation of GL entries to loss events (Correct answer)
Correct answer: Automated reconciliation of GL entries to loss events
Reconciling general ledger expense entries against recorded loss events is the most direct control to identify losses booked to P&L but not captured in the risk database.
Question 4: In operational risk modeling, what is the primary limitation of relying solely on internal loss data for estimating tail risk at the 99.9th percentile?
- Internal data is too granular for statistical modeling
- Internal loss histories are typically too short to capture rare high-severity events (Correct answer)
- Internal data violates normality assumptions required for VaR
- Internal data cannot be segmented by business line
Correct answer: Internal loss histories are typically too short to capture rare high-severity events
Most banks have only 5-10 years of internal loss history, which is insufficient to credibly estimate extremely rare catastrophic events.
Question 5: A loss event begins in Year 1 but legal proceedings extend recovery efforts into Year 4. According to BCBS loss data principles, when should the event date be recorded?
- Year 1, when the triggering event occurred (Correct answer)
- Year 4, when final resolution is reached
- Year 2, when the loss was first recognized on the P&L
- Each year proportionally as costs are incurred
Correct answer: Year 1, when the triggering event occurred
The event date should reflect when the original triggering incident occurred, not when the loss is recognized or resolved, to preserve accurate risk trending.
Question 6: Which of the following is an example of a 'timing loss' in operational risk loss data collection?
- A loss caused by a market price movement during a system outage
- A fee charged to a client that should have been waived under a contractual agreement
- A revenue gain that subsequently reversed due to a valuation error (Correct answer)
- A loss from a natural disaster affecting a data center
Correct answer: A revenue gain that subsequently reversed due to a valuation error
Timing losses arise from revenue or valuation misstatements that reverse when corrected, temporarily inflating or deflating P&L.
Question 7: What role does 'data lineage' play in an operational risk loss database?
- It tracks the age of each loss record to trigger archiving
- It documents the origin, transformation, and movement of loss data to support auditability (Correct answer)
- It categorizes losses by the business line that originated the transaction
- It maps loss events to specific risk owners for accountability
Correct answer: It documents the origin, transformation, and movement of loss data to support auditability
Data lineage ensures regulators and auditors can trace every loss record back to its source system, validating data integrity and completeness.
CORES Loss Data Collection & Analysis 3
Which Basel II event-type category captures losses from unauthorized trading by an employee acting within the scope of their employment?