What does NOT happen due to a lack of architecture concerns?

A lack of architectural concerns directly leads to inherent, structural problems within an application portfolio. These include creating inflexible systems that are slow to change (A), developing unmanageable dependencies between modules (C), and implementing poor service abstractions where business logic is scattered and not reusable (D). These are all direct consequences of poor design.

Option B describes the action of AI Mentor Studio, a tool that detects and reports on technical debt, such as cyclic dependencies. The existence of the technical debt is the consequence of poor architecture; the tool's action of raising an alert is a separate, subsequent event for monitoring and analysis, not a direct outcome of the architectural flaw itself.

A. Inflexible and slow-moving legacy systems are a direct and common consequence of neglecting architectural principles, leading to high maintenance costs and slow adaptation.

C. Unmanageable dependencies are a primary symptom of poor architecture, where a lack of layering and modularity creates a "big ball of mud" that is difficult to maintain.

D. Poor service abstraction is a direct result of failing to properly isolate business concepts, leading to duplicated logic and low code reuse across the application portfolio.

1. OutSystems Official Documentation

"Designing the Architecture of Your OutSystems Applications

" Version 2.1

Page 6

Section "Why is a sound architecture so important?". This document explicitly lists the consequences of a lack of architecture: "The application portfolio becomes a 'big ball of mud' of interconnected applications and modules

with no clear boundaries or purposes... This leads to: Inflexible and slow-moving legacy systems... Unmanageable dependencies... Poor service abstraction." This directly supports that A

C

and D are consequences.

2. OutSystems Official Documentation

"AI Mentor Studio overview

" Section "What is AI Mentor Studio?". This source describes AI Mentor Studio as a tool that "analyzes your OutSystems applications to identify and help you pay back technical debt." This clarifies that the tool's function is to identify issues

distinguishing its action from the issues themselves.

3. OutSystems Official Documentation

"Code analysis patterns

" Section "Architecture". This page lists architectural findings that AI Mentor Studio detects

such as "Cyclic Dependencies" and "Side References between End-user modules." This confirms that the tool reports on the technical debt mentioned in option B

but the reporting is not the consequence itself.