Hello Experts,
Good day
Could you please provide me with right answer with explanation?
1)A Core module should...
1. Provide reusable services around a business concept, as long as it is not consumed by another Core module
2. Be isolated to avoid impacts from changes on external consumers and producers
3. Provide business or non business reusable services, and it can depend on other Core modules
4. Be exposed to external consumers through an Integration Service and reference external producers through an API module
2)Which of the following options is the first rule/step that should be checked in the process to guarantee a good application composition?"
A. To guarantee that the application architecture prevents different lifecycles.
B. To guarantee that each application should only contain one single module, to simplify deployments between environments.
C. To make sure that all modules are developed with the same quality.
D. To make sure that modules are correctly layered and without any architecture finding that goes against best practices.
Thanks
The answer is highlighted in green.
2)Which of the following options is the first rule/step that should be checked in the process to guarantee a good application composition?
Thank you so much. Much appreciated Mate !!
Hello.
The best way to answer those, is by understand the entire set of architecture rules.
I recommend this article as it is concise yet explains all topics. You can then dive deeper into specific areas:
https://www.outsystems.com/blog/posts/application-architecture
Gone through it but sometimes it's hard to find the right answer.
Let me address both of your questions:
The correct answer is: 3. Provide business or non-business reusable services, and it can depend on other Core modules.
For reference, this aligns with the definition of Core modules in the four-layer architecture discussed in OutSystems. A key characteristic is focusing on business entities and rules or providing utility services that multiple apps or modules can use ODC 2018 OutSystems Architecture and Tooling.
The correct answer is: D. To make sure that modules are correctly layered and without any architecture finding that goes against best practices.
This follows best practices detailed in OutSystems architecture guidelines, where correct layering is emphasized as the first step to a stable and maintainable architecture ODC 2018 OutSystems Architecture and Tooling.
Hope that helps clarify your questions! Let me know if further explanation is needed.