AI0-001 AI Implementation and Operations Practice Question
A financial institution needs to integrate an AI-based credit scoring model into an existing mainframe system that processes transactions in COBOL. The model is deployed as a REST API. What is the best strategy to ensure minimal disruption and maintain data integrity?
⚠ Common exam trap
CompTIA often tests the misconception that legacy systems must be replaced or heavily modified to integrate with modern AI services, when in fact an API gateway provides a non-invasive integration layer that preserves the existing infrastructure.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use an API gateway with versioning and circuit breaker patterns.
An API gateway with versioning and circuit breaker patterns allows the COBOL mainframe to call the REST API without modifying its core transaction logic. The gateway handles protocol translation, rate limiting, and failover, ensuring minimal disruption to the existing mainframe system while maintaining data integrity through transactional consistency and graceful degradation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Copy all transaction data to a cloud database for the model to access.
Why it's wrong here
Copying transaction data to a cloud database introduces a second copy of record, so the COBOL mainframe and the model can diverge between batch syncs, breaking data integrity. It is tempting because cloud databases suit analytics workloads where latency and consistency are relaxed; here the REST API must read the mainframe's live data instead.
- ✓
Use an API gateway with versioning and circuit breaker patterns.
Why this is correct
An API gateway with versioning and circuit breakers isolates the COBOL mainframe from model changes, letting the REST API evolve without breaking existing calls. Circuit breakers halt failing requests, preventing cascading timeouts and preserving transaction data integrity during partial outages.
- ✗
Rewrite the mainframe system in Java to directly call the model.
Why it's wrong here
Rewriting the mainframe in Java replaces a working transaction system, maximising disruption and risking data integrity during migration. Full re-platforming suits greenfield modernisation programmes; here the REST API can be called from COBOL directly, leaving the system of record untouched.
- ✗
Install a GPU on the mainframe to run the model natively.
Why it's wrong here
Running the model natively on a mainframe GPU ignores the REST API deployment: the model is already served elsewhere, so local inference hardware adds nothing. GPUs on mainframes suit native COBOL batch scoring, not consuming an external API. The integration requirement is HTTP connectivity and transactional consistency, which this option does not address.
About these practice questions
This AI0-001 question is part of Courseiva's 962-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AI0-001 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AI0-001 exam.