Question 1

The Architecture Canvas is a ...

Accepted Answer

B

Explanation: The OutSystems Architecture Canvas is a foundational framework specifically created to guide the design of application architecture. It proposes a three-layer structure (End-user, Core, and Orchestration) for organizing modules within an application portfolio. This layered approach promotes the correct abstraction and isolation of components, leading to increased reusability, easier maintenance, and better scalability. The Canvas serves as a visual and conceptual tool for architects and developers to create a sound, loosely coupled, and well-structured application landscape.

Question 2

ISO/IEC 25010:2011 adds two more aspect to ISO/IEC 9126:1991. Which of the below is not part of it?

Accepted Answer

C

Explanation: The ISO/IEC 25010:2011 standard, part of the SQuaRE series, superseded the older ISO/IEC 9126 standard for software product quality. The new model redefined some characteristics and added two new top-level ones: Security and Compatibility. While "Integration" is a crucial concept, it is defined within ISO/IEC 25010 as a sub-characteristic of Compatibility, alongside Interoperability. Therefore, Integration itself was not one of the main characteristics added to the model, making it the correct answer to the question of which option was not part of the top-level additions.

Question 3

Which of the below is not a best practice for mobile security:authentication?

Accepted Answer

A

Explanation: Storing a user's password in the device's local storage is a critical security vulnerability and is explicitly against best practices. Local storage is not an encrypted or secure container and can be accessed by other applications or malicious actors if the device is compromised. OutSystems recommends using secure, platform-specific storage mechanisms, such as the Keychain on iOS or Keystore on Android, for any sensitive information. This is typically achieved by using supported Forge components like the Key Store Plugin, which provides a secure API to store data. Authentication tokens, not raw passwords, should be stored for session management.

Question 4

There are 3 common scenarios for Sharing a Style Guide. Which of the below is not part of th scenario.

Accepted Answer

B

Explanation: The scenario described in option B is architecturally incorrect for achieving a common, shared login flow. For components like a menu or login flow to be common and easily updatable across multiple applications, they must be defined in a shared, referenced module, such as a Custom Theme. A Custom Template is only used to create a new application; any subsequent changes to the template are not propagated to the applications already created from it. Therefore, placing a common login flow in a template would prevent centralized updates and break the "common" requirement. The other options describe valid, standard OutSystems architectural patterns for sharing UI components.

Question 5

What is Application Composition Process?

Accepted Answer

B

Explanation: The Application Composition Process in OutSystems refers to the fundamental step of creating an application by selecting and grouping one or more modules (eSpaces or Extensions). This process packages the modules into a single deployable and versionable unit. Defining this composition is crucial as it establishes the application's functional scope, its development lifecycle, and how it is managed within the infrastructure. It is a core activity for organizing code and maintaining a sound architecture.

Question 6

OAPI is different compared to API. What is inside an OAPI?

Accepted Answer

A

Explanation: In the context of OutSystems architecture, the term "OAPI" is likely used to refer to the internal Application Programming Interface of an OutSystems module, specifically a Service Module. The core component of this interface, used to expose reusable, non-breaking business logic and functionality to other modules within the same environment, is the Service Action. This provides a strongly-typed, compile-time-checked contract between modules. This is distinct from a REST API, which is a technology used to expose functionality over web standards (HTTP) primarily for external systems or decoupled front-ends.

Question 7

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

Accepted Answer

B

Explanation: 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.

Question 8

Which of the below matches the most to Library Module Pattern - Extension Pattern...

Accepted Answer

I

Explanation: The Extension Pattern refers to the use of an Extension Module, which is a specific type of Library module created in OutSystems Integration Studio. Its primary purpose is to extend the platform's native capabilities. This is achieved by either integrating with an external database, allowing its tables to be used as OutSystems entities, or by wrapping custom C# code and external libraries (.NET assemblies) into reusable Actions. This module then acts as a library, exposing this new functionality to other OutSystems applications.

Question 9

Foundation may have non-business services and business services in them

