AI0-001 AI Implementation and Operations Practice Question
A retail company runs an AI-powered demand forecasting service in a Kubernetes cluster. The inference pods scale based on CPU utilization, but during flash sales the request queue grows rapidly and p99 latency spikes before new pods become ready. The operations team needs to reduce latency during these spikes without changing the model itself. Which action should the team take?
⚠ Common exam trap
The trap here is assuming that any autoscaling configuration will fix latency, when the real issue is that the scaling signal does not reflect the actual bottleneck.
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
✓
Configure a Horizontal Pod Autoscaler (HPA) based on a custom external metric that reflects request queue depth, and lower the scale-up stabilization window.
The root cause is that CPU-based autoscaling reacts too slowly to a sudden queue buildup. Using a custom metric tied to queue depth or concurrent requests, combined with a shorter scale-up stabilization window, lets the HPA add capacity before latency degrades. The other options either add latency, waste resources, or do not improve reaction speed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable a Kubernetes PodDisruptionBudget for the inference deployment and increase the replica count permanently.
Why it's wrong here
A PodDisruptionBudget protects availability during voluntary disruptions and does not scale on load. Permanently increasing replicas wastes resources during normal periods and still may not keep up with flash-sale bursts, so it does not deliver the responsive scaling the scenario needs.
- ✓
Configure a Horizontal Pod Autoscaler (HPA) based on a custom external metric that reflects request queue depth, and lower the scale-up stabilization window.
Why this is correct
Scaling on queue depth or concurrent requests reacts faster than CPU, which lags behind sudden bursts. Shortening the scale-up stabilization window lets the HPA add replicas sooner, reducing p99 latency during flash sales. This directly addresses the mismatch between the current CPU-based trigger and the actual bottleneck, the growing request queue.
- ✗
Set the Kubernetes resource requests and limits for the inference pods to the maximum available node capacity.
Why it's wrong here
Raising requests and limits may improve scheduling and prevent throttling, but it does not change how quickly the deployment reacts to a surge. The bottleneck is the autoscaling trigger and reaction time, not the pod resource ceiling, so this action leaves the latency spike unaddressed.
- ✗
Increase the model's batch size and enable request batching to improve throughput per pod.
Why it's wrong here
Batching can raise throughput, but it usually increases per-request latency because requests wait for the batch to fill. The scenario requires lower p99 latency during spikes, and batching alone does not add capacity fast enough to drain the queue, so it fails to solve the stated symptom.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
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.