OutSystems Architecture-Specialist-11 Quiz 1 Topic 1 Questions 1-5

Question: 1

Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...

A... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

BSame as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on source system

CSame as ECS with direct integration, but through an Enterprise Service Bus

D... is a pattern with two modules, a connector module that can be used to encapsulate an O external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

E... tries to fetch data from local cache entity, if not there, get single entry from the external p system. Cache only that record (read-through caching) Use when whole database too big or costly to synchronize. Integration only touches a small portion of the database. Avoid if access to lists of data is needed up front

FSame as ECS with local replica but API module is provided. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)

GSame as ECS with local replica but synchronization logic is separated. Pro: Code
independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS

H... a wrapper used to contain the logic, actions and data that will expose code that is inside of O external library or to inspect external database and import the data structures so they can be used as entities inside of OS

I... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to p. external system/database. No data is being kept inside OS. Data retrieval may not be optimized as it needs to traverse two different systems to get the information back. Con: Integration API must support all use cases

J... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

Show Answer

Question: 2

There are 3 common scenarios for Sharing a Style Guide. Which of the below is not part of th

scenario.

AIntranet (Single Sign On): Own Menu, Common Login Flow. Menu is defined in the Custom Template, but Login is defined in the Custom Theme. Application reference the Custom Them which picks up the Login.

BEnterprise Apps: Common Menu, Common Login Flow. Menu is defined in the Custom Theme, but Login is defined in the Custom Template.

CIndependent Apps : Own Menu, Own Login Flow. Login and Menu is defined in the Custom Template. Applications reference to its own Application Theme thus do not use the Login and Menu in the Custom Template.

DPortal : Common Menu, Common Login Flow. Login and Menu is defined in the Custom Them Application Theme reference the Custom Theme thus have a shared menu and login flow.

Show Answer

Question: 3

In OutSystems, a Core Application can contain ...

AEnd-User, Core, and Foundation Modules.

BFoundation and Core Modules

COnly Foundation Modules.

DEnd-User and Core Modules.

Show Answer

Question: 4

Which of the below is NOT a reason for Validating a Modules' Architecture?

AOptimizes lifecycle independence

BPromotes microservices

CMinimizes impact of changes

DPromotes abstraction of reusable services

EStop unmanageable dependencies

FPrevent slow deployments, inflexible legacy systems

GAvoid poor service abstraction

Show Answer

Question: 5

Which of the following Data elements can we find in a Foundation layer Module?

ACRUD actions for Entities

BCore Entities (exposed as read-only)

CNon-core Entities

DEntities to save UI states

Show Answer

OutSystems Architecture-Specialist-11 Quiz:1 Topic:1 Questions:1-5