Outsystem Pro - 7 (All)
Consider a scenario where there is an application with an unexpected behavior When a developer queries
the built-in User Entity, with a SQL element or an Aggregate, only one user, with the admin username, is
being displayed However, when accessing the database directly all the application Users are present What
can be the reason for this behavior?
A The module is integrating with Active Directory (AD) As AD Users are never copied to the
K
OutSystems User Entity. the only user available is the original admin
B The User Provider of the module is set as Service Center, where the admin user is the only IT User
created in the system
C
C The developer is logged in as admin and its user does not have enough permissions to query other
Users, so only the developers user details are visible
D Another User is accessing the same table concurrently, locking it, so the developer only has access to
LO
the first record, which is the admin User
B
Which of the following options describes a benefit of adopting the Architecture Canvas?
YC
A The Canvas provides a systematic approach to architecture design, supported by a validation tool.
B The Canvas provides an automatic way to follow and fix architecture principles.
C The Canvas provides a way to easily promote the collaboration and understanding of the business users.
D The Canvas provides faster architecture design without validation needs.
A
D
In OutSystems, is it recommended to join unrelated concepts in the same module?
A Yes, because it reduces the number of references, which simplifies deployments.
U
B No, because it prevents the lifecycle independence of concepts and adds unnecessary impacts to
consumers.
C Yes, to avoid cyclic references and reduce the footprint of generated code.
ST
D No, because it adds unnecessary complexity to consumers requiring both concepts.
B
Consider the following statement: "In OutSystems 11, it is recommended to use business-related Screens
in Foundation layer modules, since it does not break any Architecture validation rule." Which of the
following options is correct?
A The sentence is for all business-related Screens. All references to Screens are weak, so they can and
should be used in Foundation Layer modules, without causing upward references.
B The sentence is false. Although all references to Screens are weak, only non-business related Screens
should be used in Foundation layer modules.
,C The sentence is for business-related Web Screens. References to Mobile Screens are still considered
strong references, so they should not be used in Foundation Layer modules.
D The sentence is false. Although all references to screens are weak, only business-related Screens that
are not being consumed by other modules should be used in Foundation layer modules.
B
Consider that we have a weak side reference between End-user modules. What is the best way to remove
that reference to avoid an architecture violation?
A Replace Screen destinations by external URLs and consume Actions through REST APIs.
K
B Weak side references between End-user modules are allowed, so we do not need to remove that
reference.
C In these scenarios, always move the consumed elements from the producer module to the consumer
C
module to avoid the reference.
D Identify the consumed elements, excluding destinations, and move them to reusable Core/Foundation
modules.
LO
B
Which of the following options describes a valid reason to create a Calculation Engine (_Eng) module?
A To abstract different complex logic implemented in several Business Logic modules.
YC
B To support a concept with entities and CRUD edition.
C To support complex calculations (e.g. an insurance simulator).
D To support reusable Actions from Core Widget modules.
C
D
Why is it so important to adopt a naming convention in our applications?
A To reveal the nature of each module.
B To enforce the reference architecture.
U
C To normalize patterns.
D All the remaining options are correct!
D
ST
When moving elements between modules in OutSystems, to which elements should we pay extra
attention to and act more carefully?
A The elements with no data persistency, like Actions, Structures, or Blocks. Since these elements are not
persistent, they can be deleted unintentionally in the process.
B The elements with data persistency, like Entities. When moving an Entity, only its logical definition is
moved. Physically, it is another database table.
C There is no element in particular. All elements moved between modules maintain their integrity.
D Only the configurable elements, like Timers, Site Properties, or Roles. These elements are the only ones
that have data persistency that differs from Development to Production.
,B
Consider the following Discovery screenshot. What is the major evidence of bad architecture we can find
in this application canvas?
A The small proportion of Core applications shows that there is not enough reusability of Core modules.
B The only way to solve all the upward references is by refactoring the modules inside each application.
C There are too many shared services inside End-User modules.
D It is impossible to move modules between applications.
C
K
Why is it so important to have a multi-layer framework to support Architecture Design?
C
A To promote a correct abstraction of reusable services.
B To optimize lifecycle independence.
C To minimize impact of changes.
LO
D All the remaining options are correct!
D
In which of the following scenarios should a custom Style Guide be implemented?
YC
A Whenever applications cannot benefit from any existing theme. The Style Guide should be
implemented by cloning the most complex template available, to leverage the Blocks and Actions from
the original template and accelerate developments.
B Whenever applications cannot benefit from any existing theme. The Style Guide should be
implemented by starting from the most basic template possible, since it only contains the minimum
required structure to start.
D
C Whenever an application needs to have independent deployments and low-level of interdependence
among other applications.
D Always. Every project / application should have their own custom Style Guide
U
B
ST
Application is organized source by 4 layer canvas. End User A , End User B (Share business) and Core C
is circular the using. Choose the best Architecture solution to solve this problem.
A Architecture A, because module EndUserA and module EndUserB share the business.
B Architecture B, because module EndUserA and module EndUserB will be independent the core
(EndUserA use Core A, EndUserB use CoreB,..)
A
Which of the following are true when 3 module are consumer each other
A All moduels is inifnite loop warning when publish
B Publish in sequence A -> B -> C will not error happen.
, C Publish with Solution Pack is the only way to not be warned
D After Public A module, C module will not be warned
C
In the following picture, the solution on the left presents two front-end applications (appA and appB) and
a core component (coreC) that abstracts some reusable service. appA provides a reusable business concept
required by coreC, with some of this concept's logic being implemented in appB, causing problems with
the solution's dependencies. Knowing that these dependencies violate the rules for a good architecture,
pick the best alternative and justification to fix this architecture.
K
A Alternative 2, because it's the only one that solves the circular dependencies.
B Alternative 1, because correctly isolates the reusable service from appA and appB to the new core
component coreA
C
C Alternative 2, because it clearly has one module for each code source (coreA for code that came from
appA and coreB for code that came from appB) and this is more important than grouping by functionality.
D Alternative 1, because it is less granular.
LO
B
Select the correct option.
A Publishing a solution is the only way to publish all the modules (eSpaces) without getting outdated
YC
compilation warnings.
B Publishing a solution will loop forever, since there is a chain reaction caused by circular dependencies.
C Publishing a new version of appA.oml doesn't show any warning to republish coreoml.
D Publishing the modules (eSpaces) in Services Studio by the following order: appA.oml, then
coreC.oml. and the appB.oml, will fix all Outdated Consumer warning.
B
D
Consider the following architecture. When End-user modules are reresented in the blue. Core Service
U
modules in yellow. Foundation modules in green and the arrows indicate strong dependencies from
consumer to producer. Which of the following options is incorrect?
A there is a side reference violation in module D.
ST
B Changes in module G require module B to be re-Published.
C Changes in module G require module A to be re-Published.
D there is a side reference violation in module A.
A
"Retail company wants an application to audit its suppliers and stores. The application will have a web
flow for the store auditing process, accessible by the storeAuditor Role and another flow for the supplier
auditing process, accessible by the Subblier Auditor Role.
The Screen will all share the same look & feel, but each flow will have its own menu. It is also required to
create a new Calendar pattern, with some distinct features from the built-in one.
