OutSystems Architecture Specialist (O11) study guide
OutSystems Architecture Specialist (O11) · Work through your exam, one topic at a time.
The Architecture Specialist (O11) is a specialization exam in the OutSystems certification program, delivered in English, Español, 日本語 and Português (BR), lasting 90 minutes and costing $100 US. OutSystems describes specializations as shorter exams focused on a specific topic or area, and states that a specialization can work as the final outcome for a role or experience level, or as a path to a new certification. This one concentrates on the fundamentals of OutSystems Architecture design. It targets developers or architects who are fairly autonomous in designing a good OutSystems Architecture with a scalable mindset, and who aim to contribute to an efficient and healthy lifecycle of applications. The OutSystems Architecture Specialist (O11) study guide has 4 sections and about 1,501 words.
01Architecture design fundamentals: placing modules on the OutSystems Architecture Canvas
The Architecture design fundamentals domain checks whether you can take a requirement and place every module, element and integration on the right layer of the OutSystems Architecture Canvas - and defend that placement. Foundation - modules that wrap external systems (consumed REST/SOAP, database catalogs, extensions).
388 words, about 2 min02Scalable architecture design: stateless tiers, data volume and asynchronous work
Scalable architecture design tests whether your module split and runtime choices still hold when concurrent users, data volume and node count grow. OutSystems front-ends keep no authoritative state in memory: session variables live in the session database and are re-read on each request.
378 words, about 2 min03Application lifecycle efficiency and health: pipeline, impact analysis and technical debt
Application lifecycle efficiency and health is about moving changes from Development to Production quickly and safely, and keeping the portfolio free of accumulating debt. Development → QA → Pre-Production → Production, orchestrated in LifeTime.
341 words, about 2 min04Architecture roles and responsibilities: developer autonomy inside architect-owned boundaries
Architecture roles and responsibilities covers who decides what, and how much autonomy a developer legitimately has inside the architecture. Developer - builds and publishes in Development.
394 words, about 2 min