ARCHITECTURE-SPECIALIST-11 practice question 15 of 15
Which of the below is not part of the Architecture Validation
Full set: 83 questionsArchitecture 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.
B. No Side References Between End-User Modules: This is a standard validation rule. Side references between End-User modules create a monolithic front-end, hindering independent deployment and lifecycle management.
C. No Circular References: This is a fundamental architectural violation. Circular dependencies create strong coupling, making modules difficult to maintain, deploy, and understand.
D. No Upward References: This is the primary rule of layered architecture. A module in a lower layer must not depend on a module in a higher layer to maintain proper abstraction.
1. OutSystems Official Documentation
"The 4-Layer Canvas": This document outlines the fundamental rules for module references. It states
"The rules for referencing modules are simple: a module can only reference modules in the same layer or in a layer below." This directly confirms that downward references are allowed and expected
making option A incorrect as a validation rule. It also implicitly supports that upward references are forbidden (Option D).
Reference: OutSystems Success Center
"The 4-Layer Canvas
" section: "Module references."
2. OutSystems Official Documentation
"Validating your application architecture": This guide details the specific violations detected by OutSystems architecture validation tools. It explicitly lists "No upward references between layers
" "No side references among End-user or Public/API modules
" and "No circular references between modules" as key findings. This directly validates that options B
C
and D are indeed part of the architecture validation process.
Reference: OutSystems Success Center
"Validating your application architecture
" section: "Architecture findings."
Keep practicing
Take the free ARCHITECTURE-SPECIALIST-11 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other ARCHITECTURE-SPECIALIST-11 practice questions
- Question 1The Architecture Canvas is a ...
- Question 2ISO/IEC 25010:2011 adds two more aspect to ISO/IEC 9126:1991. Which of the below is not p…
- Question 3Which of the below is not a best practice for mobile security:authentication?
- Question 4There are 3 common scenarios for Sharing a Style Guide. Which of the below is not part of…
- Question 5What is Application Composition Process?
- Question 6OAPI is different compared to API. What is inside an OAPI?
