A cybersecurity administrator generates patching reports using AI, but the process takes a long time.

Basic Concept: AI systems that repeatedly query external data sources for similar information during a single report generation process spend significant time on redundant network requests. Caching frequently accessed data locally eliminates this overhead. CompTIA SecAI+ Study Guide covers AI performance optimization strategies in security operations contexts.

Why B is Correct: Downloading the full CVE database locally before starting the cross-referencing process eliminates the need for multiple individual external API calls as the AI processes each OS version ' s patch list. Instead of making thousands of small external queries to look up CVE information for each patch-OS combination, the AI can query the locally cached database internally. This transforms multiple slow external network operations into fast local lookups, dramatically reducing report generation time.

Why A is Wrong: Using an MCP server to run multiple LLM queries simultaneously could improve throughput through parallelization. However, the fundamental bottleneck is external CVE database queries, not LLM processing capacity. Parallelizing LLM calls does not eliminate the external query latency.

Why C is Wrong: Specifying summarization algorithms in the system prompt affects how the AI structures its output. It does not address the time-consuming external data retrieval process that is the actual performance bottleneck in this cross-referencing workflow.

Why D is Wrong: Increasing token limits prevents session restarts for long contexts but does not address the external query latency that makes the report slow to generate. The bottleneck is data retrieval speed, not token limit constraints causing session breaks.