PracticeVideosBlogFlashcardsEspañol
All Practice Exams

100+ Free OutSystems Architecture Specialist (O11) Practice Questions

Prepare for the OutSystems Architecture Specialist (O11 Platform) exam with instant access — no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
100+ Questions
100% Free

Loading practice questions...

Same family resources

Explore More Low-Code Development Certifications

Continue into nearby exams from the same family. Each card keeps practice questions, study guides, flashcards, videos, and articles in one place.

OutSystems Architecture Specialist (ODC)

Practice Questions

OutSystems Delivery Specialist

Practice Questions

OutSystems Front-End Developer Specialist (O11)

Practice Questions

OutSystems Mobile Developer Specialist (O11)

Practice Questions

OutSystems Professional DevOps Engineer

Practice Questions

OutSystems Professional Platform Ops Engineer

Practice Questions
2026 Statistics

Key Facts: OutSystems Architecture Specialist (O11) Exam

~$100

Exam Fee (USD, varies by region)

OutSystems

~70%

Approximate Passing Score

OutSystems certification policy

90 min

Exam Duration

OutSystems

~45-60

Question Count (not officially fixed)

OutSystems (typical range)

3 layers

O11 Canvas: End-User, Core, Foundation (Orchestration removed)

OutSystems 11 documentation

3 rules

No upward, no End-User side, no Core/Foundation circular references

OutSystems 11 documentation

The OutSystems Architecture Specialist (O11) is a proctored multiple-choice exam costing roughly $100 USD, lasting about 90 minutes, with an approximate 70% pass mark and around 45-60 questions. It tests the 4-Layer Canvas, strong versus weak dependencies, the three architecture validation rules, reusability and service-oriented design, performance and scalability patterns, and governance with Discovery and Architecture Dashboard. OutSystems recommends Associate Reactive Developer knowledge first, and the credential is tied to the O11 platform, distinct from the ODC architecture specialization.

Sample OutSystems Architecture Specialist (O11) Practice Questions