Accepted Answer

FALSE

Explanation: The statement is false. According to the official OutSystems 3-Layer Canvas architecture, the Foundation layer is designed exclusively for non-business services. Its primary purpose is to provide reusable, non-functional logic and to abstract integrations with external systems. Core business concepts and their corresponding services (e.g., Customer, Product, Order) must be placed in the Core layer. Placing business services in the Foundation layer is considered an architectural anti-pattern as it breaks the intended abstraction and creates incorrect dependencies, leading to a monolithic and less agile application portfolio.

Question 10

Which of the below matches the most to Core Module Pattern - Base ECS Pattern...

Accepted Answer

D

Explanation: The Base ECS (Expose, Consume, Synchronize) pattern, often referred to as the Integration Wrapper pattern, is a fundamental architectural structure for integrating with external systems in OutSystems. It mandates a two-module approach for abstraction and stability. The first module, the Connector, encapsulates all technical aspects of the integration, such as consuming a specific API and its data structures. The second module, the Core Service (or Wrapper), consumes the Connector and exposes a simplified, stable, and business-aligned API to the rest of the application portfolio, effectively hiding the complexity of the external system from the consumers.

Question 11

_Eng module is for

Accepted Answer

C

Explanation: In the OutSystems Architecture Canvas, an Eng module is a specialized type of Business Logic (BL) module. Its primary purpose is to encapsulate complex business calculations or algorithms that are often subject to versioning. By isolating this logic into an "Engine" module, architects can manage, update, and version these complex rules independently from other core services. Typical examples include insurance premium simulators, invoice calculation engines, or complex financial modeling algorithms, where the rules may change over time and require different versions to coexist or be audited.

Question 12

Regarding Validation Rules for application composition, which of the following sentences is correct?

Accepted Answer

A

Explanation: This statement correctly describes a fundamental principle of sound application composition in OutSystems. Isolating common business-agnostic services, core business services, or reusable UI components into separate, dedicated applications (often in the Library or Core layers) is a key best practice. This promotes reusability, loose coupling, and independent lifecycles. Other applications can then reference these shared applications, consuming their functionality without being tightly bound to their development or release cycles, which simplifies maintenance and deployment across the portfolio.

Question 13

In which of the following scenarios should you choose to clone a built-in Style Guide?

Accepted Answer

C

Explanation: Cloning a built-in Style Guide, such as the one provided by OutSystems UI, is the recommended approach when an organization needs to implement extensive and fundamental changes to the base theme. This process creates a new, reusable corporate style guide. This new style guide can then serve as a consistent foundation for all applications within the organization, ensuring a unified look and feel while incorporating significant branding or structural UI modifications that go beyond simple CSS overrides.

Question 14

Which of the below is NOT a reason why application Architecture is important when building quality software solutions?

Accepted Answer

F

Explanation: While application architecture is a critical tool for communication, its primary purpose is to define the technical structure and quality attributes of a software solution. The main goals are to manage complexity, facilitate change, reduce technical risks, and lower long-term costs. The statement "Helps you to get buy in from the business" describes a project management or stakeholder engagement activity. Although a clear architecture facilitates this communication, getting "buy-in" is a secondary outcome, not a fundamental reason for architecture's importance in building a quality technical solution. The other options are direct, core benefits that define the quality and viability of the software itself.

Question 15

Which of the below is not part of the Architecture Validation

Accepted Answer

A

Explanation: Architecture validation in OutSystems enforces the principles of the 4-Layer Canvas (4LC). A core principle of this layered architecture is that modules in a higher layer (e.g., End-User or Core) should reference modules in a lower layer (e.g., Foundation) to consume functionality. This is known as a downward reference and is the correct and intended pattern for code reuse and abstraction. Therefore, a rule prohibiting downward references to Foundation modules is not part of the architecture validation; in fact, the validation encourages this pattern. The other options represent critical architectural violations that are actively checked.

Free OutSystems Architecture-Specialist-11 Actual Exam Questions