A financial services firm must build a model that flags potentially fraudulent card transactions in under 200 milliseconds while keeping all data inside its own Amazon VPC. The fraud team has thousands of labeled historical transactions and the pattern changes slowly over months. Which approach best balances latency, data residency, and the need for periodic retraining?
Fraud flagging with thousands of labeled transactions is a supervised classification problem, and a SageMaker real-time endpoint keeps inference within the VPC at low millisecond latency. Scheduled retraining jobs let the model adapt as fraud patterns drift over months. This combination satisfies the latency, residency, and retraining requirements directly without introducing external data movement.
Why this answer
A supervised classification model trained on the labeled history and deployed to a SageMaker real-time endpoint inside the VPC meets the latency and residency constraints, while scheduled retraining handles gradual fraud pattern drift. Purpose-built supervised learning uses the available labels, and in-VPC endpoints keep transaction data within the controlled network. Batch, unsupervised, or general foundation-model approaches each miss at least one hard requirement.
Exam trap
The trap here is treating a managed fraud service or foundation model as automatically better than a purpose-built supervised model that meets the stated latency and residency constraints.