Try these sample questions to test your OutSystems Architecture Specialist (O11) exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1In the OutSystems 11 Architecture Canvas, which layer is responsible for holding the screens, user interfaces, and user processes that implement the user stories?
A.End-User layer
B.Orchestration layer
C.Foundation layer
D.Core layer
Explanation: The End-User layer contains the user interfaces and user processes; it reuses Core and Foundation/Library elements to implement the user stories. It is the topmost layer of the canvas and is the only layer that end users interact with directly.
2Why was the Orchestration layer removed from the OutSystems 11 Architecture Canvas compared to OutSystems 10?
A.Orchestration logic was merged into the Foundation layer for reuse
B.Screen destinations became weak references in O11, so a dedicated orchestration layer is no longer required
C.Business Process Technology (BPT) replaced the need for orchestration
D.OutSystems 11 no longer supports linking screens between applications
Explanation: In OutSystems 10 hyperlinks between screens of different applications were strong dependencies, so an Orchestration layer isolated those couplings. In OutSystems 11 screen destinations are treated as weak references, removing that lifecycle-coupling problem, so the Orchestration layer was dropped from the canvas.
3A team needs a module that abstracts and normalizes calls to a third-party REST API so other modules never deal with the external API's particularities. In which Architecture Canvas layer should this integration wrapper module belong?
A.End-User layer
B.Core layer
C.Foundation layer
D.It should not be a separate module
Explanation: An Integration Service (IS) module is a technical wrapper that knows the external API and normalizes its data for internal consumption. Because it is business-agnostic plumbing that connects to an external system, it belongs in the Foundation layer of the canvas.
4Which statement best describes the purpose of a Core (Core Service) module in the OutSystems 11 Architecture Canvas?
A.It contains only the screens and navigation that end users see
B.It wraps native C# extensions built in Integration Studio
C.It provides business-agnostic UI patterns reusable across any application
D.It exports reusable business entities, business rules, and business widgets around a business concept
Explanation: Core modules implement services around business concepts, exposing reusable entities, business rules, and business widgets (Core Widgets). They sit below the End-User layer and above the Foundation layer, encapsulating the data model and logic of a business entity.
5What is the primary goal of the OutSystems Architecture Canvas as a design framework?
A.To promote correct abstraction of reusable services, maximize independent lifecycles, and minimize the impact of change
B.To enforce a single monolithic module per application
C.To replace impact analysis at publish time
D.To maximize the number of modules per application for granularity
Explanation: The Architecture Canvas supports application architecture design by promoting correct abstraction of reusable services and components, maximizing independent lifecycles among the parts of the architecture through correct dependencies, and minimizing the impact of change.
6Validation Rule #1 of OutSystems architecture design states 'No upward references.' What does an upward reference mean?
A.A consumer refreshing a producer dependency
B.A module in a lower layer consuming an element from a higher (more business-specific) layer
C.Two End-User modules referencing each other
D.A Core module referencing another Core module
Explanation: An upward reference occurs when a module in a lower layer (e.g., Foundation or Core) consumes an element from a higher, more business-specific layer (e.g., End-User). This tends to create a cluster where any two modules become directly or indirectly circularly dependent, defeating layer isolation.
7Architecture validation Rule #2 prohibits side references among which modules?
A.Among Core modules
B.Among Foundation (Library) modules
C.Among End-User (and Orchestration) modules
D.Among Extension modules
Explanation: Rule #2 forbids side references among End-User modules (and Orchestration modules in O10). If one End-User module consumes another, it can no longer be deployed or evolve independently, because it inherits the full dependency hierarchy of the consumed End-User module.
8Architecture validation Rule #3 addresses which kind of dependency problem within the Core and Foundation layers?
A.Any reference from Core to Foundation
B.References from Foundation to external systems
C.Strong references to screens
D.Cycles (circular references) among Core or among Foundation modules
Explanation: Rule #3 states there must be no cycles among Core modules or among Foundation/Library modules. A circular reference indicates the business concepts are not correctly abstracted and forces the involved modules to share a lifecycle, undermining independent deployment.
9An architect finds that a Foundation Library module consumes a server action published by an End-User module. According to the canvas, how should this be fixed?
A.Move the reusable element down to a lower layer (e.g., into the Library itself or a Core module)
B.Promote the Library module to the End-User layer
C.Add a weak reference instead of a strong reference
D.Make the End-User action public and refresh the dependency
Explanation: This is an upward reference (Rule #1 violation). The correct fix is to find the consumed element and move it down to the layer where it logically belongs, for example into the Library module or a Core module, so the dependency direction becomes downward and the lifecycle isolation is restored.
10Which type of module is created and developed in Integration Studio rather than Service Studio, typically to wrap native C#/.NET code or connect to non-standard external systems?
A.Library module
B.Extension module
C.Reactive Web module
D.Service module
Explanation: Extension modules are built in Integration Studio. They extend the platform by abstracting C#/.NET code into OutSystems, connecting to non-standard external systems, or wiring up external databases. Extensions are Foundation-layer assets consumed by higher layers.

About the OutSystems Architecture Specialist (O11) Exam

The OutSystems Architecture Specialist (O11) exam validates how a developer or architect designs a healthy, scalable OutSystems 11 application architecture. It centers on the 4-Layer Canvas (End-User, Core, and Foundation, with Orchestration removed in O11 because screen destinations are now weak references), the three validation rules (no upward references, no side references among End-User modules, and no circular references among Core or Foundation modules), and the difference between strong dependencies (entities, structures, server actions, static entities) and weak dependencies (screens, service actions, screen destinations). It also covers application and module composition, reusability through Core Services and Foundation Libraries, service-oriented design with Service Actions and Integration Service wrappers, performance patterns such as cold caching, and architecture governance using Discovery and Architecture Dashboard to manage technical debt.

Assessment

Question count not published by the exam provider

Time Limit

90 minutes

Passing Score

Approximately 70%

Exam Fee

Approximately $100 USD (OutSystems)

OutSystems Architecture Specialist (O11) Exam Content Outline

20-25%

4-Layer Canvas architecture design

Place concepts as modules across the End-User, Core, and Foundation (Library) layers; understand why O11 removed the Orchestration layer; apply the Identify and Organize design process and the canvas goals of correct abstraction, independent lifecycles, and minimized change impact.

20-25%

Application and module composition / dependency management

Distinguish strong dependencies (entities, structures, server actions, static entities) from weak dependencies (screens, service actions, screen destinations); manage refresh dependencies, impact analysis, signature compatibility, and outdated references; compose layered applications by the same validation rules as modules.

20%

Reusability and service-oriented architecture

Abstract reusable Core Services and business-agnostic Foundation Libraries; expose behavior via Service Actions for loose coupling and independent deployment; wrap external systems in Integration Service modules; uphold the single source of truth and leverage native O11 service discovery.

15-20%

Performance and scalability design

Apply cold-cache and synchronization patterns, asynchronous processing with Timers and light processes, indexing and efficient aggregates, parallel Data Actions in Reactive Web, and decomposition into independently deployable, independently scalable services.

15-20%

Architecture governance and technical debt management

Classify modules in Discovery and detect upward, side, and circular reference violations; use Architecture Dashboard (AI Mentor Studio) code and runtime analysis to monitor, prioritize, and remediate technical debt across the application portfolio.

How to Pass the OutSystems Architecture Specialist (O11) Exam

What You Need to Know

  • Passing score: Approximately 70%
  • Assessment: Question count not published by the exam provider
  • Time limit: 90 minutes
  • Exam fee: Approximately $100 USD

Keys to Passing

  • Work through all 100 available questions
  • Review every answer and explanation
  • Track weak areas and revisit them
  • Use our AI tutor for tough concepts

OutSystems Architecture Specialist (O11) Study Tips from Top Performers

1Master the difference between strong dependencies (entities, structures, server actions, static entities) and weak dependencies (screens, service actions, screen destinations), and exactly when each forces a consumer to refresh and republish.
2Memorize the three validation rules and practice spotting upward references, End-User side references, and Core/Foundation cycles in module diagrams, since Discovery reports exactly these.
3Know why O11 removed the Orchestration layer: screen destinations became weak references, so the lifecycle-coupling problem they caused in O10 disappeared.
4Practice placing real concepts on the canvas using naming conventions (_CS for Core Service, _BL for Business Logic, _IS for Integration Service, _Theme), and the cold-cache and synchronization patterns from the soccer-field reference architecture.
5Understand the trade-offs of Service Actions: loose coupling and independent deployment versus remote-call overhead and a separate transaction, so you can justify when to use them over public Server Actions.
6Be fluent in governance: how Discovery classifies modules and detects violations, and how Architecture Dashboard uses code and runtime analysis to surface and prioritize technical debt across the portfolio.

Frequently Asked Questions

What are the key exam facts for the OutSystems Architecture Specialist (O11)?

It is a proctored, multiple-choice exam costing roughly $100 USD, lasting about 90 minutes, with an approximate 70% passing score and around 45-60 questions. Exact question count and voucher pricing vary by region and certification cycle.

What does the OutSystems Architecture Specialist (O11) exam cover?

It covers the 4-Layer Canvas, strong versus weak dependencies, the three validation rules, application and module composition, reusability and service-oriented architecture, performance and scalability patterns, and governance with Discovery and Architecture Dashboard.

Why does OutSystems 11 no longer have an Orchestration layer?

In OutSystems 10, cross-application screen links were strong dependencies isolated by an Orchestration layer. In O11 screen destinations are weak references, so the lifecycle-coupling problem disappeared and the Orchestration layer was removed from the Architecture Canvas.

What are the three architecture validation rules I must know?

No upward references across the layers, no side references among End-User modules, and no circular references among Core or among Foundation modules. Discovery and Architecture Dashboard automatically detect violations of these rules.

Is this the same as the ODC architecture exam?

No. This exam targets the OutSystems 11 (O11) platform and its 4-Layer Canvas. The OutSystems Developer Cloud (ODC) has a separate architecture specialization with cloud-native concepts and platform-enforced service boundaries.

Do I need a prerequisite before taking it?

OutSystems recommends Associate Reactive Developer (Associate Developer) knowledge before attempting the architecture specialization, so you are comfortable building O11 applications before you design their architecture.