Automated risk scenario generation tools operate based on programmed logic, historical data, and pattern recognition. They may excel at generating scenarios based on known risks and documented processes but struggle to account for complex organizational interdependencies that are not fully captured in their data inputs.

Why D is Correct: The ISACA AAIR risk scenario development guidance identifies the failure to account for process interdependencies as the greatest risk from automated scenario generation. AI systems do not operate in isolation—they are embedded in complex organizational ecosystems where failures cascade through interconnected processes, systems, and stakeholders. Automated tools may miss these interdependencies, producing scenarios that are technically accurate in isolation but miss the most consequential cascade effects.

Why A is Wrong: Complexity in likelihood and impact scoring is a risk quantification challenge that affects scenario prioritization but does not result in missing scenarios entirely. Complex scoring can be managed through additional analytical methods.

Why B is Wrong: Emerging adversarial attack vectors are a potential blind spot for any tool or analyst working from historical data, but this is a known limitation of retrospective approaches that can be supplemented with threat intelligence. It does not represent the distinctive risk of automated scenario generation.

Why C is Wrong: Underestimating model change impacts is a scenario calibration issue that represents a less severe risk than missing entire categories of scenarios arising from unmodeled interdependencies.