Choose Architecture-Specialist-11 most accurate study material

OutSystems Architecture-Specialist-11 Exam Overview:

OutSystems Architecture-Specialist-11 Exam Syllabus Topics:

OutSystems Architecture Specialist (OutSystems 11) Sample Questions:

Question 1

What is the common naming convention for a mobile version of a CS module?

A. M_CS
B. mobile_CS
C. m_CS
D. _CS
E. m_cs

Question 2

Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation

A. ... Entity is exposed as read-only and API is available to centralize business logic for entity ^ creation/update
B. ... a wrapper used to contain the logic, actions and data that will expose code that is inside of ) external library or to inspect external database and import the data structures so they can be used as entities inside of OS
C. Same 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
D. ... caches only summary data that is frequently lister, joined or searched. Full detail for a (*) single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)
E. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
F. Same 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)
G. ... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to . 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
H. ... 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.
I. ... is a pattern with two modules, a connector module that can be used to encapsulate an ) external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.
J. Same 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

Question 3

Which of the below is NOT a disadvantage of having a fragmented system or microservices?

A. Monitoring & Logging : for effective monitoring & logging, requires centralized service
B. Security : need to manage credentials and access management
C. All of the above
D. Inter-process communication : network latency and hiccups
E. Multiple transactions committed independently
F. Complicated Debugging and troubleshooting : root cause may be deep inside the chain of services
G. Limited data mashup in memory and limited to APIs
H. Fault tolerance : communication errors, service consistency

Question 4

_Lib module is for

A. Theme, look & feel elements, menu, etc.
B. Reusable UI Patterns for layout and display only - no Business logic.
C. have several integration services with different systems, performing the same type of O operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).
D. Reusable Core Services with public entities, actions, and blocks.
E. Generic Library module
F. Technical wrapper to consume and normalize an external service

Question 5

Which of the below matches the most to Library Module Pattern - Connector Pattern...

A. Same 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
B. ... a wrapper used to contain the logic, actions and data that will expose code that is inside of external library or to inspect external database and import the data structures so they can be used as entities inside of OS
C. ... caches only summary data that is frequently lister, joined or searched. Full detail for a single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)
D. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
E. ... 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
F. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
G. Same 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)
H. ... is a pattern with two modules, a connector module that can be used to encapsulate an ) external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.
I. Same 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
J. ... tries to fetch data from local cache entity, if not there, get single entry from the external n 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

Solutions: