// IFF719 — Financial intelligence analytics and typology detection
$CATEGORY: VERITAS/IFF719

::IFF719-Q1::Under FATF guidance and Egmont Group practice, why is a rising STR/SAR volume not, on its own, evidence of a healthier AML system? {
    ~Because FIUs are legally capped in how many reports they may receive annually#Incorrect. Defensive filing inflates volume while lowering average report quality, which is why FATF effectiveness assessments look at dissemination outcomes rather than raw filing counts.
    =Because rising volume can reflect defensive filing that dilutes analytical value rather than genuine risk-based reporting#Defensive filing inflates volume while lowering average report quality, which is why FATF effectiveness assessments look at dissemination outcomes rather than raw filing counts.
    ~Because STR volume is confidential and cannot be measured by regulators#Incorrect. Defensive filing inflates volume while lowering average report quality, which is why FATF effectiveness assessments look at dissemination outcomes rather than raw filing counts.
    ~Because only cross-border reports are counted in FATF effectiveness assessments#Incorrect. Defensive filing inflates volume while lowering average report quality, which is why FATF effectiveness assessments look at dissemination outcomes rather than raw filing counts.
}

::IFF719-Q2::What is the primary evidentiary risk of presenting a network diagram directly to a court without further substantiation? {
    ~Network diagrams are inadmissible in every jurisdiction#Incorrect. A network diagram visualises hypothesised relationships; each depicted edge must be grounded in underlying documentary or testimonial evidence before it carries probative weight.
    =The diagram is a hypothesis-generation tool and its edges must be traceable to independently verifiable documents#A network diagram visualises hypothesised relationships; each depicted edge must be grounded in underlying documentary or testimonial evidence before it carries probative weight.
    ~Courts require diagrams to be produced only by machine-learning software#Incorrect. A network diagram visualises hypothesised relationships; each depicted edge must be grounded in underlying documentary or testimonial evidence before it carries probative weight.
    ~Network diagrams cannot legally include natural persons#Incorrect. A network diagram visualises hypothesised relationships; each depicted edge must be grounded in underlying documentary or testimonial evidence before it carries probative weight.
}

::IFF719-Q3::A false merge in entity resolution results in which outcome? {
    =Two distinct real-world entities are wrongly treated as a single entity, contaminating the network with unrelated transactions#A false merge wrongly combines two distinct entities, introducing unrelated transactional data into the network and generating false positives.
    ~A single entity is split into two apparently unrelated records#Incorrect. A false merge wrongly combines two distinct entities, introducing unrelated transactional data into the network and generating false positives.
    ~A transaction is duplicated in the ledger#Incorrect. A false merge wrongly combines two distinct entities, introducing unrelated transactional data into the network and generating false positives.
    ~A beneficial-ownership register entry is deleted#Incorrect. A false merge wrongly combines two distinct entities, introducing unrelated transactional data into the network and generating false positives.
}

::IFF719-Q4::Why is betweenness centrality particularly useful for identifying professional enablers in a laundering network? {
    ~It measures the total transaction value processed by an entity#Incorrect. Professional enablers often exist structurally to connect clusters that would otherwise have no reason to interact, which is exactly what betweenness centrality measures.
    =It identifies entities positioned on the shortest path between otherwise unconnected clusters, matching the structural role enablers play#Professional enablers often exist structurally to connect clusters that would otherwise have no reason to interact, which is exactly what betweenness centrality measures.
    ~It only applies to entities with the highest transaction frequency#Incorrect. Professional enablers often exist structurally to connect clusters that would otherwise have no reason to interact, which is exactly what betweenness centrality measures.
    ~It automatically confirms criminal intent#Incorrect. Professional enablers often exist structurally to connect clusters that would otherwise have no reason to interact, which is exactly what betweenness centrality measures.
}

::IFF719-Q5::What governance failure allowed the machine-learning alert-scoring layer in the case study to deprioritise the shell-company network? {
    =The model was never validated and inherited historical under-investigation bias from its training labels#Models trained on historical alert-disposition labels inherit whatever blind spots existed in that history; independent validation is designed to catch precisely this failure mode.
    ~The model used only rules-based logic#Incorrect. Models trained on historical alert-disposition labels inherit whatever blind spots existed in that history; independent validation is designed to catch precisely this failure mode.
    ~The model was deployed without any regulatory approval process anywhere in the world#Incorrect. Models trained on historical alert-disposition labels inherit whatever blind spots existed in that history; independent validation is designed to catch precisely this failure mode.
    ~The model exclusively monitored cash transactions#Incorrect. Models trained on historical alert-disposition labels inherit whatever blind spots existed in that history; independent validation is designed to catch precisely this failure mode.
}

::IFF719-Q6::Under POPIA and GDPR-equivalent frameworks, what obligation typically arises when an automated model materially affects a customer, such as through an account restriction? {
    ~No obligation arises if the model is proprietary#Incorrect. Both POPIA and GDPR-equivalent regimes require meaningful information about automated-decision logic and, typically, a right to human review where the decision has significant effect.
    =The institution must provide meaningful information about the logic involved and generally ensure human review of the decision#Both POPIA and GDPR-equivalent regimes require meaningful information about automated-decision logic and, typically, a right to human review where the decision has significant effect.
    ~The customer must be charged a fee for an explanation#Incorrect. Both POPIA and GDPR-equivalent regimes require meaningful information about automated-decision logic and, typically, a right to human review where the decision has significant effect.
    ~The model's source code must be published publicly#Incorrect. Both POPIA and GDPR-equivalent regimes require meaningful information about automated-decision logic and, typically, a right to human review where the decision has significant effect.
}

::IFF719-Q7::What was the primary legal innovation of the UK's Joint Money Laundering Intelligence Taskforce (JMLIT)? {
    ~It eliminated the requirement to file STRs entirely#Incorrect. JMLIT, enabled by the Criminal Finances Act 2017, provided a statutory basis for cross-institutional and law-enforcement information sharing that would otherwise breach confidentiality or data-protection law.
    =It created a statutory gateway allowing banks, law enforcement and the FIU to share information under protection from ordinary confidentiality constraints#JMLIT, enabled by the Criminal Finances Act 2017, provided a statutory basis for cross-institutional and law-enforcement information sharing that would otherwise breach confidentiality or data-protection law.
    ~It centralised all UK bank data into a single government-owned database#Incorrect. JMLIT, enabled by the Criminal Finances Act 2017, provided a statutory basis for cross-institutional and law-enforcement information sharing that would otherwise breach confidentiality or data-protection law.
    ~It replaced FATF Recommendation 16 with a UK-specific standard#Incorrect. JMLIT, enabled by the Criminal Finances Act 2017, provided a statutory basis for cross-institutional and law-enforcement information sharing that would otherwise breach confidentiality or data-protection law.
}

::IFF719-Q8::Why might secure multi-party computation be preferred over full data pooling for cross-institution AML analytics? {
    ~It is always faster than any other computational method#Incorrect. Secure multi-party computation enables institutions to jointly compute an analytical result while each retains control of its own raw data, reducing the privacy trade-off of centralised pooling.
    =It allows a joint result to be computed without any institution disclosing its raw underlying customer data#Secure multi-party computation enables institutions to jointly compute an analytical result while each retains control of its own raw data, reducing the privacy trade-off of centralised pooling.
    ~It removes the need for any legal basis to process personal data#Incorrect. Secure multi-party computation enables institutions to jointly compute an analytical result while each retains control of its own raw data, reducing the privacy trade-off of centralised pooling.
    ~It is required under all FATF Recommendations#Incorrect. Secure multi-party computation enables institutions to jointly compute an analytical result while each retains control of its own raw data, reducing the privacy trade-off of centralised pooling.
}

::IFF719-Q9::In the false-positive economics of transaction monitoring, what is the central operational trade-off compliance functions must manage? {
    ~Between hiring more analysts and closing the compliance function entirely#Incorrect. Scenario tuning requires an explicit, documented trade-off between reducing analyst workload from false positives and the risk of introducing false negatives.
    =Between tightening thresholds to reduce false positives (risking missed true positives) and leaving thresholds conservative (accepting high manual-review cost)#Scenario tuning requires an explicit, documented trade-off between reducing analyst workload from false positives and the risk of introducing false negatives.
    ~Between using only cash-based rules and only wire-based rules#Incorrect. Scenario tuning requires an explicit, documented trade-off between reducing analyst workload from false positives and the risk of introducing false negatives.
    ~Between reporting to the FIU and reporting to the central bank exclusively#Incorrect. Scenario tuning requires an explicit, documented trade-off between reducing analyst workload from false positives and the risk of introducing false negatives.
}

::IFF719-Q10::What structural failure did the two banks' independent STR filings referencing the same registered address illustrate in the case study? {
    ~A failure of individual analyst competence at each bank#Incorrect. Both banks independently held relevant intelligence; the absence of a sharing mechanism, not analyst error, is what allowed the corroborating link to go unrecognised for so long.
    =A structural failure of the AML system to enable information sharing between institutions holding corroborating intelligence#Both banks independently held relevant intelligence; the absence of a sharing mechanism, not analyst error, is what allowed the corroborating link to go unrecognised for so long.
    ~A failure of the company-formation agent to conceal the address adequately#Incorrect. Both banks independently held relevant intelligence; the absence of a sharing mechanism, not analyst error, is what allowed the corroborating link to go unrecognised for so long.
    ~A failure of the remittance platform's currency conversion process#Incorrect. Both banks independently held relevant intelligence; the absence of a sharing mechanism, not analyst error, is what allowed the corroborating link to go unrecognised for so long.
}